Bug #2199
To have "stable" and "testing" tracking branches, like andoma/showtime
0%
Description
Hi,
This would help new users particularly, who cannot know if master is currently broken.
For an explanation for how it might work, pls look at the showtime project, how andoma did it there.
You may have 2 or 3 branch (including master). Just depending if you feel it worth the hassle to maintain either 1 or 2 more stable branch behind head.
In showtime they are called "testing" and "stable".
This since my IRC conversation with negge:
[10:12] < dreamcat4> negge i suspect they DONT tag anymore because they announced 'next future version is 4' and have used up all tags too '3.9'
[10:13] < dreamcat4> so it becomes less helpful to tag like 3.901 -> 3.99 with including so many new features since "3.9"
[10:13] < dreamcat4> it is over 1000 commits since 3.9 tag
Many thanks for considering this.
I know it's extra effort / overhead.
History
Updated by Dreamcat 4 over 10 years ago
Updated by It looks like indeed @perexg is indeed maintaining a 'testing' branch.
https://github.com/tvheadend/tvheadend/commits/testing
Was not previously aware of that. But great!
It may not be as solid as something called 'stable'. But this testing branch seems to be well kept in recent times. And part of the development cycle, not some stale branch.
In regards to 'stable'. It's likely the case that @perexg, who spending his life in HEAD isn't well placed enough person to feel confident to update a 'stable' branch. So maybe others (who are more like packages or long-term users) with a commit access to the same repo would be more appropriate peoples to maintain such 'stable' branch.
If not then we still have @perexg's 'testing' line for new users to jump onto. And others more afraid of master.
Many thanks.
Updated by Adam Sutton almost 10 years ago
Updated by - Status changed from New to Invalid
Closing this, it doesn't really need logging as a "bug". We know we need to sort out out release management and get back to something more sane.