Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
W
weston
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 275
    • Issues 275
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 116
    • Merge Requests 116
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • wayland
  • weston
  • Issues
  • #396

Closed
Open
Opened Apr 30, 2020 by Pekka Paalanen@pqMaintainer

Always create stable branches?

This is prompted by !418 (closed).

Maybe stable branches should always get created when master opens up for new development after a release?

Otherwise people cannot cherry-pick patches and submit MRs for stable branches, which means we basically stop any stable branch maintenance from ever occurring.

If people were able to submit MRs against stable branches, reviewing those MRs should be a breeze most of the time (Did it use git cherry-pick -x? Is it only a bug fix?). If contributors help pick the patches for stable branches, maybe the release manager doesn't need to do anything more than cut releases sometimes.

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