Problem/Motivation

I've been asked for an unstable but soon release. But a release is something people like to have a stable API etc. This is one of the main reasons I'm careful with creating a release.

Proposed resolution

I'm open to create a unstable 8.x-1.0-alpha release to move on. But when I do this early I like to stop working on 8.x-1.x-dev branch.
By myself I will switch to a 2.x branch with a plan to get a 2.0 stable release. With this strategy people get their first unstable release and we can move on with improvements where we don't have to look on logic and api changes.

Remaining tasks

Comments

C-Logemann created an issue. See original summary.

c-logemann’s picture

Issue tags: -Plan for 8.x-1.x (D9/D10) unstable release
Related issues: +#3292832: Plan for 2.0 D10/D11 stable release
c-logemann’s picture

Issue summary: View changes
c-logemann’s picture

Issue summary: View changes
c-logemann’s picture

Title: Plan for 8.x-1.x (D9/D10) unstable release » Plan for 8.x-1.x (D10) unstable release
c-logemann’s picture

c-logemann’s picture

Title: Plan for 8.x-1.x (D10) unstable release » Plan for 8.x-1.x (D10/D11) unstable release
Issue summary: View changes
c-logemann’s picture

c-logemann’s picture

Issue summary: View changes
c-logemann’s picture

Status: Active » Needs work
joseph.olstad’s picture

Status: Needs work » Reviewed & tested by the community

Previous blocker is RTBC
#3325126: Boost Cacheability Settings functionality fix

Awesome work c-logemann, just needed a tiny bit more pepper to the sauce.

c-logemann’s picture

Assigned: c-logemann » Unassigned
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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