[ntp:hackers] hackers] Post 4.2.8 Release Number Scheme
Brian Utterback
brian.utterback at oracle.com
Fri Jan 3 00:48:43 UTC 2014
Okay, so it would seem that we would rev the stable and dev sets pretty
much simultaneously, right?
The use of the stable branch seems to alternate between too much and too
little activity. I remember a few years ago when almost every changeset
was pulled over into the stable branch, including some that added
features. This time around, in the last two years there wasn't a single
bug fix that was pulled over into the stable branch. Maybe there should
be a field in bugzilla that says "Should this be pulled over into the
stable branch, yes or no?" and we don't commit anything until it is
filled out one or the other.
On 1/2/2014 7:42 PM, Harlan Stenn wrote:
> Greg Troxel writes:
>> Harlan Stenn <stenn at ntp.org> writes:
>>
>>> Cutting a release means:
>>>
>>> ntp-dev-4.2.5pNNN-RC gets some changes to packageinfo.sh and becomes
>>> ntp-4.2.6 in the -stable repo.
>>>
>>> After that release fully rolls I pull -stable into -dev, and make some
>>> changes to packageinfo.sh in ntp-dev and release ntp-dev-4.2.7p0.
>> Earlier you said that the package name was "ntp4", following the example
>> on the wiki, but here it is "ntp".
> Yes, I gave examples of what we have been doing, so folks would have an
> easier time understanding it.
>
> ntp-4.2.6p3 would be ntp4-2.6.3 in the new scheme - the values should
> translate quite easily. Similarly, ntp-dev-4.2.7p300 would be
> ntp4-dev-2.7.300 .
>
> H
More information about the hackers
mailing list