Robin Sheat wrote: > Looking on Launchpad (https://code.launchpad.net/mixxx), it's hard to tell > which branch I should be using if I want to make patches.
The 1.7 branch is in feature-freeze, so only patch against it if your changes are fixes rather than new features. > The one marked 'focus of development' is 11 weeks old, the 1.7 one is only 30 > hours old, but doesn't have the star beside it. That's because we haven't migrated trunk from SVN yet but are planning to do so after 1.7.0 is released. > I assume that we should make > our own branches against lp:mixxx and propose them for merging when done? After migration of trunk from SVN to BZR, this is correct. > Also, should we be making branches for tiny changes (like I'm about to do), > or > is there a better way? The head devs have the final say of course, but I would say that tiny changes could be sent as patches. However, there is a risk of them getting lost/forgotten if they're just mailed. If you keep a personal branch around and make your changes to that, then propose it for merging every so often, that would ensure it doesn't get missed. Sean <<--------------------------------------------------------------------------------->> This E-Mail message has been scanned for viruses and cleared by >>SmartMail<< from Smarter Technology, Inc. <<--------------------------------------------------------------------------------->> ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
