Tge 1.4

#1 1.3 was released into CVS before it was put into the installers. 1.4 is on the way.

At least, that's my impression.

#2 In the past three months, 1.4 on SVN has seen 113 commits. This is not counting development work done in other venues (people working offsite and off the repo, for instance).

#3 We don't have access to SVN, though, correct? I get all muddled on this since it has changed a bit over time.

#4 I thought that the CVS connection that we have was going to keep up to date with your internal updates, while the downloadable installer was going to be based on more stable versions.

#5 Steve, iirc, cvs will only be updated with stable point releases, ie when a new SDK installer comes out, CVS will be synced with it.
I also suppose some bug fixes will find their way in there in between releases.
In other words, GG and the associates helping them with TGE development are using an internal SVN repo, and hence CVS is not their development repo any more. It also means that HEAD should always be stable from now on :)
If I'm wrong, a GG employee will chime in I'm sure ;)

#6 You'll be seeing our Torque development plans unfold over the course of the next few months. Rest assured that we are thinking hard about how to balance internal development with public accessibility.

#7 I think I've mentioned this before, but one of the things I really liked about the CVS method of accessing the source was that I had the option of syncing daily, if I wanted. This meant that I could add each bug fix/code change one by one, as they were added to the HEAD. This meant a little bit of work each day, or once a week, or so, as opposed to a big sync, and a lot of comparisons. I will almost certainly want to add most, if not all of 1.4 to my project source, but the notion of needing to compare those 113 commits Ben mentioned all at once, is kind of daunting.

#8 I would like to see more updates live. If there is a bug that could be fixed, or improvement to be made, I sure would like to know about it and add the fix to my code.

thanks.

#9 I agree with Steve here , the cvs update was real good.
With cvs i could do small improvements and test them real fast.
And scream if it was something wrong with them :)

#10 Perhaps there should be two CVS branches, one with bleeding edge and the other with more stable stuff or CVS the way it is and SVN access for the bleeding edge.

#11 SVN access instead would be pretty cool. I prefer SVN anyway, it's what I use for my company's repositories. CVS is a pain. :)

#12 I've used both (on sf.net and berlios.de) and I think they are pretty much a muchness. CVS hasn't been updated in quite sometime, but hopefully the OpenCVS project will change that.

#13 Right now we're doing some really major rewrites. We have 10-15 branches going on, all with distinct but undocumented purposes, some of them with proprietary or NDA code, others badly broken...

Anyway, we're really aware of how handy it is to have up-to-the-minute access to the dev process, and we aren't trying to take that way from you. It's just that at this point in the dev cycle for Torque, in our SVN repo, there's a level of brokenness higher than there has been in the past. The short-term approach we're going to take is to release "code drops" every so often, so that you aren't totally cut off from development. When we're not in a "major rewrite" mode then we'll make more of an effort to keep the community tightly involved.

The thing I really want to avoid right now is having to explain, over and over, why HEAD is not only broken, but that it's broken in ways that are totally contradictory to the existing docs. :) Rest assured that we're already collecting a list of finished fixes that we're going to put into the first code drop, and that that list is getting longer every day...

#14 Sounds good. I'm loving this community more and more as time goes on. :)

#15 @Ben: Any chance of seeing SVN replace the CVS server?

#16 Even an SVN mirror of it would be awesome.

#17 @Tom - afaik thats the plan. SVN will become the revision system of choice