Re: [Alioth-staff-replacement] alioth deprecation - next steps
- Date: Thu, 26 Apr 2018 10:52:41 +0200
- From: Alexander Wirt <formorer@xxxxxxxxxxx>
- Subject: Re: [Alioth-staff-replacement] alioth deprecation - next steps
On Thu, 26 Apr 2018, Andrej Shadura wrote:
> On 26 April 2018 at 10:21, Alexander Wirt <formorer@xxxxxxxxxxx> wrote:
> > On Thu, 26 Apr 2018, Andrej Shadura wrote:
> >> On 17 April 2018 at 13:00, Alexander Wirt <formorer@xxxxxxxxxx> wrote:
> >> > Hi,
> >> >
> >> > as you should be aware, alioth.debian.org will be decommissioned with
> >> > the EOL of wheezy, which is at the end of May. The replacement for
> >> > the main part of alioth, git, is alive and out of beta, you know it
> >> > as salsa.debian.org. If you did not move your git repository yet,
> >> > hurry up, time is running out.
> >> >
> >> > The other important service from the alioth set, lists, moved to a
> >> > new host and is now live at https://alioth-lists.debian.net .
> >> > All public list archives moved over too and will continue to exist
> >> > under the old URL.
> >> >
> >> > ## decommissioning timeline
> >> >
> >> > 01.05.18: DISABLE registration of new users on alioth. Until an improved SSO (GSOC Project, see ) is ready, new user registrations
> >> > needed for SSO services will be handled manually. More details on this will follow in a seperate announcement.
> >> > 10.-13.05.18: darcs, bzr and mercurial repositories will be exported as tarballs and made available readonly from a new archive host,
> >> > details on that will follow.
> >> > 17.-20.05.18: During the Mini-DebConf Hamburg any existing cron jobs will be turned off, websites still on alioth will be disabled.
> >> > 31.05.18: All remaining repositories (cvs, svn and git) will be archived similar to the ones above.
> >> > The host moszumanska, the home of alioth, will go offline!
> >> Could the steps including taking VCS repos offline be offset by at
> >> least two months? There are too many packages not yet migrated to
> >> Salsa or to Git in general, and completing that by the end of May is
> >> putting too much pressure on the maintainers.
> > Nope, we announced that months, if not years ago.
> That doesn’t seem like a reasonable reply. What was announced is one
> thing, but the plans have to be adjusted to the reality, which is that
> you cannot switch off the VCS hosting by the end of May.
It is. The plans were announced, I blocked the dates (I am even on vacation
for that) and the system is EOL with end of may. It will go down then.