Garth Dahlstrom wrote: > Andreas, > > On Fri, May 8, 2009 at 6:18 AM, Andreas Pflug > <[email protected] <mailto:[email protected]>> wrote: > > Beta means, > "This will be our next version, should work for you, please report > bugs > we haven't noticed yet". > > > You should re-read the definition then, because you seem to have Beta > and Release Candidate confused with each other (I blame GMail Beta for > that! :P)... http://en.wikipedia.org/wiki/Software_release_life_cycle#Beta No I didn't. Citing: A "beta version" is the first version released outside the organization or community that develops the software, for the purpose of evaluation or real-world black/grey-box testing <http://en.wikipedia.org/wiki/Software_testing#White-box.2C_black-box.2C_and_gray-box_testing>. The process of delivering a beta version to the users is called *beta release*. Beta level software generally includes all features, but may also include known issues and bugs of a less serious variety
The Bugs I encountered are much too severe for somebody "outside the community", and are not "less serious". > > Are you running the beta or are you build this off of the very old > non-beta trunk? If it's the former we have; launchpad where people > are supposed to make bug reports when they find problems... Your > problem with the RMX was reported there by a user and has been > addressed: https://bugs.launchpad.net/bugs/367281 Both. I started with the beta trunk, because that's where the website directed me to, and later used beta. > > > While you are writing a perfect conversion script, don't spend too > much time on it, because its only going to be one-time use script to > convert all the mappings and then it will be discarded. I won't, I'm talking about 1.6 users that would like to upgrade to a more recent version to benefit from bugfixes. > > Oh and please take care to test it with each resulting device > mapping... huh? you don't have all of the devices? [The dev team > collectively have about a third of the devices that mappings exist > for, btw] That's why older mappings need to continue to work with bugfixed versions. Maybe you'd have to tell people, "ok, you can't have new features, only bugfixes with 1.6.2 but your mapping will continue to work" instead of "use the shiny new 1.7, your mapping will continue to work". > > The latest mappings for the RMX from BZR mixxx/1.7 branch work fine > for me. > > Expecting someone to be able to jump in and start contributing right > away is not a realistic expectation to have... > > If you want to contribute to Mixxx eventually, then take your time > learning it (all of the devs went through this process). Sorry, at an early stage I'm NOT willing to surf all mailing lists just to find out that the directive given at the bottom of http://www.mixxx.org/download.php is plain wrong for getting started. I'm embarrassed to have been misled, which wasted me hours. Does anybody care fixing that?!?!? Regards, Andreas ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
