[Edbrowse-dev] versioning

[Edbrowse-dev] versioning

[Karl Dahlke]

> do we want to decide what is going to go in the next version
> and whether that wants to stay a 3.5 (or even really a 3 for that matter).

A good point - presetting a version number is a form of prognostication,
of which I have never been very good.
Our mode has been to make a bunch of changes, stop and take a breath,
look back, and set a new version based on what we did.
Not sure we can work any other way.
So maybe we call it 3.5.3.plus,
and when we're done we'll advance it to something else.
If we do indeed start using a library we didn't use before, I think,
subjectively, more an art than a science, that we jump to 3.6.0.

Karl Dahlke

Re: [Edbrowse-dev] versioning

[Chris Brannon]

Karl Dahlke <eklhad@comcast.net> writes:

> A good point - presetting a version number is a form of
> prognostication,

If we used 3.5.4.git, this is just a guess at what
the next version number might be, and we can change that guess if we
need to do that.
I'd be fine with something like 3.5.3+, though, since it indicates that
we're working on whatever comes after 3.5.3.

-- Chris

Re: [Edbrowse-dev] versioning

[Adam Thompson]

[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]

On Wed, Feb 18, 2015 at 06:18:20AM -0800, Chris Brannon wrote:
> Karl Dahlke <eklhad@comcast.net> writes:
> 
> > A good point - presetting a version number is a form of
> > prognostication,
> 
> If we used 3.5.4.git, this is just a guess at what
> the next version number might be, and we can change that guess if we
> need to do that.
> I'd be fine with something like 3.5.3+, though, since it indicates that
> we're working on whatever comes after 3.5.3.

Same here, I don't really mind either way.
There're so many different ways to do version strings that this could turn into
a *very* long discussion. I've always quite liked the year.release.bugfix
numbering myself (i.e. 2015.1 or 2015.1.1 if we have a minor bug that we fix)
but again I don't particularly care.
I equally see the benefit of 3.5.4.git or 3.5.3+ which can then be changed to
3.6 if we make the major changes we have planned, or 3.5.4 if we don't  (though I'd have a minor
preference for 3.5.3+ if I had to choose between the two).

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]