| Re: [cross-project-issues-dev] 2020-12 Release |
Just to note, I had thought I had created the release record, but I must not have saved it properly. I have just created the 8.1.0 release recordand the N&N.-- Jeff J._______________________________________________On Thu, Dec 3, 2020 at 11:30 AM Jeff Johnston <jjohnstn@xxxxxxxxxx> wrote:Hi Wayne,I somehow missed this error, but Linux Tools is releasing 8.1.0 for 2020-12. We released 8.0.0 for 2020-09. We have contributed 8.1.0 to simrel for a while now so hopefully it should just be a doc issue.-- Jeff J.On Thu, Nov 26, 2020 at 3:45 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:Greetings folks._______________________________________________Thanks for all of your hard work in assembling your contributions to the simultaneous release.I've created the master record ("release page") for the 2020-12 simultaneous release. Please have a look at the page and let me know what I've gotten wrong.I've started comparing it to the build aggrcon files and have noticed that a few projects appear to be contributing new releases but have not yet created release records. Please make sure that you've created the release record before asking me to update the release page.Selecting the right release record has required some guesswork on my part. I did notice that some of the release records have dates that are later than the simultaneous release date. Please make the value in the release date field for your release record is no later than December 16/2020.There were a few records dated 2020-12-18 that (at least according to the aggrcon files) I believe that I have correctly guessed are participating in the release; there was at least one release dated much later in December that I wasn't sure about and instead opted to pick the previous release as the participating one.If your project's release date is more than one year later than the date of your project's last successful release review, then you must engage in a release review. The EMO will automatically start tracking your release review when you submit your IP Log for review. Note that you only need to submit your IP Log for review or request PMC approval for your release if you are engaging in a release review.Even if your project does not require a release review, you must still take care to ensure that all of the intellectual property included in your release has been property vetted by the IP due diligence process. If you require assistance, please contact the IP Team.Note that the IP Team consults the future release records as input into their prioritization. Please create your release records as early as possible (even if you have to shift the date later) to ensure that we have as much information as possible to assist with prioritization and improve our odds of getting the intellectual property that you care about cleared well in advance of your planned release date.Wayne--Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
Join us at our virtual event: EclipseCon 2020 - October 20-22
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
Join us at our virtual event: EclipseCon 2020 - October 20-22