Hello, 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...
Best regards, carlos Hilmar Berger wrote: >Hi, > >just two rather stupid questions: > >1. Does "tagged" mean we can't change them anymore or that can we still fix >bugs/minor features on this version ? >2. Is there a TODO list for bugs we want to fix before 0.1 ??? > >Hilmar > >On Thu, 14 Jul 2005 21:49:59 +0200 >Karsten Hilbert <[EMAIL PROTECTED]> wrote: > > > >>Dear all, >> >>if all goes well the GNUmed CVS will be tagged for release >>0.1 tomorrow, Friday July 15th 2005 at midnight CET (Central >>European Time). >> >>Anyone not agreeing with that better speak up now. >> >>The 0.1 release will follow soon after for reasonable >>values of "soon". >> >>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 >> >> >> > > > > -- GPG key ID FA50E162 @ random.sks.keyserver.penguin.de ECBD 59FE 1A50 630E DF7A 4AF2 E410 83FB FA50 E162 _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
