From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] versioning
Date: Wed, 18 Feb 2015 22:32:56 +0000 [thread overview]
Message-ID: <20150218223256.GB32332@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87h9ujl2vn.fsf@mushroom.localdomain>
[-- 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 --]
prev parent reply other threads:[~2015-02-18 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 10:35 Karl Dahlke
2015-02-18 14:18 ` Chris Brannon
2015-02-18 22:32 ` Adam Thompson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150218223256.GB32332@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=chris@the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).