Re: [Scons-dev] point release time?

2013-12-17 Thread Bill Deegan 
Dirk,

If the memory patch uses __slots, then won't that likely break some user
logic? If so then we should push out 2.3.1 without it with a notice in the
release notes indicating what such change may break?

Also looks like we have more than a handful of tests broken.
So my suggestion would be to fix the broken tests, then push 2.3.1.
Then address the other issues?

-Bill


On Tue, Dec 17, 2013 at 8:51 AM, Dirk Bächle tshor...@gmx.de wrote:

 Hi Gary,


 On 17.12.2013 17:19, Gary Oberbrunner wrote:

 I think it's time for a point release to fix the linker option bug, and
 roll in the other goodies that have been submitted.  I'll have some time
 over the holidays I think; anyone object?  I'd think about calling it 2.3.1
 rather than 2.4, but am open to suggestions.  This would of course not
 include any python3 stuff (which is on its own branch anyway).

  sounds good in general, I don't mind much about the exact version
 number. I'm already in my holidays and working on a patch to reduce overall
 memory consumption. I'd like to get this into the upcoming release if
 possible...
 Then, the documentation comes to my mind. There were a few voices that
 wanted to change the layout of the new DocBook stylesheets, but nothing has
 happened so far. I like the design as-is, but we probably should put some
 time aside for straightening out the author/copyright blobs.
 Finally, what's the status of the VersionedSharedLibrary stuff? I remember
 that there were still some open issues last time I heard about it. We
 should be sure that it really works before pushing it out the door...

 Best regards,

 Dirk

 ___
 Scons-dev mailing list
 Scons-dev@scons.org
 http://two.pairlist.net/mailman/listinfo/scons-dev

___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] point release time?

2013-12-17 Thread Dirk Bächle 

Bill,

On 17.12.2013 22:06, Bill Deegan wrote:

Dirk,

If the memory patch uses __slots, then won't that likely break some 
user logic? If so then we should push out 2.3.1 without it with a 
notice in the release notes indicating what such change may break?




this patch doesn't use slots at all, it just tries to release as much 
infos as possible for already built targets...without breaking any 
existing tests. This means that we don't get the full amount of saved 
memory that would be possible, but it's a start.



Also looks like we have more than a handful of tests broken.
So my suggestion would be to fix the broken tests, then push 2.3.1.
Then address the other issues?



My pull request #96 should fix the Environment bug...which other issues 
would you like to address?



Regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev