From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: (release) versioning
Date: Wed, 6 May 2015 11:57:54 +0100 [thread overview]
Message-ID: <5549F3B2.9030007@citrix.com> (raw)
In-Reply-To: <554A0E850200007800077104@mail.emea.novell.com>
On 06/05/15 11:52, Jan Beulich wrote:
>>>> On 06.05.15 at 12:37, <david.vrabel@citrix.com> wrote:
>> On 06/05/15 08:25, Jan Beulich wrote:
>>>>>> On 06.05.15 at 09:21, <wei.liu2@citrix.com> wrote:
>>>> One exceptional situation is that we had 4.1.6 and 4.1.6.1. I don't
>>>> expect that to happen very often, but we do make mistakes in the release
>>>> process and figure out we need to release a slightly updated version.
>>>> How does this fit into the proposed scheme?
>>>
>>> I think we would just attach a .1 to the previous version the same
>>> way we did there, i.e. 5.2.0.1.
>>
>> What happens if this minor fixup itself needs a micro fixup? Do we then
>> have 5.2.0.1.1? etc. etc.
>
> No, that would (naturally I would say) become 5.2.0.2.
>
>> Why not always bump the minor version regardless of how small the change
>> was?
>
> That's certainly an option, but we chose the other route on the one
> occasion when we needed it.
Fair enough, I don't really mind.
David
next prev parent reply other threads:[~2015-05-06 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 15:54 (release) versioning Jan Beulich
2015-05-05 17:05 ` Andrew Cooper
2015-05-05 23:15 ` Dario Faggioli
2015-05-06 11:54 ` Jan Beulich
2015-05-06 12:45 ` Dario Faggioli
2015-05-06 7:21 ` Wei Liu
2015-05-06 7:25 ` Jan Beulich
2015-05-06 10:37 ` David Vrabel
2015-05-06 10:52 ` Jan Beulich
2015-05-06 10:57 ` David Vrabel [this message]
2015-05-06 9:02 ` Ian Campbell
2015-05-06 10:12 ` Jan Beulich
2015-05-06 10:21 ` Ian Campbell
2015-05-06 14:58 ` Konrad Rzeszutek Wilk
2015-05-06 15:19 ` George Dunlap
2015-05-06 15:01 ` George Dunlap
2015-05-06 15:44 ` Jan Beulich
2015-05-06 15:55 ` Lars Kurth
2015-05-07 10:54 ` Tim Deegan
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=5549F3B2.9030007@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.