[Libburn] Libburn 0.2

Derek Foreman manmower@signalmarketing.com
Wed, 25 Feb 2004 20:41:10 -0600 (CST)


On Wed, 25 Feb 2004, Archit Baweja wrote:

> Hey
>
> I would agree having the well-known "Release early and often" cycle, but
> not really specifying an exact period. Just release after a few bug fixes etc.
>
> Archit

The problem we're starting to face now is that libburn and libisofs are
fairly independent.  Until recently, libisofs didn't matter much, but now
it's probably going to be ready for use before I've done anything
significant to the burning stuff.

I think a strict timeline would solve sync problems between libburn and
libisofs at release, but I don't want to commit to a specific schedule.
(Because I'm lazy, and having multiple releases that are exactly the same
looks bad. :)

> P.S. You can see that I don't appreciate the Gnome Release Cycle for personal
> reasons :-D
>
> Also, there is no harm in doing a no feature/bug-fix release. Spice it up :D

True.  And there can be a new release when libisofs is ready for use,
regardless of whether I've finished adding TAO and whatever to the burning
stuff.  I think that's what I'll do for now.  (Might have to re-assess
things when the code's not "alpha" anymore, if people actually start using
it :)

> Todd Kulesza <todd@dropline.net> writes:
>
> > On Wed, 2004-02-25 at 15:59, Derek Foreman wrote:
> > > Sorry about that, I didn't realize you were so close to done.
> > >
> >
> > Well, "done" and "usable" are two different things... the code is mostly
> > in place, but there's a lot of cleaning-up I'd like to do.
> >
> > > I'm hoping to shorten the delay between releases, 0.3 shouldn't be too far
> > > off anyway.  It might just add TAO (which is already mostly in place),
> > > and clean up a few little corner cases I've been ignoring.
> >
> > Maybe we could do time-based development releases; release every (2
> > weeks?  monthly?) just to keep up interest and allow enough time for
> > feedback to trickle in between releases.  The lib is in heavy
> > development, so releases don't need to be 100% perfect.  I'd say getting
> > more eyeballs looking at the code and banging on the latest version is
> > the main goal this early in a product's lifecycle :)
> >
> > Todd
> >
> >
> > _______________________________________________
> > Libburn mailing list
> > Libburn@pdx.freedesktop.org
> > http://pdx.freedesktop.org/cgi-bin/mailman/listinfo/libburn
>