Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Final requirements document and plan for Neon

That reminds me, the biggest challenge with 3 month releases will be dealing with a CQ deadline that’s before the last release finishes and you've started on the new one. Happened with us on CDT last year and made for some pretty late requests.

From: <> on behalf of Wayne Beaton <wayne@xxxxxxxxxxx>
Organization: The Eclipse Foundation
Reply-To: Eclipse Planning Council <>
Date: Wednesday, December 9, 2015 at 3:39 PM
To: Eclipse Planning Council <>
Subject: Re: [] Final requirements document and plan for Neon

I've added some dates to the planning page. Specifically,

Dec 18/2015 - Opt-in deadline
Feb 12/2016 - (Tentative) CQ Submission deadline (specify that the CQ is required for Neon)
May 26/2016 - (Tentative) IP Log submission deadline
June 2/2016 - Review materials due
June 9/2016 - End of Release Review Period

Note that while I have confidence that the IP Team will agree with my IP-related dates, I'm waiting on final confirmation.


On 09/12/15 11:40 AM, David M Williams wrote:
As discussed at our last meeting, I have updated the requirements document and plan with all the latest, for the Neon release.

Since we commit to having these done by M4, I would like to give just a short period for your final review. Let's say, by Friday, Dec. 11. I think that is feasible, since we have discussed for so long, but if anyone needs an additional few days, please say. Otherwise I will announce "final" on Monday, 12/14.

The main new section of the Plan is that one about the 3 update releases for Neon:

As for requirements, you can search for
[added 12/2015, for Neon]
to read in context, but I will past them in there, for quick review.

[added 12/2015, for Neon]. Note: If a jar is already signed by the Eclipse certificate, then it must not be re-signed by projects for the release train.

[added 12/2015, for Neon] While part of the mechanics of contributing to the build, it is required that any contribution to the Simultaneous Release repository be done by a unique change to the b3aggrcon file. There are two ways to do this. First, your contribution repository can point to a simple repository where you know for sure there is only one version of your contribution available. Second, your contribution repository can be a composite repository but then you name exactly which versions to include. That is you need to specify all 4 version fields. You can, of course, do both methods, simple repository and name exact versions if you want the safety of that redundancy.

Feel free to correct spelling or grammar at will, but anything substantial should be here on this list.


_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Wayne Beaton
The Eclipse Foundation
          NA 2016
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Back to the top