Public SourceMage Discussion List

[Andrew <afrayedknot AT thefrayedknot.armory.com>]

On Fri, Jun 03, 2005 at 05:32:26PM -0700, Eric Sandall wrote:
> Quoting Andrew <afrayedknot AT thefrayedknot.armory.com>:
> >I'll try and hash out some of the requirements based on how I would
> >quantify them.
> >
> >On Fri, Jun 03, 2005 at 04:35:09PM -0500, David Kowis wrote:
> <snip>
> >>Easy to maintain.
> >>How can this be measured?
> >>Perhaps better would be:
> >>- - Installer will be modularly built, such that each module is one 
> >>menu item in
> >>the installer.
> >
> >I think theres two goals here. The first is the code itself is
> >maintainable. In other words, someone reports a bug, it should be easy
> >to look at the bug and figure out what section of code is causing the
> >bug and to fix the code itself.  The other goal is to have that fix
> >presented to the user in a timely fashion. It isn't totally obvious which
> >one is being referenced here.
> 
> I think he's mainly talking about the first point: Easy to identify the
> offending code and fix it. The other goal (new ISO in a timeley
> fashion) is more geared towards our goal of automating the ISO creation
> process.

I think they're both necessary ingredients to satisfy "easy to fix and
update" requirement, no matter how fast you can fix the bug in the code
it doesnt matter until theres an iso with the code on it (we tend to
ignore that part in our contituents, since its relatively automatic) on
the other hand, if it takes you very little time to release an iso but
the code is a nightmare, you have the same result. The question is, are
they both long term goals? short term goals? one is long the other short?
If they're both short term goals, how does that effect the near term schedule?

<snip>

> >I think the first step for this is to prioritize and order all the bugs 
> >into
> >releases they'll be fixed in. The iso "works" when all the bugs for that
> >release are fixed and all the enhancements targeted for that release 
> >a working.
> 
> I think some of that work has been done, but it is a bit disorganized.
> 

Perhaps call a meeting to scrub through all the bugs? Or just have david
go through them and ask people to change if they disagree.

-Andrew

-- 
__________________________________________________________________________
|Andrew D. Stitt                           | astitt at sourcemage.org    |
|irc: afrayedknot                          | afrayedknot at t.armory.com |
|aim: thefrayedknot or iteratorplusplus    | acedit at armory.com        |
|Sorcery Team Lead                         | ftp://t.armory.com/         |
--------------------------------------------------------------------------