William,
On 12.08.2014 01:46, William Blevins wrote:
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 understand your concerns, but I don't see any changes in the diff
2.3.2-current that would break Python2.x compatibility. So I'd like to
continue with release numbering as normal, everything else might confuse
the user.
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?
I still think that we really have enough workflows, now we actually have
to do wome work. Boring, I know...it's so much more fun to fiddle with
tech stuff and new interfaces while migrating from one technology to the
other. ;)
BTW, the OpenHatch project just migrated its issues from Roundup to
Github, because with having the tracker close to the sources they would
"save so much work". They wrote scripts and did all their stuff, and now
the first users complain because Github doesn't have a notion of
"depends on", for example. Lots of hours down the drain basically, and
let me just add: I warned them in advance...
I don't want the same thing happening to us, our resources are still to
scarce.
We might consider handling version releases more like the python
release model (or some other industry-standard-like release model).
Releasing/branching off from default is an industry standard.
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
I saw your documentation PRs, and I'll make sure that they go in before
the release.
Regards,
Dirk
_______________________________________________
Scons-dev mailing list
[email protected]
http://two.pairlist.net/mailman/listinfo/scons-dev
