Now that 2.0-rc5 is done.... What's next?

Remaining tasks

Critical isues

Major issues

Other

  • The subdirs issues aren't blocking release, as it's an 'experimental' feature, and can thus be re-factored within a stable release or 3.x, see #2046167: [META] Remaining issues with subsite support (Part II). Update: it seems there *are* issues with the current code, more than just refactoring, but we need an issue to clarify those issues. - the current code works well, although there are still some issues, but we won't block release on that.

Planning

Do we need another RC? Maybe, since there are so many critical issues!

We're good to go for 2.0.

One thing that still needs to be done is to change our release process documentation to switch to semver, i opened #2168955: switch to semantic versionning for that.

Comments

anarcat’s picture

anarcat CreditAttribution: anarcat commented

we'll release beta2 today.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

start beta

anarcat’s picture

anarcat CreditAttribution: anarcat commented

i struggled a bit more with the output stuff, and I believe we can have a fix. also note that it only affects hosting-queued and we have a workaround (chown aegir `tty` + interactive), so we could ship something that works for beta2...

anarcat’s picture

anarcat CreditAttribution: anarcat commented

i wanted to release this today, but i'm overwhelmed, postponing to tomorrow.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

link to the community site

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented

Updated the issue summary to reflect the post-beta2 reality.

anarcat’s picture

anarcat CreditAttribution: anarcat commented

test dump:

nevermind.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

Updated issue summary.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

meta

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Assigned: Unassigned » ergonlogic

we're in the process of releasing 2.0-rc1.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented
Assigned: ergonlogic » Unassigned

It took a while (due to weather-induced blackout), and learning to upload .debs, but RC1 is out.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented
Assigned: Unassigned » ergonlogic

As helmo pointed out, I messed up the RC1 packaging. I seem to have lost the updates to our drupal-org.make, so they're still pulling in beta2. I'll release RC2 shortly.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented
Assigned: ergonlogic » Unassigned

RC2 went out last night.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented
Issue summary: View changes

drush cc done

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Assigned: Unassigned » anarcat

next step: rc5. hopefully this week.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

update after rc4

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

update task list

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

add an issue, reshuffle

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

move some features out of experimental

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

fdsafdas

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
CreditAttribution: cweagans commented

What are the blockers for an RC5 release? I'd like to help get it out the door :)

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
CreditAttribution: cweagans commented
Issue summary: View changes

add upgrade path

helmo’s picture

helmo CreditAttribution: helmo commented

this link should give an overview of critical issues.

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
CreditAttribution: cweagans commented

Sure - are all of those blockers for an RC?

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented

No, those are blockers to a final 2.0 release. The blocker for rc5 is mostly time constraints amongst the core devs.

anarcat’s picture

anarcat CreditAttribution: anarcat commented

i uploaded a 5.10 package to the debian archive and the aegir unstable archive so we can fix #2002114: fix release process and scripts.

anarcat’s picture

anarcat CreditAttribution: anarcat commented

2.0-rc5 release notes here: http://community.aegirproject.org/2.0-rc5 - please review.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

Updated issue summary.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes

features out of experimental

anarcat’s picture

anarcat CreditAttribution: anarcat commented

alright, I fixed up the release stuff, we should now be able to use release.sh for a release again.

the only things remaining for the release (rc5) are:

* investigate upgrade path, in particular #2056741: Experiences upgrading from 1.10 and #2102455: Frontend missing after upgrade
* #2078531: ci.aegirproject.org loses jobs after every reboot: there still seems to be problems with jenkins and vagrant

But I feel we can release with those anyways. We are likely to require another RC because of the shaky release process change, but I am confident it will work properly.

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
CreditAttribution: cweagans commented

Looks good to me.

cweagans’s picture

cweagans
He/Him
Primary language English
Location Boise, ID, USA
CreditAttribution: cweagans commented
Issue summary: View changes

almost done!

helmo’s picture

helmo CreditAttribution: helmo commented

I went ahead and created 6.x-2.0 releases of hosting_site_backup_manager, provision_site_backup_manager, hosting_site_git

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Issue summary: View changes
helmo’s picture

helmo CreditAttribution: helmo commented
Issue summary: View changes
anarcat’s picture

anarcat CreditAttribution: anarcat commented

for the record, i released 1.11 with the security fixes, it would be a good time to release 2.0 as well.

helmo’s picture

helmo CreditAttribution: helmo commented

Lets just do 2.0, there will always be bugs... 2.1 can bring some fixes.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented

I agree. Let's get 2.0 released in 2013!

anarcat’s picture

anarcat CreditAttribution: anarcat commented

Well, today's the last day to do that if we want to. :)

anarcat’s picture

anarcat CreditAttribution: anarcat commented

Joking aside, I don't think it's a good idea to release today. Lots of people will be on vacation tomorrow, and I would hate to ring oncall sysadmins around the world because the 2.0 release went out...

helmo’s picture

helmo CreditAttribution: helmo commented

I don't think there's a real need for oncall admins to immediately install this.

I understand though. We've waited this long, no reason to rush it now.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented

So much for Aegir 2.0 in 2013. Oh well... :)

Anyway, I've started a draft for the 2.0 rel notes: http://community.aegirproject.org/2.0, based largely on the 1.0 notes. It's just a skeleton right now, and needs to have all the new features and improvements gathered, etc.

I see there's been some improvements lately :) I'll be reading up on them shortly. I'd also like to put up the new api.aegirproject.org soonish, and there some tests that need fixing. So, I'll try to find time for that in the coming days.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Title: [meta] 2.0 release » [meta] 2.0.0 release
Issue summary: View changes

I did a rush of changes in the release notes to integrate all the changes from all the release notes since the 1.x branch (in other words, all the 2.x releases), as we did for the 1.0 release.

It makes for an awesome release notes document, which really shows how many changes we have in this equally awesome release. :)

I also pushed ahead semantic versionning much further: this will become the 2.0.0 release, and the next bugfix release would be 2.0.1. If we have major changes, it would be 2.1.0, etc... More details in the release notes, but I thought I would mention it seperately here since it's a significant change, one that seemed originally to be targeted for 3.0.0 only, but that I think we should make current for 2.0.

I also explicitely announce 1.11 as the last release, unless there are changes required to fix the upgrade path.

So we're almost there - just need some documentation changes for semver, I opened #2168955: switch to semantic versionning about this.

anarcat’s picture

anarcat CreditAttribution: anarcat commented

i updated this page for 2.0:

http://community.aegirproject.org/content/branch-and-tagging-conventions

anarcat’s picture

anarcat CreditAttribution: anarcat commented

Another thing, that ergonlogic is taking on, is that we don't have the changes since rc5 yet.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
CreditAttribution: ergonlogic commented

I've added changes since rc5, all bug fixes. This replaces the list of bugfixes since the beginning of the 2.x dev cycle, as it was just too long :D.

anarcat’s picture

anarcat CreditAttribution: anarcat commented
Title: [meta] 2.0.0 release » [meta] 2.0 release
Status: Active » Fixed

2.0 is now released.

we updated hosting_platform_pathauto to 2.0 and should be shipping that with hostmaster, although right now there seems to be problem with that release: https://drupal.org/node/2169757 (look ma: no tarball!).

2.0 is in the unstable and testing repositories, we should copy it to stable once we are sure the upgrade won't explode anything.

the release notes have been officially published, as an event and a discussion post as well. and the frontpage of the site was updated. topic, irc and twitter announcements are also done.

anything else?

Status: Fixed » Closed (fixed)

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