25 Jun
2018
25 Jun
'18
7:03 p.m.
Hi Carl.
I'm just wondering how/when you go about merging commits from the test
version into stable branch?
For example, a feature request I made
(https://dcpomatic.com/mantis/view.php?id=1284) was implemented in test
version 2.13.19. Since then, stable 2.12.6 has been released but does
not contain this commit.
Stable releases since 2.12.2 are bug fix releases. However, what
confuses me is that there are many more bug fixes which have been
committed to the test branch. So there's obviously some criteria for
what makes it through to stable and what doesn't.
If you can be bothered, can you explain the release strategy a little
bit? And do you have a rough timeline of when the next stable release is
likely to be?
Just asking as I'm planning ahead to an upcoming festival and wondering
what version to settle on.
Many thanks,
Jim
25 Jun
25 Jun
10:20 p.m.
Hi Jim,
On Mon, 25 Jun 2018, Jim Dummett via DCPomatic wrote:
Hi Carl.
I'm just wondering how/when you go about merging commits from the test
version into stable branch?
It's a fairly ill-defined procedure. At the moment, if some commit either
1. probably fixes a nasty bug with no side-effects, or
2. almost certainly fixes a minor bug with no side-effects
I will put it into the stable branch. So far I haven't added many (or
any) feature requests into stable, but then
this is a fairly risk-free feature addition to a area of the code (the CLI
client) which is not very much used, so I could be persuaded to put it
into master ;)
Some of the test branch bug fixes are either
1. not certain to fix the bug, or
2. deep or complicated or in some way more likely to cause other breakages
At the moment the timeline is really just putting a finger in the air and
seeing how many commits there are to the release branch since the last
release. I'm happy to firm this up if it would help people.
Just asking as I'm planning ahead to an upcoming
festival and wondering
what version to settle on.
OK I'm fine with adding your --config patch to master and making 2.12.8
(2.12.7 has already been and gone) if that helps.
All the best,
Carl
6 Aug
6 Aug
7:19 p.m.
Hi Carl.
Sorry for very slow reply to this. Work has been crazy.
Damn I missed the 2.12.8 release! But yes would very much appreciate it
if you were willing to include the commit for specifying config file
location in CLI in the next stable release.
Thanks for explaining the releasing policy too. That makes sense.
From my point of view (just saying since you asked) there's no great
need for a roadmap of releases. I imagine that I'm fairly unusual in
using DCP-o-matic as part of an automated pipeline, where doing an
update may impact other parts of the system. So I'd probably be one of
the most likely to want a predictable release schedule. But I don't!
Many thanks,
Jim
On 25/06/2018 23:20, Carl Hetherington wrote:
2475
days inactive
2517
days old
3 comments
2 participants
participants (2)
-
Carl Hetherington -
Jim Dummett