Hey folks. I've assembled the list of participating projects and releases.
https://projects.eclipse.org/releases/2021-03 Let me know what I've gotten wrong. Note that before I can update a release number, you need to create a corresponding release record <https://www.eclipse.org/projects/handbook/#pmi-releases> for your project. I did notice that we have at least a few projects that have updated their aggrcon file. If you've done that, then chances are that we probably also need to update the release version on the releases page too. As I stated previously, you only need to engage in a release review if you are adding a new major or minor release to the simultaneous release and have not engaged in a successful release review since March 2020. Please make sure that all of your project's legal documentation is up-to-date. Let me know if you have any questions. Wayne On Tue, Feb 9, 2021 at 2:52 PM Wayne Beaton < wayne.bea...@eclipse-foundation.org> wrote: > Greetings 2021-03 Simultaneous Release Participants. > > *ACTION Required*: Create your release record for 2021-03.* > > * If you need one and have not already done so. More below... > > I'm starting to assemble the list of participating projects and versions. > > If you are adding new updated bits to the simultaneous release, then you > need to create a release record for the release that you are contributing. > Set the date to March 17; earlier is fine, but not later. > > If you are contributing a new major or minor release, and have not engaged > in a release review since March 2020, then you need to initiate a release > review (if you submit your IP Log for review now/soon, the EMO will guide > you through the rest of the process). There's help for IP Log reviews > <https://www.eclipse.org/projects/handbook/#ip-iplog> and releases and > reviews <https://www.eclipse.org/projects/handbook/#release-review> in > the handbook. If your service release only includes bug fixes with no new > features or significant changes, then no review is required. > > Note that you only need to seek PMC approval or submit your IP Log if you > need to engage in a release review (again, if you've done one in the last > year, you probably don't need to do one now). > > You are required to ensure that all intellectual property included in your > release bits has been fully vetted by the process. If you're not sure, > submit your IP Log and I'll have a look. > > Note that the Eclipse Dash License Tool > <https://github.com/eclipse/dash-licenses> does a good job of identifying > third party content that may need to be reviewed by the IP Team. > > Thanks, > > Wayne > -- > > Wayne Beaton > > Director of Open Source Projects | Eclipse Foundation > -- Wayne Beaton Director of Open Source Projects | Eclipse Foundation
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
