Hi guys, With the 0.9.4 release coming very soon... I was thinking about the major changes planned for 0.9.5 (transport, fx-fun, jackMidi). In addition, it's been (what?) 3 years between 0.9.3 and 0.9.4. And that included some major changes. In light of these, I would like to make two suggestions:
Proposal #1: After releasing 0.9.4, create a 0.9 branch for bug fixes. Trunk will become 0.10.x. Releases 0.9.5, .6, .7, etc. would only be bug fixes for 0.9. Proposal #2: Try for shorter release cycles. Allow a short period of time (somewhere between 2 and 6 weeks) for new features. Freeze until all the bugs are worked out (or backed out). Release when stable. Rinse. Repeat. (This is how the Linux kernel is currently doing it.) Note: Prop #2 implies that new features are developed in private branches while trunk stabilizes. Thus, we should probably make sure that the private branches be pretty stable before merging into trunk. (For example, I was testing the jackMidi branch and found that MIDI Recording is totally broken. :-)) What do you think? Peace, Gabriel ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Hydrogen-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
