| Re: [ee4j-pmc] Release Reviews for EE4J Projects |
Wayne, would you please update our "how to release" wiki page with any information from your message below that's missing from that page, so we'll have a more permanent and discoverable record of these instructions?
Thanks!
Wayne Beaton wrote on 11/07/2018 08:40 PM:
Note that I have sent this note to the PMC and have included all EE4J Project Leads (who are not themselves PMC members) in BCC.
Project leads: if you have not already done so, please subscribe to the ee4j-pmc mailing list.
The Eclipse Project Handbook describes our processes in painful detail. If you're not sure about what you're supposed to do, that is a good place to start. Please don't be shy to connect with the PMC via this list. We also have the incubation mailing list for questions. If you're really stuck, you can email emo@xxxxxxxxxxx and Cydnie and I will take care of you.
All Eclipse Projects are required to engage in a Release Review before distributing anything called a "release" to the general community. Distributing "milestone" or "snapshot" builds, intended for a more limited audience to gather feedback, during your release cycle is permitted by the process and strongly encouraged by the PMC and EMO.
Before your project can engage in a Release Review, we need to first have all of the intellectual property taken through the complete IP Due Diligence process. That is, everything must either be "license_certified" or "approved" by the IP Team before you can engage in the Release Review process.
Note that you absolutely need to create a CQ for your project's initial contribution and for every bit of third-party content that your project uses. Please take a look at your dependencies using "mvn dependencies:list" or "mvn dependencies:tree" should help you discover dependencies that you may have missed (as a general rule, anything that is "compile" phase is probably a pre-req dependency)
Regardless of the state of your intellectual property, if you have not already done so for your first Eclipse release, please create a Release record right now. Set the review date to December 5/2018, the version to an increment of one of the patch level over the last release, and the description to something along the lines of "First release from Eclipse. No API or implementation changes, just new licensing and Maven coordinates."
Note that as a matter of practice you should create a release record as early in each release cycle as possible. The IP Team uses the dates for releases as part of their task prioritization process. You can change/refine the date as necessary.
On the newly created release record and click "Schedule a Release Review for this release" and use December 5/2018 as the date.
Click the link in "This review is pending; contact The Eclipse Management Organization to make it public." to send a note to the EMO. The EMO will create a Bugzilla record to track the progress of the release (project leads will automatically be added in copy).
Wait for the Intellectual Property due diligence process to complete. Note that the IP Team has made getting the EE4J Project requests completed a high priority.
After the IP Team as completed processing your intellectual property records (CQs), and everything has either been "approved" or "license certified", return to the release record and click "Generate IP Log". Quickly scan the log to make sure that it looks okay and submit it for review. Do not submit your IP Log for review until after all project CQs have been resolved.
Then, click "Send Email to the PMC" with a request to the PMC for approval of the release and the corresponding review materials (clicking the link will form an email with all of the information that you need). You can do this in parallel with the IP Log review. The PMC does not need to see the IP Log, nor do they need to approve it (the IP Team and EMO will do this).
As the approvals come in, the EMO will update the tracking record in Bugzilla. When we have everything that we need, we will turn the release record from "pending" to "ongoing" and start our part of the review process.
On the date of the release review, the EMO will mark the record as "Successful" and update the tracking bug.
Let me know if you have any questions.
I've set up a call on Friday, November 9/2018. I'll walk through the process and answer any questions that you might have. I'm planning a 30 minute call, but have the entire hour blocked off if we need more time.
Join from PC, Mac, Linux, iOS or Android: https://eclipse.zoom.us/j/939811335
Or iPhone one-tap :US: +16699006833,,939811335# or +16468769923,,939811335#Or Telephone:Dial(for higher quality, dial a number based on your current location):US: +1 669 900 6833 or +1 646 876 9923Meeting ID: 939 811 335International numbers available: https://zoom.us/u/azOvdHyry
Thanks,
Wayne--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
Meet us at EclipseCon Europe 2018: LUDWIGSBURG, OCTOBER 23 - 25
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.