|Re: [orbit-dev] [Bug 568936] Remove remaining CVS defined bundles from Orbit recommended builds starting in 2022-06|
Hello folks,I am working on this now - some of the scripts are a little brittle and hard to test locally. Therefore I am doing a series of commits directly to master. This isn't my ideal workflow as the master branch is now a little bit broken until I resolve all the issues. I hope to resolve all the issues and get the M1 out soon. Note that one of the differences is that I have migrated all the scripts that the build process uses into git - they were previously stored in a combination of Jenkins and https://download.eclipse.org/tools/orbit/commonFiles dating back to a time when committers had shell access.That said, there have been no bundle changes since 2022-03 R, so all 2022-06 M1 will be is the same bundles in the new structure.Announcement as soon as I get it working.JonahOn Tue, 22 Feb 2022 at 22:32, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:Hello folks,Starting with 2022-06 M1 the Orbit repo will no longer be a composite repo combining the old CVS build with the latest git based build.The 2022-03 recommended build will be the last to contain these old CVS bundles.Please comment on the bug if this causes you any concerns, or would like to voice your support.Thanks,Jonah---------- Forwarded message ---------
Date: Tue, 22 Feb 2022 at 22:29
Subject: [Bug 568936] Remove remaining CVS defined bundles from Orbit recommended builds starting in 2022-06
Product/Component: Orbit / bundles
Jonah Graham <jonah@xxxxxxxxxxxxxxxx> changed:
What |Removed |Added
Summary|Move remaining CVS defined |Remove remaining CVS
|bundles to git |defined bundles from Orbit
| |recommended builds starting
| |in 2022-06
Target Milestone|--- |2022-06
--- Comment #7 from Jonah Graham <jonah@xxxxxxxxxxxxxxxx> ---
After discussing with various stakeholders, including at the Planning
Council the current plan is to instead of migrating all these bundles is to
just deprecate the CVS versions.
Projects consuming the CVS versions of the bundles can point to the last
release containing them (will be 2022-03 recommended build*) and/or update the
git repo to include them, or better yet consume directly from Maven Central.
Therefore the plan is from 2022-06 M1 the CVS component of this Orbit repo will
* please recall that "R" builds in Orbit means recommend, not release.
You are receiving this mail because:
You are the assignee for the bug.
You reported the bug.
You are on the CC list for the bug.
Back to the top