Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 6607] sorcery versions

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 6607] sorcery versions
  • Date: Sun, 11 Apr 2004 07:53:06 -0400

http://bugs.sourcemage.org/show_bug.cgi?id=6607





------- Additional Comments From hgreig AT bigpond.net.au 2004-04-11 07:53
-------
Having thought about this a little more there are two related aspects I would
like to mention.
Atomic merges of the entire suite of sorcery scripts from devel to stable and
basically "renaming" them is a problem. Code that hasn't been adequately
debugged is a liability to every user and developer but you can't feature
freeze devel sorcery for weeks on end to make sure bugtesting is done before
stable versions are released, for the simple reason that peoples timetables
and their personalities will let your release map down. You can't guarantee
in
advance when someone will be available to fix bugs, and some people won't fix
bugs they have introduced, many would rather move on to write "new" code and
let a person suffering from the bug find the solution. Thought needs to go
into how best to handle these releases, how to integrate good code (and not
integrate bad code) and some basic policies regarding feature submissions,
accountability for code and bugfixing. I had 5 machines over two months stop
booting due to sorcery bugs, 4 of those machines were remotely administered,
so I had to gain physical access to the machine before I could even begin
repairing them (FYI three of those machines were running stable sorcery, the
other two are an unfortunate side-effect of running devel sorcery on them).
Also releasing to a dated deadline is a damn good way to ensure bugs creep
into stable sorcery, the entire 1.7.X series is a good example of this. In
the
future stable releases should only be made when a feature set has been
implemented and bugtested, not beause some magical day has come around.
Of course, it is possible that bugs will still be released inside of stable
sorcery, so this "downgrade" feature and archiving of releases is still
necessary, hopefully it will be rarely used though.

thanks



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page