tor, 19 02 2009 kl. 12:23 +0100, skrev Schirmacher, Rolf: > This might come close to the naming convention of "the other brand": Calling > a release by a unified release number (R12, R13) or date (R2008-1) > independent of the versions of all the components, but allowing for some > canonical reference.
I can see the benefit of this from a users point of view. If Octave had time-based (rather than feature-based) releases then I think this might work. As things stand right now, then I don't think this is a good approach though. I have fixed a bunch of bugs in the image package since the last release and I would like to make a new release so that users aren't affected with these. But if I had to wait until a new release of Octave was made then there is a chance that I had to wait for a fairly long time. The problem is that I don't know when the next release of Octave is. I think individual package maintainers should be able to make releases whenever they think it is appropriate. We're all volunteers and it can be hard to make us all do some work at the same time. But that's just my 2 Danish Kroner... Søren ------------------------------------------------------------------------------ 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 _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
