It's not really up to me. I suppose that we could think of Eclipse JustJ as something that the package project pulls in, but it should IMHO have a proper place in the simultaneous release. It serves us well to include it (and not including it will lead to weird "what does it mean to be in the simultaneous release then anyway" sorts of discussions). FWIW (and more for other random observers, because I know that you know this), there's no rule that says that participating projects must contribute bits for the shared p2 repository.
So... since we're well past M1, I'll need Planning Council approval to add it. Can I get a couple of +1s from Planning Council members on this thread please? For completeness, +1 from me (and as assumed +1 from Ed). Wayne On Fri, Aug 28, 2020 at 12:11 AM Ed Merks <ed.me...@gmail.com> wrote: > Wayne, > > You may wish to add JustJ: > > https://projects.eclipse.org/projects/technology.justj/releases/1.0 > > While it is not in the release train p2 repo, it is incorporated into the > Eclipse Installer and into three of the EPP packages. > > Regards, > Ed > > On 27.08.2020 20:50, Wayne Beaton wrote: > > I've created the tracking page for 2020-09 > <https://projects.eclipse.org/releases/2020-09>. Please have a look to > ensure that I've correctly recorded your project's participation correctly. > > In particular, please make sure that I have the version right. If I've > made a mistake... please first make sure that you've created a release > record for the right version and then let me know to update the tracking > page to point to that version. > > If you are contributing a new major or minor release and have not engaged > in a release review since September 16/2019, then you need to submit your > IP Log and connect with EMO ASAP to initiate the release review process. > Note that you only need to submit your IP Log for review if you are > required to engage in a release review. There's more information in the > handbook <https://www.eclipse.org/projects/handbook/#release>. > > Based on messages on this list, both Eclipse Corrosion, Eclipse EMFStore, > and Eclipse Tools for Cloud Foundry (CFT) have dropped out, so they've been > removed from the list. > > *AFAICT, the corrosion.aggrcon file still exists and is not disabled.* Also, > since CFT has dropped out, its aggrcon file should also be removed (not > just disabled). Can somebody take care of that, please? > > Thanks for all your efforts. > > 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 listcross-project-issues-...@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 > -- 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-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
