Community
Participate
Working Groups
Hide 4.14 builds from the download page
New Gerrit change created: https://git.eclipse.org/r/149135
I suggest to skip this step in the future. It is IMHO unnecessary work which adds no value.
But wont user get confused since 4.13 is yet to be released and we will have 4.14 builds?
Gerrit change https://git.eclipse.org/r/149135 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=100bfbac3210c67fa4832369379a0050c3505819
(In reply to Vikas Chandra from comment #3) > But wont user get confused since 4.13 is yet to be released and we will have > 4.14 builds? I don't think so. Alexander, WDYT?
(In reply to Lars Vogel from comment #5) > (In reply to Vikas Chandra from comment #3) > > But wont user get confused since 4.13 is yet to be released and we will have > > 4.14 builds? > > I don't think so. > > Alexander, WDYT? I don't believe there are end users going to that page as it's not refrenced from any of the public downloads so it should be fine to skip that part.
Vikas, is that OK for you (skip this part) or shall we discuss this in the PMC.
?
I am ok to skip this. It made sense when we had yearly releases. but I think this is not required any more
New Gerrit change created: https://git.eclipse.org/r/149162
Ok, reverted the patch and will merge after the Gerrit build. Also I will mark this bug as wontfix after the merge. One step less....
Gerrit change https://git.eclipse.org/r/149162 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=f799415437a92dcd48bfdaa4fc8c7607440d7721
Here is the rationale for my opinion on skipping this When we had active development for current release and next release (like we did in annual releases, Branching out after RC2 and have active developement for RC3 and RC4 for current release and opening master for next release) it made sense to hide next release builds as the list of builds consists builds from both streams. Now we are branching out after last build of current release. So there is a clear distinction on next release builds and current release builds based on date. I feel this is no longer required.