We have enough bugs fixed to warrant a new bugfix release.

Currently included:

Specifically excluded:

Postponed to further release:

Full up to date list of 3.1 issues.

Please rewrite this description and re-tag as needed.

I'm guessing this release won't happen before next Thursday (August 13th), since that's when the weekly meeting is, which gives everyone at least week to talk and add to this.

Comments

gboudrias created an issue. See original summary.

gboudrias’s picture

Issue tags: -Aegir 3.0.1 +Aegir 3.0.2
gboudrias’s picture

Title: [meta] 3.0.1 (bugfix) release » [meta] 3.0.2 (bugfix) release

We already have 3.0.1, this would be 3.0.2.

gboudrias’s picture

Title: [meta] 3.0.2 (bugfix) release » [meta] 3.1 release (bugfix/patches)
Issue tags: -Aegir 3.0.2 +Aegir 3.1

As ergonlogic mentionned, contrib doesn't have semver yet...

gboudrias’s picture

Issue summary: View changes

Updated description. Please help clarify unclear cases.

I tagged all "Reviewed and tested" and most "Needs review" as Aegir 3.1.

I excluded all "needs work" issues except #2347557: No systemd service file for queue runner (which is probably a blocker), as we already have a lot to review for a single release. Here they are, if anyone wants to fix something before 3.1. I ignored "active" issues, which I take to mean either unreviewed or unfixed.

gboudrias’s picture

Issue summary: View changes

Added a bunch of golden contrib issues.

gboudrias’s picture

Issue summary: View changes

Some issues have been clarified.

cweagans’s picture

Category: Task » Plan
ergonlogic’s picture

@gboudrias, thanks for taking this initiative.

I'm not sure how realistic it is to include all these items in 3.1, if we're targeting a release this week. Certainly all the RTBC issues should be included, assuming tests succeed. On the other hand, if these are all somewhat close to RTBC, then perhaps a better approach would be to start working through these, and release 3.1 When It's Ready™:)

FWIW, I think there's enough for a 3.1 release as is, and the rest can be worked on for an upcoming 3.2 release.

gboudrias’s picture

The main blocking issue in my mind is #2347557: No systemd service file for queue runner, everything else seems mostly optional, so we can see what made it to RTBC once this is fixed. I think a lot of issues will be pretty quick to review.

I think we should aim for August 20th to give everyone at least this week to review what they can. I know it would suit me personally at least, as my Aegir day is Thursday and the release would likely take all day.

helmo’s picture

Issue summary: View changes

Combining with a duplicate issue I had created... #2540004: Release a 7.x-3.1 bugfix release

gboudrias’s picture

Issue summary: View changes

Issues have been clarified. See description.

helmo’s picture

Issue summary: View changes
gboudrias’s picture

Issue summary: View changes

Removed duplicate issue.

helmo’s picture

Issue summary: View changes
gboudrias’s picture

gboudrias’s picture

I think it's safe to postpone the issues that haven't been reviewed to 3.2.

gboudrias’s picture

Issue summary: View changes

Moved postponed issues into their own list.

gboudrias’s picture

Issue summary: View changes

Postpone provision issue.

helmo’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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