Hi, It would help to actually state the rules the bot is following.
This case below is an assumption since you don't really name the rules and I am interpreting in between your lines: How do I stage a change that is not a cherry-pick? Yes, they do exist and I can name a few cases where this makes sense especially since we are talking about 3 minor releases of Qt in between. -- Alex ________________________________________ From: Development <[email protected]> on behalf of Oswald Buddenhagen <[email protected]> Sent: Friday, 3 February 2017 11:22:22 PM To: [email protected] Subject: [Development] HEADS-UP: 5.6 / LTS is now open for business moin, we finally managed to add a cherry-pick validator to the sanity bot, so i dared to open the 5.6 branch for staging again. caveat: patchsets created before the final forward merge got a positive review while they aren't cherry-picks. i don't suppose anyone would stage such an old patchset as-is anyway, but please check. note that there is an exception to the policy as well: the qt5 super repo continues to operate in forward-merge mode also for the LTS branch. you probably don't care unless you're in the release or CI team. there is also another consideration: these off 5.6 integration runs of course cost CI resources. maybe it would be smart as a matter of policy to have a dedicated team do the staging in batches. _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
