On Mon, 5 Dec 2016 12:07:25 -0800
Hans Wennborg via lldb-dev wrote:
> On Mon, Dec 5, 2016 at 12:02 PM, Renato Golin wrote:
> > On 5 December 2016 at 19:56, Hans Wennborg wrote:
> >> I'd like to avoid 4.1 because of the
On 5 December 2016 at 20:07, Hans Wennborg wrote:
> I'm worried that users will, with some reason, think that the 4.1 and
> 5.1 releases are the same kind as 2.1 and 3.1 :-/
IMO, this is too small of a worry to encumber us for the rest of our
release days with silly zeroes.
On Mon, Dec 5, 2016 at 12:02 PM, Renato Golin wrote:
> On 5 December 2016 at 19:56, Hans Wennborg wrote:
>> I'd like to avoid 4.1 because of the potential for confusion about
>> whether it's a major release (as it would have been under the old
>>
On 5 December 2016 at 19:56, Hans Wennborg wrote:
> I'd like to avoid 4.1 because of the potential for confusion about
> whether it's a major release (as it would have been under the old
> scheme) or a patch release.
But if the versioning scheme is different, users will have
On Mon, Dec 5, 2016 at 11:00 AM, Renato Golin wrote:
> On 5 December 2016 at 18:56, Hans Wennborg via Release-testers
> wrote:
>> The idea is that Tom's stable releases will keep incrementing the
>> "patch" part of the version numbers,
On 5 December 2016 at 18:56, Hans Wennborg via Release-testers
wrote:
> The idea is that Tom's stable releases will keep incrementing the
> "patch" part of the version numbers, just as today, so they would be
> 4.0.1, 4.0.2, etc.
Hum, this looks weird. I was under
On 5 December 2016 at 18:42, Dimitry Andric via Release-testers
wrote:
> Maybe I didn't pay enough attention, but where is the general outline
> for this versioning scheme documented? And are we still going to do
> 4.1, 4.2, etc?
This is the thread: