This document is for '''developers''' of the June 2010 Helios [[Simultaneous Release]]. [Need link for users and consumers]

−

This page is for '''developers''' of the June 2010 Helios Simultaneous Release. If you are a consumer of the Release, perhaps a tester or an early adopter, you'll want [[Helios Simultaneous Release/For Users | Helios Simultaneous Release For Users]]. Note that [http://www.eclipse.org/projects/helios.php the master page on the eclipse.org site] points here.

+

<!--

−

</div></div>

+

If you are a consumer of the Release, perhaps a tester or an early adopter, you'll want [[Helios Simultaneous Release/For Users | Helios Simultaneous Release For Users]]. Note that [http://www.eclipse.org/projects/helios.php the master page on the eclipse.org site] points here.

+

-->

−

This page is under development. It is expected to be complete around Mid September.

−

−

===Project Plan===

−

A roll up project plan for projects participating in the Helios simultaneous release is found here: http://www.eclipse.org/projects/project-plan.php?projectid=helios

===Requirements For Participation===

===Requirements For Participation===

−

Projects that are part of Helios agree to abide by the following requirements. '''Note:''' the EMO will remove projects that do not meet the ''required'' constraints.

+

Projects that are part of Helios agree to abide by the [http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php requirements of the Eclipse yearly Simultaneous Release].

−

