[Scons-dev] Time for a release?

Dirk Bächle tshortik at gmx.de
Wed May 20 12:46:15 EDT 2015


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



More information about the Scons-dev mailing list