[Scons-dev] Time for a release?

[Bill Deegan]

William,

Of course your vote counts!
It's open source.

-Bill
p.s. Plus you have a good first name so I give it a little more weight :)

On Wed, May 20, 2015 at 4:45 PM, William Blevins <wblevins001 at gmail.com>
wrote:

>
> On Wed, May 20, 2015 at 3:14 PM, Dirk Bächle <tshortik at gmx.de> wrote:
>
>> On 20.05.2015 20:35, Bill Deegan wrote:
>>
>>> Could we push default as is as 2.3.5, and then merge slots and push that
>>> in a couple weeks?
>>> Then we could branch default as 2.3 prior to merge of slots?
>>>
>>
>> Sure, I have no objections to that. After 2.3.5 we could also branch out
>> from default to a "2.4" branch, and then merge the "slots" stuff only on
>> that branch as a first step. So we would never risk to "taint" our trunk
>> with merges that would be kind of hard to undo.
>> If no problems show up with 2.4 we could then still merge it again to
>> default, and continue from there towards 2.5 and 3.x. Just as an idea...
>
>
> I think this is a good idea.  Risk mitigation plus consistency with the
> SCons version numbers~!
>
> Not that my vote counts ;)
>
> V/R,
> William
>
> _______________________________________________
> Scons-dev mailing list
> Scons-dev at scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist2.pair.net/pipermail/scons-dev/attachments/20150520/6bed4b11/attachment.html>