From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Mlmmj 1.2.18a1 released
Date: Tue, 13 Mar 2012 12:14:26 +0000 [thread overview]
Message-ID: <4F5F3A22.3050206@yahoo.com.au> (raw)
In-Reply-To: <4F5E32B9.6090908@yahoo.com.au>
On 13/03/12 6:16 PM, Thomas Goirand wrote:
> On 03/13/2012 01:30 AM, Ben Schmidt wrote:
>> An alpha release for the upcoming Mlmmj 1.2.18 has been published.
>
> Hi!
>
> Why suddenly changing versioning scheme?
I didn't realise I changed anything.
> Does the "a" means alpha?
Yes, A is for alpha. Followed by B for beta, and RC for release
candidate. That's the system in my head, anyway.
> Later, if you publish 1.2.18.0, it's going to be considered smaller
> than 1.2.18a1, so I think it's not a nice numbering scheme
Well, that depends how you sort, doesn't it? What I've used is a fairly
common numbering system that a lot of packages use, so it wouldn't
surprise me if many sorting algorithms for version numbers dealt with it
OK. A simple ASCII sort won't though, it's true.
> (it might break upgrading in Debian, for example).
I'm not sure that an alpha release should be included in a distribution
anyway, to be honest.
> Something like:
>
> 1.2.18.0.rc1
>
> would have been better. Then, you would release 1.2.18.1 ...
I guess I probably should have had a hyphen in there, that's all.
1.2.18-a1 would be better, right? I'll do that for beta and beyond.
Cheers,
Ben.
next prev parent reply other threads:[~2012-03-13 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 17:30 [mlmmj] Mlmmj 1.2.18a1 released Ben Schmidt
2012-03-13 7:16 ` Thomas Goirand
2012-03-13 12:14 ` Ben Schmidt [this message]
2012-03-13 20:07 ` Lukas Fleischer
2012-03-15 11:51 ` Ben Schmidt
2012-03-17 12:16 ` Lukas Fleischer
2012-03-17 15:52 ` Ben Schmidt
2012-05-02 16:41 ` Quentin Heath
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=4F5F3A22.3050206@yahoo.com.au \
--to=mail_ben_schmidt@yahoo.com.au \
--cc=mlmmj@mlmmj.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.