I'm bullish on version numbers increments too. I'd like to see the minor in
major.minor.fix bumped either +.1.0 or at least +.0.5 every time a
noticeable, significant feature or enhancement is introduced (including
internal refactoring)...
That would leave room for fix releases without having to resort to
1.6.1+fix1+fix2also.
I also think it is better to show minor version bumps especially when
configuration compatibility changes... As it will with the 1.6.2 release of
Mixxx which will feature completely incompatible midi mapping formats and
midi behaviour then that of the other point releases in the 1.6.x series.
__
--- == __/ t.O ==--
http://stacktrace.org/
On Tue, Feb 17, 2009 at 12:24 AM, Sean M. Pappalardo <
[email protected]> wrote:
> Hello.
>
> I had been wondering about this for awhile and it came to a head tonight
> as Garth prepared a Mixxx release to support the Herc driver...
>
> I always thought version numbers go like this: Major.minor.bugfix/maint
>
> Which would mean the MIDI scripting & learning really belongs in v1.7
> rather than 1.6.2. (This would've left 1.6.2 free for a Herc release.
> Now it's gotta be called 1.6.1+Herc or 1.6.1.1 or something equally
> nutty.) Then looping and such would go in 1.8, leaving 1.7.x free for
> bug fix releases.
>
> If you're worried about running out of numbers, there's nothing wrong
> with 1.10, 1.11, etc. if needed. (Though if we want to prepare for this,
> it helps to use leading zeroes for the single digit minor versions e.g.
> 1.05, 1.06, 1.06.01 to avoid confusion if we cross 10.)
>
> So I propose to move to this model, and rename what's currently slated
> 1.6.2 to 1.7.0, and current 1.6.3 to 1.8.0.
>
> Thoughts? Ideas? Rotten tomatoes?
>
> Sean
>
>
> <<--------------------------------------------------------------------------------->>
> This E-Mail message has been scanned for viruses
> and cleared by >>SmartMail<< from Smarter Technology, Inc.
>
> <<--------------------------------------------------------------------------------->>
>
>
> ------------------------------------------------------------------------------
> 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
> _______________________________________________
> Mixxx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>
------------------------------------------------------------------------------
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
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
