Coming Soon: Stable D Releases!

[Adam Wilson]

On Tue, 24 Jul 2012 11:41:52 -0700, Leandro Lucarella <luca at llucax.com.ar>  
wrote:

> Adam Wilson, el 23 de July a las 11:07 me escribiste:
>> On Mon, 23 Jul 2012 01:52:57 -0700, Leandro Lucarella
>> <luca at llucax.com.ar> wrote:
>>
>> >Adam Wilson, el 22 de July a las 16:05 me escribiste:
>> >>I can't really say, but it sounds like what you are asking for is
>> >>D2/D3, thats not really the scope of the dlang-stable project, we
>> >
>> >Nope! What I'm talking about is D 2.1, 2.2, etc. Not D3. As somebody
>> >said before in this thread talking about PHP, minor version changes in
>> >the languages should only introduce backward compatible new features.  
>> D3
>> >should be allowed to break backward compatibility while D 2.1 should
>> >not. The same is done in Python. In Python is even allowed to break
>> >backward compatibility in very small and are cases, like introducing
>> >a keyword. In those cases the changes are introduced in steps, let's  
>> say
>> >in Python 2.5 with is not a keyword and they want to convert it to
>> >a keyword. Then in Python 2.6 you have an option to enable that
>> >behaviour (disabled by default) and in Python 2.7 the new feature will
>> >be enabled by default. Python 2.5.1 can only introduce bugfixes.
>>
>> Minor release ARE what we are hoping for, but you'll have to
>> convince Walter and company to move to that scheme, it's out of my
>
> Are you talking about the development model or just the version naming
> scheme?
>
>> control. For the moment, we will be using a scheme that looks like
>> 2.60.1. Which may be what you are talking about. When it's time to
>> roll in the new features and breaking fixes the stable release will
>> be bumped to 2.61.1. Is this what you are asking for?
>
> I guess. But if after 2.60.1, when you want to make a new "minor"
> release with new features, you fork it from, say, 2.064, I would name
> that new version, 2.64.1 instead of 2.61.1. Or with that comment you are
> implying that there will be "minor" release for each and every official
> release? Also, are you planning to drop the leading 0 in the version
> number or was just a typo?

Yes, the minor will match the minor it's forked from, that is important to  
semantically understanding which release the bugfixes apply to.

There will many releases per minor. So 2.060.1, 2.060.2, etc. I am hoping  
for packaged releases every week.

I would like to drop the leading 0, but I think it would be confusing to  
people to not have them exactly match D's current scheme.

> --
> Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
> ----------------------------------------------------------------------
> GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
> ----------------------------------------------------------------------
> Que barbaridad, este país se va cada ves más pa' tras, más pa' tras...
> 	-- Sidharta Kiwi


-- 
Adam Wilson
IRC: LightBender
Project Coordinator
The Horizon Project
http://www.thehorizonproject.org/