[Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17
Simon.Hausmann at qt.io
Tue Apr 11 17:13:42 CEST 2017
I think that what you are asking for is reasonable. I think the set of sha1s of qt5.git satisfy that requirement to the best of the project's ability.
Why would the tip of the 5.8 branch of all modules be superior to for example the sha1s of qt5's 5.9 branch at this point?
For users of the product we can only point to tags. For developers all active branches should be good enough. I find it hard to imagine introducing a third "level" that is good enough for "some" but clearly not all. Unless there is a consensus to define and introduce this new way of identifying a development branch.
On 11. Apr 2017, at 16:59, Stottlemyer, Brett (B.S.) <bstottle at ford.com> wrote:
>> On 4/11/17, 9:49 AM, "Development on behalf of Tuukka Turunen" <tuukka.turunen at qt.io> wrote:
>> Now that there are no patch releases planned, the benefit from pushing to 5.8 then merging to 5.9 does not exist.
> I feel there should always be a stable HEAD that you can push a fix to and expect to be able retrieve and do a rebuild with that fix. Is that unreasonable?
> Right now, the only branch that meets that criteria is 5.8, so I disagree there is no benefit to it.
> Whether it is worth the effort is a different question. I'm simply trying to make the point that the value doesn't go to zero because there isn't another planned release from that branch.
> Development mailing list
> Development at qt-project.org
More information about the Development