Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

our releases break too many user sites #1628

Copy link
Copy link
Open
@drammock

Description

@drammock
Issue body actions

Every time we push out a release, a flood of new issues comes in. As a maintainer I feel responsible to fix them, but as a maintainer with other, higher-priority responsibilities I don't really have time to drop everything and make hotfixes.

For our most recent release I suggested we do an RC, which happened, but then a full release was done almost immediately (AFAICT after only one user site had tested it). In my mind that defeats the purpose of an RC, which is to give several test users time to try it and find bugs, so that we have time to fix those bugs at our own pace before those bugs break all user's sites.

I'd like to propose a change to our release process, which is to always require and RC and to set a mandatory minimum delay between the RC and the full release.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs: discussionNeeds discussion before an implementation can be madeNeeds discussion before an implementation can be madetag: team processTeam process, governance, and guidelinesTeam process, governance, and guidelines

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.