to do proper testing and support for the 2.x branch, we should have a set of debian packages uploaded for it.

it should probably be done in a separate debian archive.

Comments

anarcat’s picture

Status: Active » Needs work

I started working on this. I added a "experimental" distribution to the debian archive where alpha releases and similar garbage can be uploaded. :) Now onto the actual alpha1 release.

anarcat’s picture

Title: publish debian packages for 2.x » publish debian packages for 2.x and 2.0-alpha1
Version: 7.x-2.x-dev » 6.x-2.x-dev
Assigned: Unassigned » anarcat

So - more progress here.

Release notes are available here: http://community.aegirproject.org/2.0-alpha1

I am still unsure the experimental repository is the right approach. I am thinking now we should just *rename* the debian package to "aegir2" and conflict/replace with the regular debian packages. That would allow us to upload both packages in the same repository. I am not sure, however it would make the upgrade possible, although that would need to be tested.

Hum.

anarcat’s picture

So yeah, after thinking about it more, there are two options:

* make a separate repository for 2.x (debian2.aegirproject.org?)
* make a separate *package* for 2.x (aegir2, aegir-provision2, aegir-hostmaster2, etc)

I think I would prefer the latter - people wouldn't have to fiddle with their sources.list to upgrade, they would just need to apt-get install aegir2...

This needs to be tested though, so it's holding off the release.

anarcat’s picture

Status: Needs work » Needs review

I got code here that renames the whole packages to *2. It's kind of ugly, but it works, and the upgrade works too.

I think that's the way to go, but i'll sleep on it.

anarcat’s picture

An offshoot of this: #1912238: automatically build and upload aegir 2.x packages - note that I'll build the alpha1 packages by hand for now, but they will be uploadable to the archive directly, so we need an autobuilder there too.

anarcat’s picture

Status: Needs review » Fixed

alright, i released the damn thing.

a few things I didn't do in the release process:

  • Update the version in the script upgrade page
  • A link to the release notes on the frontpage block
  • pull the debian packages into the stable release channel (they stay in unstable)
  • test the debian package upgrade (it's broken)

phew!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.