Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] Team Tasklist for 1.0

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Andrew <afrayedknot AT thefrayedknot.armory.com>
  • To: SM-Discuss <sm-discuss AT lists.ibiblio.org>
  • Subject: Re: [SM-Discuss] Team Tasklist for 1.0
  • Date: Fri, 31 Mar 2006 13:09:20 -0800

On Thu, Mar 30, 2006 at 02:11:20PM -0800, Eric Sandall wrote:
>
> Sorcery:
> * Configuration files should never be overwritten (Stageroot?)

Stage_root is currently the sorcery team's top priority and is planned
to be released in sorcery 1.14. Stage_root is a pretty major feature, it
will effect every build api2 spell. Its side-effects should be minimal
and transparent to the spell, but we are not taking this lightly and are
planning on having a lot of internal testing before it even reaches devel.
The last thing we want is to inadvertantly cause more work for the
grimoire team.

According to the 1.0 roadmap, as of the 1.13.0 release (last fall)
everything the sorcery team had agreed to do for 1.0 was completed
(actually I think everything except one or two items was done in 1.12).

I think its a bit late in the game to add anything new to the sorcery
agenda as a 1.0 milestone, especially something big like stage_root
(actually I think its a bit late in the game to add *anything*at*all*
to the roadmap).

The proposed date is for a July 1.0, thats in about 3 months, which I
dont think is doable for stage_root. That leaves about a month to month-
and-a-half to finish up all the 1.14 work, another month for things to
soak in test and another few weeks before the proposed 1.0 to work out
all the rough edges in the first stable version (as invariably happens).
With our current development and testing resources I dont think thats
a realistic goal.

I cannot commit to it at this time, doing so would jeopardize sorcery's
stability.

The 1.14 release also includes sub-depends, so if the grimoire team is
going to have a new milestone requiring sub-depends, then either the
sorcery schedule needs a fairly big overhaul or that proposed July date
just isn't going to happen. In other words, Im open to scheduling changes
and adding newly completed sorcery work (not in the 1.0 roadmap) if
thats what other teams want.

I think the additions are lot to ask, either we want 1.0 "soon" (as in
July), or we're going to be adding a bunch of stuff at the 11th hour and
postpone it some more. We can't have both. On a personal level, 1.0
soon or not isnt a big deal to me either way. However I wont commit to
unrealistic milestones, regardless of what they're for.

In summary, I think if we want 1.0, we should stick with what we planned
on and not add *anything* to the roadmap unless its absolutely necessary.

-Andrew

--
_________________________________________________________________________
| Andrew D. Stitt | acedit at armory.com | astitt at sourcemage.org |
| irc: afrayedknot | Sorcery Team Lead | ftp://t.armory.com/ |
| 1024D/D39B096C | 76E4 728A 04EE 62B2 A09A 96D7 4D9E 239B D39B 096C |
-------------------------------------------------------------------------

Attachment: pgpznh2wd_CYp.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page