For a report of overall Helios status, see this [http://www.eclipse.org/projects/helios_status.php report]. '''Note:''' this report is bugzilla intensive, so please use sparingly.

+

[http://eclipse.org/helios/planning/SimultaneousReleaseGrid.php Compliance Reports] show progress on meeting the requirements and their final achievement.

−

==== Must Do ====

+

===Milestones and Release Candidates===

−

{| border="1" cellpadding="3" cellspacing="1"

+

The Release is always on the fourth Wednesday of June. The milestone dates are at roughly 6 week intervals. Any end-of-cycle release-candidate (RC) dates are typically one week apart. Each project has their deliveries due at times offset from the end-date, so that the project dependencies can come together in a reasonable order. These delivery times are based on the dependencies between projects. They are labeled +0, +1, +2, and +3, with +0 coming first (the Platform) and +3 coming last (EPP). Projects themselves decide if they are +0, +1, +2, or +3. The actual time-offset represented by these intervals change over the course of the year of development, being several days at first, but then only one day near the end of the release. The following calendar is the official schedule of the overall Helios Release. Projects are free to have their own schedules as long as they meet the Helios deliverables.

−

|+ '''Helios Release "Must Do" Items'''

+

−

! style="background:#efefef;" | Category

+

−

! style="background:#efefef;" | Item

+

−

! style="background:#efefef;" | Description

+

−

! style="background:#efefef;" | Target Milestone

+

−

! style="background:#efefef;" | Verification Method

+

−

! style="background:#efefef;" | Master Bug

+

−

|-

+

−

| rowspan="6" | Participation

+

−

| rowspan="2" | Intent

+

−

| Projects must have stated and demonstrated their intent to join Helios by the M4+0 date. Projects do so by adding themselves to bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=251715 251715] and asking to have their project-specific bugs created as clones of each of those referenced in this table.

| At least one person from each project must subscribe to cross-project bug inbox, i.e. edit Bugzilla prefs to watch "cross-project.inbox@eclipse.org". Build team members (or their designated alternates) from each project will provide communication channels: phone, mail, IM, IRC and will be available during the milestone integration periods.

| Projects must have a written ramp down policy by M6+0, linked in the table above pending inclusion of ramp down element in the XML project plan. (One of the issues identified with this guideline is that its not so much the ramp down policy of how many votes are needed for each bug fix that we need to be consistent on, but rather the meaning of each of the milestones and release candidates. See [http://www.eclipse.org/eclipse/development/freeze_plan_3.4.php Platform 3.4 Endgame plan] as a guideline. See also [[Helios/Final Daze|Helios Final Daze]].)

| Projects should leverage only published APIs of dependencies. As a Release Review requirement, all deviations must be documented. Additionally, rectification for the issues should be listed as part of a migration plan, with bugs listed where APIs need to be provided by dependent projects. '''Perhaps a '99 44/100% Pure APIs' indicator for projects with no improper usage can be used to advertise the 'cleanest' projects?''' ;)

| All plug-ins (bundles) must use the true bundle form. That is, provide a manifest.mf file, and not rely on the plugin.xml file being 'translated' into a manifest.mf file at initial startup. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130598 bug 130598]. With that, empty plugin.xml files in the presence of a manifest.mf file should not be included in a bundle.

| All plug-ins must correctly list their required JVM versions in the manifest.mf. See the wiki page about selecting the correct JVM [http://wiki.eclipse.org/index.php/EMF_2.3_JVM_Requirements#Runtime_.2F_Compilation_Compatibility].

| Projects must use jar'ed plug-ins (with unpack=false) unless authorized by the planning council for technical reasons. Nested jars should be avoided if possible since it creates problems for projects that has dependencies to such plug-ins. The OSGi runtime is fine with it but the compiler is not able to handle classpaths that contain nested jars. In case only one nested jar exists, it is often better to expand the contents of that jar into the root folder (i.e. unnest the jar). If a plug-in contains large files that are frequently used (opened and closed), a jar'ed plug-in might degrade performance significantly since the file must be decompressed each time it is opened.

| Any new third-party plug-ins that are common between projects must be consumed via [http://www.eclipse.org/orbit/ Orbit]; the final Helios release will not have duplicate third-party libraries (note that this only applies to identical versions of the libraries; thus if project A requires foo.jar 1.6 and project B uses foo.jar 1.7, that's ok).

| Projects must [[Update_Site_Optimization|optimize]] their own update site using [[Pack200|pack200]] to reduce bandwidth utilization and provide a better update experience for users. With the introduction of p2, project update sites must generate metadata (artifact and content repository info).

| Must have [[Architecture Council/New and Noteworthy|New &amp; Noteworthy]] for each milestone. Must be something readable and usable not just a static list of all the bugs, e.g. [http://download.eclipse.org/eclipse/downloads/drops/R-3.4-200806172000/whatsnew3.4/eclipse-news.html platform]. Corollary: individual new &amp; noteworthy should be linked in to the collective New & Noteworthy.

| This means that users can load any subset of the Helios projects into Eclipse and each of the loaded projects will pass all the same tests as if it had been loaded independently. If such a problem is identified, the affected projects must fix the problem.

| Each project will provide basic capability/activity definitions to allow for their UI contributions to be hidden. These must be provided in a separate plugin/feature to facilitate inclusion/exclusion by consumers in product development.

| Each major project (as determined by participating PMCs) should have an About dialog icon with [https://bugs.eclipse.org/bugs/show_bug.cgi?id=198941 descriptive text] (e.g. provider name = "Eclipse Modeling Project" and not simply Eclipse.org) and contribute to the welcome page.

Note that projects choose their own +n category based on major or primary dependencies. There are many cases where a project might have to deliver pieces of their code a little earlier, if some project depends on it, or a little later if they have a stray dependency. These sorts of deviations are left to the projects to work out, pair-wise, among themselves. Feel free to bring up complicated cases for discussion.

−

{| border="1" cellpadding="3" cellspacing="1"

+

−

|+ '''Helios Release "Should Do" Items'''

+

Given all these constraints, the exact dates for any particular year are pretty predictable. The following table summarizes the most significant Helios dates, but see the subsequent calendar for the important details. That is, your stuff is due earlier than these table dates! Projects need to deliver a week or two before these "end dates", depending on their chosen, committed offset category (+0, +1, etc).

| Should follow the [[User Interface Guidelines]]. The [[UI Checklist]] is a good place to start. Also, should participate in a [[User Interface Best Practices Working Group]] [[UIBPWG UI Walkthrough | UI walkthrough]].

These milestone and release candidate dates are based on the dependencies of the projects (we call these the +0, +1, and +2 dependencies). Obviously, if a +0 date slips, then it will cause the +1 and +2 dates to slip; similarly for a +1 slip causing +2 slips. Note that the +0, +1, +2, and +3 dates are roughly equivalent to stable nightly builds in a traditional Eclipse project - each of these partial milestone builds will incorporate more and more of the associated project milestones. The "Release" date is the official M/RC date.

−

Note: in the following table, '''''RC5''''' on the 'Helios' line does not mean this final build is a release ''''candidate'''' ... it is still to be the ''''final build'''' for this Release ... but 'RC5' is the suggested "target" to have some consistent terminology in Bugzilla, and similar things, to be able to mark things that are different in the final release build than in the RC4 build. [The full word, "Helios" doesn't make a very good bugzilla milestone target, since it's a little too inclusive, and "R" (for "Release") is too short. TODO: next year consider "GA" for this final target?]

+

M1 Friday, August 21, 2009

+

M2 Friday, October 2

+

M3 Friday, November 13

+

M4 Friday, December 18

+

M5 Friday, February 5, 2010

+

M6 Friday, March 19

+

EclipseCon! March 22

+

M7 Friday, May 7

+

RC1 Friday, May 21

+

RC2 Friday, May 28

+

RC3 Friday, June 4

+

RC4 Friday, June 11

+

Release Wednesday, June 23

−

'''Hopefully''' there will '''not by ''ANY'' differences''' between RC4, and RC5 ... but, some projects may find they have to make doc additions, readme files, etc., so ... this just provides a way that such changes can be consistently marked, tracked, etc., to better keep everyone informed about what might be different between RC4 and the RC5 (the final released code). [Note: it's probably obvious, but this does not mean "RC5" should be part of the final zip file names or anything. those can still be what ever "final" name they would always have.]

As with Ganymede, reporting on status will be done using a wiki table.

−

</del>

−

We have decided that instead of affirmative signoffs, projects should post exceptions to the cross-project dev mailing list.

+

Only negative status needs to be reported. It is essential for many aspect of the simultaneous release that communication be prompt and clear, on many topics. One of the most important ones, is if someone is not meeting some date or delivery. Put another way, we assume everyone is on target and has delivered their stuff unless a note is sent to cross-project list that you are delayed. Its better to be up front about it, so everyone knows what to expect, rather than to hope things turn out ok at the very last minute, since if you "miss" without saying anything you are more likely to impact other people, and miss your chance to be part of the release.

−

+

−

====Conference Calls====

+

−

+

−

The [[Planning Council]] is the body responsible for coordinating the Helios release train. Thus, its [[Planning_Council#Call_and_Meeting_Schedule|conference calls]] are the Helios planning and coordination calls.

+

====Mailing Lists and Newsgroups====

====Mailing Lists and Newsgroups====

−

Eclipse projects have three communication channels: a mailing list for developers, a newsgroup for users, and Bugzilla. Helios, although not a "project" per se, will use the same structure:

+

Eclipse projects have three communication channels: a mailing list for developers, a newsgroup for users, and Bugzilla. While Helios is not a "project" per se, it will use the same structure:

* [https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev cross-projects-issues-dev] - mailing list for developers and releng (see [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/threads.html archives]). This is the list to use to discuss build issues, announce changes in plans, slippage in deliverables, etc.

The old [https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council eclipse.org-planning-council ] mailing list will be used for non-Helios Planning Council items.

+

=====Bugzilla=====

−

=== Bugs & Feature Requests ===

+

If there is any doubt about where a bug belongs, it can always start in the "Cross-Project" component. (Under Eclipse Foundation > Community). If it turns out to be a single-project's responsibility, it can be moved to that project. If it is a true cross-project bug, where several projects need to act, then it can stay in the cross-project component.

* Open a new [https://bugs.eclipse.org/bugs/enter_bug.cgi?assigned_to=cross-project.inbox%40eclipse.org&product=Community&component=Cross-Project Cross-Project] bug

* Open a new [https://bugs.eclipse.org/bugs/enter_bug.cgi?assigned_to=cross-project.inbox%40eclipse.org&product=Community&component=Cross-Project Cross-Project] bug

+

+

=====The Planning Council Mailing List=====

+

+

Because there has been confusion in the past, we'll be explicit here that the [https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council planning council mailing list (eclipse.org-planning-council) ] is for Planning Council business, not the Helios Release activities per se. While they sometimes overlap, there is no need to cross post. While anyone can request a subscription to the planning council list (for openness and transparency) the expectation is that only Planning Council members post to it.

+

+

=====Conference Calls=====

+

+

The [[Planning Council]] has regularly scheduled calls for Planning Council business. See [[Planning_Council#Call_and_Meeting_Schedule|conference calls]].

+

+

But there are no planned calls for the release, per se, or for larger audiences, but they can be arranged if required or desired (for example, if needed for build coordination).

===Helios Builds and P2 repository ===

===Helios Builds and P2 repository ===

−

A number of utilities have been written to automate the assembly of Callisto '06, Europa '07, Ganymede '08 and now Helios '09 builds. These are available in their own CVS respository. You can find more information about how this is organized and individual project responsibilities for the build on this [[Helios/Build | Helios Build]] page (with old information on the [[Ganymede/Build | Ganymede Build]] and [[Europa/Build | Europa Build]] pages).

+

==== Builds (Aggregation) ====

−

And with Helios we are using the [[Buckminster Helios Builder]].

+

This section, about assembling the repositories, is subject to change, as improvements in the process are made.

+

+

A number of utilities have been written to automate the assembly of Callisto '06, Europa '07, Ganymede '08, Galileo '09, and now Helios '10 builds. These are available in their own CVS repository. You can find more information about the history and organization by looking at some of the old, previous information on the [[Galileo/Build | Galileo Build]], [[Ganymede/Build | Ganymede Build]] or [[Europa/Build | Europa Build]] pages).

+

+

With Helios we are using the [[Buckminster Galileo Builder|Buckminster Galileo/Helios Builder]] (with some discussion of incorporating the [[Buckminster_Aggregator_User_Guide|Buckminster Aggregator]]).

The [[Helios/Contributing_to_Helios_Build | Contributing to Helios Build]] page is where you go to learn how to add your project to the Helios build.

The [[Helios/Contributing_to_Helios_Build | Contributing to Helios Build]] page is where you go to learn how to add your project to the Helios build.

Line 263:

Line 98:

http://download.eclipse.org/releases/staging

http://download.eclipse.org/releases/staging

−

===Coordinated Service Releases ===

+

===Service Releases ===

+

+

Coordinated Service Releases are (always) scheduled for the fourth Friday of September, and the fourth Friday of February. Individual Projects may have their own, of course, at any time, if they need to, but all participants in the Yearly Release, are expected to participate in the Coordinated Service Releases. What bugs are fixed, if any, is up to each Project to decide, but each Project must continue to "fit in", build, install, avoid conflicts, etc.

+

+

[Note: the following Service Release dates have not yet been added to the above calender, but will be soon.]

==== SR1 ====

==== SR1 ====

−

GA: 9/25/09 (last Friday of September)

+

GA: 9/24/2010 (last Friday of September)

In the SR1 rampdown, as shown in the following table, there will be 4 RCs, each spanning one week, with projects staging themselves into the build just one day apart.

In the SR1 rampdown, as shown in the following table, there will be 4 RCs, each spanning one week, with projects staging themselves into the build just one day apart.

−

Projects may elect not to participate in a particular RC, but have an obligation to fix any build problems that is related to their code or p2 repository.

+

Projects may elect not to participate in a particular RC, but have an obligation to fix any build problems that are related to their code or p2 repository.

RC1 will be in the middle of August, several weeks earlier than previous years, just to make sure we can still build, etc. Subsequent RCs dates are similar to [[Ganymede#Coordinated_Service_Releases| previous years]], except a "quiet" final week is also planned. (It is normally pretty quiet anyway ... this just formalizes it).

RC1 will be in the middle of August, several weeks earlier than previous years, just to make sure we can still build, etc. Subsequent RCs dates are similar to [[Ganymede#Coordinated_Service_Releases| previous years]], except a "quiet" final week is also planned. (It is normally pretty quiet anyway ... this just formalizes it).

Line 276:

Line 115:

The Final week before GA will not have any further builds or contributions, but instead be reserved for final adopter testing and preparation and only emergency fixes for very serious regressions will be considered.

The Final week before GA will not have any further builds or contributions, but instead be reserved for final adopter testing and preparation and only emergency fixes for very serious regressions will be considered.

−

The 'promote' day (9/24) will be the day projects put final zips in their final spot (without displaying them) so they can propagate through the mirroring system. Similar for the p2 repository -- it will be replaced on 9/24 with the new content so it can start mirroring. Note: there is no plan to retain multiple versions in the common discovery repository (unless someone volunteers to do what's required to make that happen). At noon on 9/25 projects can make their final maintenance releases visible.

+

The 'promote' day (9/23) will be the day projects put final zips in their final spot (without displaying them) so they can propagate through the mirroring system. Similar for the p2 repository -- it will be replaced on 9/23 with the new content so it can start mirroring. Note: there is no plan to retain multiple versions in the common discovery repository (unless someone volunteers to do what's required to make that happen). At noon on 9/24 projects can make their final maintenance releases visible.

{| border="1" align="center" width="600"

{| border="1" align="center" width="600"

Line 288:

Line 127:

|-

|-

! align="right" | RC1

! align="right" | RC1

+

| 8/9

| 8/10

| 8/10

| 8/11

| 8/11

| 8/12

| 8/12

| 8/13

| 8/13

−

| 8/14

|-

|-

! align="right" | RC2

! align="right" | RC2

+

| 8/30

| 8/31

| 8/31

| 9/1

| 9/1

| 9/2

| 9/2

| 9/3

| 9/3

−

| 9/4

|-

|-

! align="right" | RC3

! align="right" | RC3

+

| 9/6

| 9/7

| 9/7

| 9/8

| 9/8

| 9/9

| 9/9

| 9/10

| 9/10

−

| 9/11

|-

|-

! align="right" | RC4

! align="right" | RC4

+

| 9/13

| 9/14

| 9/14

| 9/15

| 9/15

| 9/16

| 9/16

| 9/17

| 9/17

−

| 9/18

|-

|-

! align="right" | Helios SR1 ("GA")

! align="right" | Helios SR1 ("GA")

Line 319:

Line 158:

|

|

|

|

−

| promote: 9/24

+

| promote: 9/23

−

| GA: 9/25

+

| GA: 9/24

|}

|}

==== SR2 ====

==== SR2 ====

−

2/26/10 (last Friday of February)

+

2/25/2011 (last Friday of February)

Rampdown similar to SR1.

Rampdown similar to SR1.

Line 339:

Line 178:

|-

|-

! align="right" | RC1

! align="right" | RC1

+

| 1/17

| 1/18

| 1/18

| 1/19

| 1/19

| 1/20

| 1/20

| 1/21

| 1/21

−

| 1/22

|-

|-

! align="right" | RC2

! align="right" | RC2

+

| 1/31

| 2/1

| 2/1

| 2/2

| 2/2

| 2/3

| 2/3

| 2/4

| 2/4

−

| 2/5

|-

|-

! align="right" | RC3

! align="right" | RC3

+

| 2/7

| 2/8

| 2/8

| 2/9

| 2/9

| 2/10

| 2/10

| 2/11

| 2/11

−

| 2/12

|-

|-

! align="right" | RC4

! align="right" | RC4

+

| 2/14

| 2/15

| 2/15

| 2/16

| 2/16

| 2/17

| 2/17

| 2/18

| 2/18

−

| 2/19

|-

|-

! align="right" | Helios SR2 ("GA")

! align="right" | Helios SR2 ("GA")

Line 370:

Line 209:

|

|

|

|

−

| promote: 2/25

+

| promote: 2/24

−

| GA: 2/26

+

| GA: 2/25

−

|}

+

−

+

−

===Projects===

+

−

The projects that plan to participate in the Helios Simultaneous Release are listed below, along with their milestone offsets, leaders, release engineer, and ramp down policy.

Requirements For Participation

Milestones and Release Candidates

The Release is always on the fourth Wednesday of June. The milestone dates are at roughly 6 week intervals. Any end-of-cycle release-candidate (RC) dates are typically one week apart. Each project has their deliveries due at times offset from the end-date, so that the project dependencies can come together in a reasonable order. These delivery times are based on the dependencies between projects. They are labeled +0, +1, +2, and +3, with +0 coming first (the Platform) and +3 coming last (EPP). Projects themselves decide if they are +0, +1, +2, or +3. The actual time-offset represented by these intervals change over the course of the year of development, being several days at first, but then only one day near the end of the release. The following calendar is the official schedule of the overall Helios Release. Projects are free to have their own schedules as long as they meet the Helios deliverables.

Note that projects choose their own +n category based on major or primary dependencies. There are many cases where a project might have to deliver pieces of their code a little earlier, if some project depends on it, or a little later if they have a stray dependency. These sorts of deviations are left to the projects to work out, pair-wise, among themselves. Feel free to bring up complicated cases for discussion.

Given all these constraints, the exact dates for any particular year are pretty predictable. The following table summarizes the most significant Helios dates, but see the subsequent calendar for the important details. That is, your stuff is due earlier than these table dates! Projects need to deliver a week or two before these "end dates", depending on their chosen, committed offset category (+0, +1, etc).

Communication Channels

Cross-Project Milestone & RC Status Reporting

Only negative status needs to be reported. It is essential for many aspect of the simultaneous release that communication be prompt and clear, on many topics. One of the most important ones, is if someone is not meeting some date or delivery. Put another way, we assume everyone is on target and has delivered their stuff unless a note is sent to cross-project list that you are delayed. Its better to be up front about it, so everyone knows what to expect, rather than to hope things turn out ok at the very last minute, since if you "miss" without saying anything you are more likely to impact other people, and miss your chance to be part of the release.

Mailing Lists and Newsgroups

Eclipse projects have three communication channels: a mailing list for developers, a newsgroup for users, and Bugzilla. While Helios is not a "project" per se, it will use the same structure:

Developer mailing list

cross-projects-issues-dev - mailing list for developers and releng (see archives). This is the list to use to discuss build issues, announce changes in plans, slippage in deliverables, etc.

Users news group

Bugzilla

If there is any doubt about where a bug belongs, it can always start in the "Cross-Project" component. (Under Eclipse Foundation > Community). If it turns out to be a single-project's responsibility, it can be moved to that project. If it is a true cross-project bug, where several projects need to act, then it can stay in the cross-project component.

The Planning Council Mailing List

Because there has been confusion in the past, we'll be explicit here that the planning council mailing list (eclipse.org-planning-council) is for Planning Council business, not the Helios Release activities per se. While they sometimes overlap, there is no need to cross post. While anyone can request a subscription to the planning council list (for openness and transparency) the expectation is that only Planning Council members post to it.

Conference Calls

But there are no planned calls for the release, per se, or for larger audiences, but they can be arranged if required or desired (for example, if needed for build coordination).

Helios Builds and P2 repository

Builds (Aggregation)

This section, about assembling the repositories, is subject to change, as improvements in the process are made.

A number of utilities have been written to automate the assembly of Callisto '06, Europa '07, Ganymede '08, Galileo '09, and now Helios '10 builds. These are available in their own CVS repository. You can find more information about the history and organization by looking at some of the old, previous information on the Galileo Build, Ganymede Build or Europa Build pages).

Service Releases

Coordinated Service Releases are (always) scheduled for the fourth Friday of September, and the fourth Friday of February. Individual Projects may have their own, of course, at any time, if they need to, but all participants in the Yearly Release, are expected to participate in the Coordinated Service Releases. What bugs are fixed, if any, is up to each Project to decide, but each Project must continue to "fit in", build, install, avoid conflicts, etc.

[Note: the following Service Release dates have not yet been added to the above calender, but will be soon.]

SR1

GA: 9/24/2010 (last Friday of September)

In the SR1 rampdown, as shown in the following table, there will be 4 RCs, each spanning one week, with projects staging themselves into the build just one day apart.

Projects may elect not to participate in a particular RC, but have an obligation to fix any build problems that are related to their code or p2 repository.

RC1 will be in the middle of August, several weeks earlier than previous years, just to make sure we can still build, etc. Subsequent RCs dates are similar to previous years, except a "quiet" final week is also planned. (It is normally pretty quiet anyway ... this just formalizes it).

The Final week before GA will not have any further builds or contributions, but instead be reserved for final adopter testing and preparation and only emergency fixes for very serious regressions will be considered.

The 'promote' day (9/23) will be the day projects put final zips in their final spot (without displaying them) so they can propagate through the mirroring system. Similar for the p2 repository -- it will be replaced on 9/23 with the new content so it can start mirroring. Note: there is no plan to retain multiple versions in the common discovery repository (unless someone volunteers to do what's required to make that happen). At noon on 9/24 projects can make their final maintenance releases visible.