[Scons-dev] Time for a release?

[Bill Deegan]

Dirk,

Are you suggesting we should merge slots into default and push 2.4?
Or push what we have as 2.4 and then merge slots?

I'm thinking since slots will (could) break compatibility for some that we
should have a major version change? (3.0?)

If I remember correctly, that was our criteria for major version number
changes.
Unfortunately that means 3.0 may confuse some with thinking python 3.0 is
supported by the new (slots) version.
(No need to discuss python 3.0 here, that's an entirely other ball of wax)

*There are 3 broken tests on our win32 buildbot slave. We should resolve
those prior to a release.*

-Bill

On Wed, May 20, 2015 at 9:46 AM, Dirk Bächle <tshortik at gmx.de> wrote:

> Hi Bill,
>
>
> On 20.05.2015 16:36, Bill Deegan wrote:
>
>> All,
>>
>> It's been a while since the last release and a number of fixes are in the
>> repo, is it a good time for a release?
>>
>> I forget where we are with slots? Is that still on a  branch or in
>> default now?
>>
>>
> the slots branch hasn't been merged yet. From my perspective the current
> situation is as follows:
>
> - I agree that the basic fixes we have would justify a release v2.4 right
> now. Current trunk seems to be reasonably
>   stable....
> - The slots changes seem to work basically, at least nobody else
> complained after we added the getattr
>   wrapper for backward compatibility.
> - Jason Kenny is still examining the impact on Parts. He refactored some
> source code, but is still working
>   on some minor warts here and there...but over all it looked promising.
>
> So, I'd like to pass the token to Jason to hear what he has to say. The
> questions we all should probably discuss together are:
>
> - Is there more work needed to get Parts going with this new "slotted"
> version of SCons?
> - If yes, what are the single steps...and also: do we have to block the
> release for them?
> - What is our basic plan for getting Parts synchronized with SCons again?
> In some way, a new Parts release will
>   depend on SCons v2.4 and won't work with any version lower than that.
> How do we tell the user, and how do
>   we plan the next release of Parts in relation to SCons v2.4?
>
> There's probably more, but I forgot. ;)
>
> Best regards,
>
> Dirk
>
> _______________________________________________
> 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/d4a563ac/attachment.html>