Hi Alexander, Andrey, all,
Thanks for the mail chain. As a JDT lead and also taking into consideration the long legacy of Eclipse, my take as mentioned in [2] comment 11 is reproduced below verbatim:
"
I would prefer an early mail being sent across to various mailing lists (in the hope of *everyone* will see this) much before.
Now since Andrey has brought up this issue, let me re-iterate my stand here albeit with a modification. If it feels that there is a pressing need to move to 11 in 4.21, let us announce it in the cross-project/eclipse general mailing lists which Andrey has already gone ahead. And then lets wait for a few days (a week?) in M1 time frame.
However, I would like to make sure that this is a repeatable process and we stick to a particular mode.
In this case, the mode will be "let us move to the last stable release just before the BETA support for the next stable version is expected" instead of "let us move to the last stable release along with the BETA support of the next stable version".
If we announce this also, then the customers are not taken by surprise for the move and they can always plan for the same.
For those TL;DR, Here is the gist:
Option 1: Move to Prev Stable (11) when Next Stable(17) is supported => 4.22
Option 2: Move to Prev Stable(11) just before Next Stable(17) is supported => 4.21
My preference would be option 1 still, given that the expectation is set always in sync with the next stable version, more logically. However, am open for the 2 as well, but with weighted preferences for those in the JDT.Core team who finally ends up supporting this.
Regards,
Manoj
PS: sorry if you ended up getting multiple copies.