From: Andrew T. (nilspace) <nil...@us...> - 2005-12-18 01:34:49
|
Kevin has finished the feed refactoring for 0.2. I think we should all test and fix any *major* bugs - and call this the 0.2 release. Also, Kevin, I think as we move forward, bug fixes should happen on the main CVS trunk, correct? If we have to go back and fix the 0.2 release, or anything, then we will branch it. But 0.2.1, etc will come off of HEAD. Then eventually there will be a 0.3 release (and possible branch) from HEAD. Andy ---------- Forwarded message ---------- From: Kevin <ke...@dr...> Date: Dec 17, 2005 12:15 PM Subject: [fofr] feed refactor complete To: Andrew Turner <ajt...@hi...> I'm satisfied the changes I've made are pretty well stable. I've merged them back into HEAD. If there are no more features to add, a release 0.2 branch should be created for bugfixes. With a name like this: REL_0_2-branch. Then, release tags on this branch can be like this: REL_0_2_0_final =3D v0.2.0 REL_0_2_1_final =3D v0.2.1 REL_0_2_2_final =3D v0.2.2 Putting the 'final' on there will help avoid confusion if we need to put other identifiers for a particular version number. For instance, if we need to have a beta or "release candidate" release. REL_0_2_0_beta1 REL_0_2_0_rc2 I don't see using this much, probably just for the first release on a release branch. -- Andrew Turner ajt...@hi... 42.4266N x 83.4931W http://highearthorbit.com Northville, Michigan, USA |