Will the next SCons update (SCons 2.3.3) be released from default based? Based on the current commit workflow this seems to be the case.
Is this a good model for project releases? In this case, the reason for releasing an update is to fix a VERY specific issue. Wouldn't it be better to release with a patch fix on top of branch rel_2.3.2 as 2.3.2-2 rather than release everything current in default which may include changes intended for SCons 3.X? I am concerned that the leading contributor to SCons 2.X instability, including breaking pre-2.7 compatibility, is the lack of separation between 2.X baselines and 3.X. Maybe there needs to be a workflow developed for this? We might consider handling version releases more like the python release model (or some other industry-standard-like release model). Maybe I am misunderstanding. We are releasing SCons 2.3.3 from default, please consider merging pull request #164 to improve the documentation on http://scons.tigris.org/issues/show_bug.cgi?id=2395 V/R, William
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
