Plan for 8.x-1.x (D10) unstable release

Created on 16 December 2022, about 2 years ago
Updated 20 April 2024, 8 months ago

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

📌 Task
Status

Active

Version

1.0

Component

Code

Created by

🇩🇪Germany c-logemann Frankfurt/M, Germany

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024