Hi, Eddy Petrișor a écrit : > Now the beta2 branch will (ttbomk) be abandoned and trunk will continue to be > worked on (at least that's how *I* think is would be wise to go on), so beta > is > now worth nothing since beta2 was released.
Let's follow the following steps: 1) beta N is targeted to verify bug fixes and new code 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 4) beta N is released 5) if bugs are found in beta N, target beta N+1 and go back to 1), otherwise release official release All seems well, except if the new features introduced bugs, and they are found after beta release. Yeah, infinite loop! Really, to me, a release is: - make a branch for the release: features are frozen - betas are made until the last beta has no blocking bug or that can be delayed to a following release - the last beta is the official stable version This should shorten the time between releases and ease the work required on each beta. 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. But I'd really like if we could use it for 0.8.1 release. Best regards, -- Kurosu _______________________________________________ Wormux-update mailing list [email protected] https://mail.gna.org/listinfo/wormux-update
