| Re: [cross-project-issues-dev] OSSRH Service: Migration Plan (EOL June 30th, 2025) |
This is the typical message we encounter for some projects. Specifically those marked with a red cross that require Sonatype support.
For many of these projects, the message is relevant (e.g: glassfish). However, for others, such as Californium, my assumption is that the message may be misleading.
That said, in any case, we still need to coordinate the effort with Sonatype support.
Hope this helps.
Hi Sebastien,
I checked that spreadsheet, it marks "iot.californium" with a red cross.
What's the reason for that?
br
Achim
Am 22.05.25 um 16:50 schrieb Sebastien Heurtematte via
cross-project-issues-dev:
> Please find the spreadsheet that helps us to track the migration.
>
> https://docs.google.com/spreadsheets/d/19ClAQxS-ZGxP1rd-0CXadOPgMsJ38pute67DTgArVJ8
>
>
> On Thu, 22 May 2025 at 08:16, Lorenzo Bettini via
> cross-project-issues-dev <cross-project-issues-dev@xxxxxxxxxxx> wrote:
>
> Thanks for the updates!
>
> But how do we know how our projects are related to the metrics
> reported
> below?
>
> Lorenzo
>
> On 5/20/25 15:49, Sebastien Heurtematte via
> cross-project-issues-dev wrote:
> > Dear projects,
> >
> > This message is a follow-up to our previous communications
> regarding the
> > migration of Eclipse projects from *oss.sonatype.org
> <http://oss.sonatype.org> <http://
> > oss.sonatype.org <http://oss.sonatype.org>>*to the new Central
> Portal at sonatype:
> > *central.sonatype.org <http://central.sonatype.org>
> <http://central.sonatype.org>*.
> >
> > We are now sharing updated details on the migration plan, key
> dates, and
> > metrics based on the latest analysis of all Eclipse projects
> currently
> > published to OSSRH.
> >
> > Reminder: OSSRH Service End Of Life: June 30th, 2025
> >
> >
> ------------------------------------------------------------------------
> >
> >
> > Migration Metrics (as of today)
> >
> > We have reviewed all registered namespaces and project
> configurations:
> >
> > *
> >
> > 104 namespaces(91 projects) can be migrated automatically (no
> > Sonatype support needed)
> >
> > *
> >
> > 42 namespaces(31 projects) will require support from Sonatype
> >
> > *
> >
> > 11 projectshave an account on Central but no declared
> namespace. We
> > will follow up individually
> >
> > NOTE:Projects managing multiple namespaces may fall into both
> categories
> > above.
> >
> >
> ------------------------------------------------------------------------
> >
> >
> > Migration Timeline
> >
> > As the migration date approaches and we have not received
> confirmation
> > from Sonatype regarding a possible postponement, our focus is
> now to
> > carry out the migration as efficiently and reliably as possible.
> >
> > To achieve this, we are proposing a multi-step migration
> planadapted to
> > each project's needs, with the following key milestones:
> >
> > *
> >
> > Now → May 30: Feedback window – projects may opt out of the
> June 9
> > migration and be part of the second phase on June 24 Comment
> on the
> > migration ticket with a +1 from PL: OSSRH end-of-life on
> June 30th,
> > 2025
> <https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5854>
> >
> > *
> >
> > June 9: First migration batch – all projects (except those that
> > choose to opt out) will be moved to *central.sonatype.org
> <http://central.sonatype.org> <http://
> > central.sonatype.org <http://central.sonatype.org>>*
> >
> > *
> >
> > June 24: Final migration batch – for all***remaining*projects
> >
> > *
> >
> > July 1–4: Cleanup – OSSRH secrets removed, legacy accounts
> > deactivated, and obsolete configs cleaned up
> >
> > If your project needs to delay migration to June 24, please
> comment in
> > the GitLab ticket above no later than May 30.
> >
> > IMPORTANT: Regarding the previous post, we mentioned that
> projects would
> > be able to actively request a migration. This is no longer the case
> > under the new plan. All projects will now be handled in a global
> manner.
> >
> > If you have any concerns, please either open a new Helpdesk
> ticket or
> > comment in the top level migration
> ticket:<https://gitlab.eclipse.org/
> > eclipsefdn/helpdesk/-/issues/5854>OSSRH end-of-life on June
> 30th, 2025
> > <https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5854>
> >
> > Thank you again for your support and collaboration.
> >
> >
> > Best regards,
> >
> > *Sébastien Heurtematte*
> > *Release Engineer| Eclipse Foundation*
> > eclipse.org <http://eclipse.org> <https://www.eclipse.org/>| X
> <https://twitter.com/
> > EclipseFdn>| LinkedIn <https://www.linkedin.com/company/eclipse-
> > foundation/>| YouTube <https://www.youtube.com/user/EclipseFdn>|
> > Instagram <https://www.instagram.com/eclipsefoundation/>| Bluesky
> > <https://bsky.app/profile/eclipsefdn.bsky.social>| Mastodon
> <https://
> > mastodon.social/@EclipseFdn>
> >
> > Eclipse Foundation <http://www.eclipse.org/>: The Community for
> Open
> > Collaboration and Innovation
> >
> >
> >
> > _______________________________________________
> > 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
>
> --
> Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
> HOME: https://www.lorenzobettini.it
> TDD Book: https://leanpub.com/tdd-buildautomation-ci
> Xtext Book:
> https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
>
> _______________________________________________
> 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