Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
R
Release
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • Release
  • Issues
  • #14

Closed
Open
Opened Mar 12, 2020 by MikeyMJCO@MikeyMJCODeveloper

Document the process for pulling or skipping/missing releases

When we skip or pull a release we should have a policy that dictates followup notifications/communications.

Recent examples include 5.23 (WordPress) 5.23.1 (Joomla) and the remove/release of one of the earlier 5.x.x versions. We should have a standard, transparent, open communication policy that announces these decisions and the reasons as soon as practicably possible after the decision is taken.

Currently there is no policy on this and the communication is spotty/unreliable. I'm willing to put my "money where my mouth is" on this and I'll volunteer to write short blog posts when this happens if it's useful - so I don't mind putting in the effort - I'd just like us to debate and agree a coordinated policy on this!

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/release#14