: release branch. Until 10 is actually released, why would we commit to : main, branch_10x, and *not* branch_10_0? The answer is stuff going to 10.1 : but really can't we just defer back-porting such changes? Then the RM can
Corret: New features might be "ready" and suitable for 10.1 but not suitable for 10.0 (which is in feature freeze) If you commit these features to main (but not 10x) and "wait" until after 10.0 to backport them, you risk them being forgotten about (and you complicate other "new feature" backports to branch_10x for people who *are* ready to backport them. The question "Can't we just defer back-porting such changes?" could be applied to any level of branching... We could also eliminate ever needing a branch_10x, and only use "main" for all feature development, if people just agreed to make a note of what features are suitable for 10.x and which need to wait for 11.x -- and then when brancH_10_1, (or branch_10_2, etc...) is created, go through that list and backport all the "10.x suitable" features -- but that moves all of the pain of backporting (and jenkins testing) to a short window of time before each release. -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
