Hello everyone.

To bring you into the discussion, we're considering renumbering 1.6.2 to
1.7 before release, as kind of a "surprise" to end users, and a
reflection of reality that this version is really much improved over 1.6.x.

I understand that the marketing department has been using 1.6.2 all this
time, but I don't think anyone will have trouble putting together that
1.7 is "better" than 1.6.2. (Especially given the time between public
mention of 1.6.2 and release.) Just so long as we make a clean break at
release time, refusing to use the numbers interchangeably. (Which means
renaming the bzr branch after the coding sprint.) To clarify, I'm also
proposing to call the beta "Mixxx 1.7.0-beta1" to avoid any user
confusion (since they will have seen 1.6.0, 1.6.1, 1.6.1+Herc,
1.7.0-beta1, 1.7.0. No problem.)

Another argument for this is that some MIDI controllers supported in
1.6.1 & below are no longer, which would be unexpected in a point release.

So essentially, "1.6.2" is the development codename for 1.7. :)

Adam said:
> I'm not against this. I think it's a reasonable expectation that 
> 1.6.2 would be polish on 1.6.1 whereas actually we introduce new 
> features and probably a load of regressions.

Albert also agrees.

Let us know what _you_ think.

Sincerely,
Sean M. Pappalardo
"D.J. Pegasus"


<<--------------------------------------------------------------------------------->>
This E-Mail message has been scanned for viruses
and cleared by >>SmartMail<< from Smarter Technology, Inc.
<<--------------------------------------------------------------------------------->>

------------------------------------------------------------------------------
_______________________________________________
Mixxx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mixxx-devel

Reply via email to