Kurosu wrote: > Hi, > > Eddy Petrișor a écrit : >>> 2) a branch beta N is made out of current trunk >>> 3) fixes are made to pre-beta N branch, while trunk get new features >> What do you mean by pre-beta N branch? > > Nevermind, I forgot to change all occurrences of this ill-chosen > expression I selected first. > >> As I see it the branching mechanism should be something like this: >> >> --beta N--bugs?->X --beta N+1-nobugs?->-final >> --trunk(feature freeze)--/----(fix bugs)------/----unfreeze(after final)-- > > I agree. > >>> That's the model used for many big projects, distros, firefox and >>> kernel. It may be unadapted to the development model of Wormux, though: >>> without new features, people may not be that interested in testing every >>> new beta. >> Indeed, that is a problem, but AFAIK 0.8 was meant to have the network code >> stabilised, so why not focus on that. There are some bugs that are related to >> networking which are interesting enough for a developer (e.g. disconnects) >> and >> probably a more stable game would be enough incentive for the testers. >> >> For 0.9 AI is the target, AFAIK, I guess AI is interesting enough to attract >> testers and developers ;-) > > Yes. It's just that 0.8 has been more burdensome than required. > > Now, some of the "bugs" reported against 0.8beta2 (mainly disconnection > warnings) are a bit troublesome: they may require important changes to > both branch and trunk/head.
Why would you want to do fixes in the branch? Are there that few bugs in the beta that we're considering already the final 0.8.0 release from the beta2 branch? Shouldn't the final branch be another beta which is generated from trunk and shortly after that declared final with just a few changes (bump version in configure.ac, rebuild tarball)? Taking into account the Windows<->Linux connectivity issues, I'd say that we are still far enough to not think yet about 0.8.0. > By the way, gna's bugtracker seems not to have knowledge of svn's > tags/branches/... The end result is that I don't know how to sort bugs > that are related to <= 0.8beta2. That would have been helpful to track > down problems in that release. Hmmm, so that you can do some regression testing? Or why? Anyway there is the "Target release" field, iirc which has that meaning. -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Wormux-update mailing list [email protected] https://mail.gna.org/listinfo/wormux-update
