On Thu, May 23, 2024 at 10:42 PM Wayne Beaton via cross-project-issues-dev < cross-project-issues-dev@eclipse.org> wrote:
> I have applied all of the updates. There's an anomaly in the system > related to the recent upgrade of the PMI that required a little more > mechanical work than usual to apply these updates, so there is some chance > that I may have messed something up. If you notice something, let me know. > You missed to update JGit which will ship 6.10.0 not 6.9.0 AFAICT (based on what I'm seeing in the simrel.build Git repository), this > release marks the return of the Eclipse Papyrus project to the simultaneous > release. Welcome back. > > Please let me know if there are any other issues. > > If you require a review, please reach out to the EMO. > > Wayne > > On Wed, 22 May 2024 at 17:56, Wayne Beaton < > wayne.bea...@eclipse-foundation.org> wrote: > >> Greetings folks! >> >> I've assembled the release information for participating projects here >> <https://projects.eclipse.org/releases/2024-06>. >> >> Note that the list of projects reflects our long time practice of only >> including projects whose teams are actively participating in the >> simultaneous release. If you look hard enough, you'll notice that projects >> that have been "sponsored in" by participating projects are absent from the >> list. This is per the requirements. I expect that these requirements will >> change in some future release. >> >> A lot of the releases are quite old, and based on the activity in the >> simrel.build <https://github.com/eclipse-simrel/simrel.build> >> repository, at least a few projects need to create some release records, >> and some may need to engage in a progress review (I've done my usual thing >> of making by best guess based on the release records in the system). >> >> If your project is contributing a different release than what you see >> here, please ensure that you've created a release record >> <https://www.eclipse.org/projects/handbook/#pmi-commands-release>, and >> let me know. If your project has not engaged in a progress (or release) >> review <https://www.eclipse.org/projects/handbook/#progress-review> in >> more than one year, please engage with the EMO ASAP to schedule a review. >> >> Be sure to set the New and Noteworthy URL in your release record: it is >> through this relationship that we build the aggregate N&N. >> >> Please make sure that you've made your best effort to engage in the IP >> Due Diligence Process for all third party content before you engage with >> the EMO for review. Bear in mind that you should be engaging in the IP >> Due Diligence Process >> <https://www.eclipse.org/projects/handbook/#ip-third-party> on an >> ongoing basis and that all releases (regardless of whether or not they >> correspond with a progress or release review) must only contain content >> that has been vetted through the due diligence process. With the Eclipse >> Dash License Tool <https://github.com/eclipse/dash-licenses> and the >> ability to use it to automatically create review requests, it should be >> *easier >> than ever* before to engage (the README has extensive information on how >> to engage, and does include some pointers for using it with Eclipse Tycho >> <https://github.com/eclipse/dash-licenses#eclipse-tycho>-based builds). >> Connect with the EMO if you need assistance. >> >> Here are some things that I've observed: >> >> Eclipse Client Platform has been removed. >> >> The aggrcon files for the following projects are disabled; if any of >> these projects are dropping from the release, please let me know: >> >> - Eclipse Xpand >> - Eclipse BPMN2 Modeler Project >> - Eclipse RCPTT >> >> Let me know what I've missed. >> >> Thanks, >> >> Wayne >> -- >> >> Wayne Beaton >> >> Director of Open Source Projects | Eclipse Foundation >> >> >> My working day may not be your working day! Please don’t feel obliged to >> read or reply to this e-mail outside of your normal working hours. >> > > > -- > > Wayne Beaton > > Director of Open Source Projects | Eclipse Foundation > > > My working day may not be your working day! Please don’t feel obliged to > read or reply to this e-mail outside of your normal working hours. > _______________________________________________ > 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 >
_______________________________________________ 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
