On Fri, Jul 15, 2005 at 08:39:00PM +0200, Carlos Moro wrote: > Maybe it could be useful not only to tag but also make a new 0.1 branch. > That would allow us to go on fixing 0.1 when needed and algo go on > working in MAIN trunk, towards 0.2. At a convenience, we could: make > fixes both in 0.1 and MAIN. Or after a while, merge agin the branches to > join 0.1 branch changes to MAIN trunk...
The above is why I asked whether there was anyone with release management skills around. For now we'll just a) tag a baseline that we declare to be 0.1, b) keep on applying fixes only to it, and c) do not yet start development on 0.2 until we have figured out how to keep developing in HEAD all the while applying fixes to the 0.1 branch. Once we figure out how to safely keep a fix-only 0.1 branch around we will re-tag HEAD as 0.1.1 and branch it and start 0.2. That way we are likely fine. Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
