On 9/5/08, Brian Aker <[EMAIL PROTECTED]> wrote:
>
>
> I like rolling versions. One thought I am having is the for folks who want
> to support Drizzle, that if they want to support formal versions let them
> fork and maintain those. I am not married to this idea... but the old model
> of  ship once a year and do nothing in between is really broke in our
> industry.
>
> This is something that web development gets right when it works. There is a
> "train" and that leaves in a set/short period. If you are done you go in,
> but if you are not... then the next train is coming soon.


++

When I worked at Online Buddies (www.manhunt.net, may not be worksafe if
half-naked men aren't your thing) this is what we did on both the web
development side and the db/systems side.  Set a goal date for the work, if
it doesn't meet the goal, it doesn't go in the release.  We further set all
goals for dev work due on Fridays, with QA starting Monday morning, so that
"It's almost there" syndrome didn't creep up on us.  If it's not ready
Monday morning, you already had 2 extra days to make it work, so it doesn't
go in.

As the unofficial project manager (but with official approval to act as
such), I pushed about 5 db/systems changes per week.  This kept us focused
and on task.  We'd get 2-4 of them done -- we always got something done
every week, and always set the bar high enough that there was plenty to do.
The trick is making sure the big and small projects get worked on.

Given how in IT, timelines lasting more than a month will definitely change
(even with doubling/tripling estimates....and often less than a month will
change anyway), this is actually the only way I've seen software releases
work.  Given MySQL's promise to have a certain number of community releases
per year, I'd actually hoped they'd do it that way.

-Sheeri
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to