From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] versioning
Date: Wed, 18 Feb 2015 05:35:40 -0500 [thread overview]
Message-ID: <20150118053540.eklhad@comcast.net> (raw)
> 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
next reply other threads:[~2015-02-18 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 10:35 Karl Dahlke [this message]
2015-02-18 14:18 ` Chris Brannon
2015-02-18 22:32 ` Adam Thompson
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=20150118053540.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.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).