: Wednesday, March 30, 2016 3:42 AM
To: devel@ntpsec.org
Subject: Re: Version bump.
dtpoi...@gmail.com said:
> Folks also use odd numbers for development branches and adding a dot
> release for new features.
I think we should seriously consider the odd-even aproach. That solves most
dtpoi...@gmail.com said:
> Folks also use odd numbers for development branches and adding a dot release
> for new features.
I think we should seriously consider the odd-even aproach. That solves most
of the ambiguity problem. It uses the bottom bit of a numeric slot to
indicate firm vs fuzz
On Mar 27, 2016 6:24 PM, "Chris Johns" wrote:
>
> On 26/03/2016 8:05 AM, Amar Takhar wrote:
>>
>> On 2016-03-25 13:51 -0700, Hal Murray wrote:
So, ntpd 0.9.2-afceec0+
>>>
>>>
>>> I'd put the + right after the 2:
>>>ntpd 0.9.2+afceec0 or ntpd 0.9.2+ if you build without git.
>>>
>>> M
On 26/03/2016 8:05 AM, Amar Takhar wrote:
On 2016-03-25 13:51 -0700, Hal Murray wrote:
So, ntpd 0.9.2-afceec0+
I'd put the + right after the 2:
ntpd 0.9.2+afceec0 or ntpd 0.9.2+ if you build without git.
My normal mode of operation is to have a master copy on one system, rsync to
other sys
On 2016-03-25 13:51 -0700, Hal Murray wrote:
> > So, ntpd 0.9.2-afceec0+
>
> I'd put the + right after the 2:
> ntpd 0.9.2+afceec0 or ntpd 0.9.2+ if you build without git.
>
> My normal mode of operation is to have a master copy on one system, rsync to
> other systems dropping the .git directo
> So, ntpd 0.9.2-afceec0+
I'd put the + right after the 2:
ntpd 0.9.2+afceec0 or ntpd 0.9.2+ if you build without git.
My normal mode of operation is to have a master copy on one system, rsync to
other systems dropping the .git directory to save space and time, and then
build there.
(.git is
Folks also use odd numbers for development branches and adding a dot release
for new features.
Even numbers are for release branches with dot releases for maintenance
release.
Increment in the version number would indicate a major milestone.
The '-v' command line switch should report the sh
Amar Takhar :
> On 2016-03-25 09:47 -0400, Eric S. Raymond wrote:
> > Amar Takhar :
> > > Advancing the version stops that confusion.
> >
> > Another praxtice often used is to append "+" to the version after a release.
>
> Oh? I've never heard of that interesting. I will throw that in it can't
On 2016-03-25 09:47 -0400, Eric S. Raymond wrote:
> Amar Takhar :
> > Advancing the version stops that confusion.
>
> Another praxtice often used is to append "+" to the version after a release.
Oh? I've never heard of that interesting. I will throw that in it can't hurt.
I'm going to throw
Amar Takhar :
> Advancing the version stops that confusion.
Another praxtice often used is to append "+" to the version after a release.
--
http://www.catb.org/~esr/";>Eric S. Raymond
___
devel mailing list
devel@ntpsec.org
http://lists.
On 2016-03-24 23:18 -0700, Hal Murray wrote:
>
> I don't see how the next version is any better than the previous one. It may
> seem that way to you, but it will be just as logical to somebody else who
> gets started the other way.
Because what is in master right now *is* 0.9.3. It's very com
v...@darkbeer.org said:
>> 0.9.3 isn't right either. It will look like the real 0.9.3
> I can change it to add a revision to the version number. But there is no
> other way to denote the next version all the current changes go into 0.9.3
> so it is the correct number to use.
I don't see how t
On 2016-03-24 21:47 -0700, Hal Murray wrote:
>
> v...@darkbeer.org said:
> > devel shouldn't be at 0.9.2 still as it has already been released. This
> > will make the snapshots easier to understand as users are always testing the
> > next release not the current.
>
> 0.9.3 isn't right either.
v...@darkbeer.org said:
> devel shouldn't be at 0.9.2 still as it has already been released. This
> will make the snapshots easier to understand as users are always testing the
> next release not the current.
0.9.3 isn't right either. It will look like the real 0.9.3
I think we need some cons
14 matches
Mail list logo
