Permanent Current Release Plan #51

Open
opened 2021-01-20 12:48:20 +00:00 by lambadalambda · 1 comment

This issue is meant for constant planning of the current state of the next release. Looking it at should always give you the overview of what's happening and when the release is expected.

General Rules

These rules are meant to ensure a continuous stream of releases and to prevent dropping a lot of new features and changes on users. This will make debugging user issues easier and will prevent a too great divergence between our stable and development branches.

  1. Patch releases are done as needed.
  2. Feature releases are done every 8 weeks. A 'feature freeze' in the development branch for one or two weeks before release is suggested.
  3. Delays in the feature release process don't delay the next release. That is, if a release is late by 2 weeks, the time to the next release will be 6 weeks.
  4. Currently, @rinpatch and @lambadalambda are responsible for the release process.

Upcoming release dates:

This issue is meant for constant planning of the current state of the next release. Looking it at should always give you the overview of what's happening and when the release is expected. ## General Rules These rules are meant to ensure a continuous stream of releases and to prevent dropping a lot of new features and changes on users. This will make debugging user issues easier and will prevent a too great divergence between our stable and development branches. 1. Patch releases are done as needed. 2. Feature releases are done every 8 weeks. A 'feature freeze' in the development branch for one or two weeks before release is suggested. 3. Delays in the feature release process don't delay the next release. That is, if a release is late by 2 weeks, the time to the next release will be 6 weeks. 4. Currently, @rinpatch and @lambadalambda are responsible for the release process. ## Upcoming release dates: - 2.3 (2021-03-01) [Milestone MRs](https://git.pleroma.social/pleroma/pleroma/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&milestone_title=2.3.0), [Milestone Issues](https://git.pleroma.social/pleroma/pleroma/-/issues?scope=all&utf8=%E2%9C%93&state=opened&milestone_title=2.3.0) - 2.4 (2021-04-26) - 2.5 (2021-06-21)
Owner

should we document various steps needed to do in practice for every release? just in case we need to do a release while key members are away

should we document various steps needed to do in practice for every release? just in case we need to do a release while key members are away
Sign in to join this conversation.
No labels
BE
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/pleroma-meta#51
No description provided.