> Hi Lars, > > On Monday December 3 2012, Knoll Lars wrote: > > Dev: > > > > Dev is the branch where you can land anything that's supposed to go > > into 5.1. The following policies apply: > > > > * Changes have to be source and binary compatible > > * You can add new method and classes given that they are fully > > documented and tested * Please do not add half finished features. > > Create your own branch for that, and only push your changes once the > feature is fully done. > > Should we add: > > * carries a change to dist/changes-5.1.0 if it's (Qt-)user-visible (bug > fixes, > new features, performance fixes)? > > Same for stable once 5.0.0 branches off?
This would cause many more staging conflicts, as most changes would touch the same file. I'd suggest that bug fixes should not touch the changes file, only new features. This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
