Yes, it is wrong. It should be 8.1.0. We released 8.0.0 for 2020-09. -- Jeff J.
On Thu, Dec 3, 2020 at 11:23 AM Jonah Graham <jo...@kichwacoders.com> wrote: > Hello Linux tools folk, > > I think your entry on https://projects.eclipse.org/releases/2020-12 is > incorrect. It says 8.0.0, but I think you are planning on 8.1.0 for 2020-12? > > PS Please ping me or update the NewAndNoteworthy entries in > epp.website.xml in the EPP project. > > Thanks, > Jonah > ~~~ > Jonah Graham > Kichwa Coders > www.kichwacoders.com > > > On Thu, 26 Nov 2020 at 15:45, Wayne Beaton < > wayne.bea...@eclipse-foundation.org> 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 <https://projects.eclipse.org/releases/2020-12>. >> 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 >> <https://www.eclipse.org/projects/handbook/#pmi-commands-release> 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 >> <https://www.eclipsecon.org/2020> - October 20-22 >> _______________________________________________ >> cross-project-issues-dev mailing list >> cross-project-issues-...@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev >> > _______________________________________________ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev >
_______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
