Release? was Re: Stepping back as Zinf Debian maintainer

On Sat, 2004-01-24 at 10:12, Robert Hart wrote:
> On Sat, 24 Jan 2004, Andreas Rottmann wrote:
> 
> > That would help, but a release before that would be even more useful
> > (so I can mail all the bugsubmitters of old bugs, and ask them if they
> > can still reproduce the bug).
> 
> Was going to say the same thing myself. The difference between the last
> release and current CVS is just too huge right now.
> 
> I think we (myself included) are too good at starting things, and not very
> good at finishing things.
> 
> Do we have any uptodate & definitive list of release critical bugs. A
> quick scan of the list on sf doesn't seem to bear any relationship to
> reality...

Yes, there should have been a release, at the latest, around
the 1st of January.    

I think we have a few choices to make and it would be great
to get some feedback from the developers involved.   The
overall question is whether to release RSN, with what we
have or to push ahead in the hope that things will get better.
Of course, nobody has a lot of time to spare, myself included.

Rob Hart did some excellent work upgrading zinf to GTK2, and I would
like to release that work.   There were a few visual bugs, but these
were not show stoppers (please let me know if you think they are).  They
ones I remember are listed below.

1.  Column titles in new browser windows don't appear initially 
2.  Dnd between playlist to playlist etc.

I would be happy to wrap this as an initial release of GTK2 and see if
anybody else notices.  

Eventually I would like to move over to David's browser code that is 
integrated with MDB.  Both need a bit of work to complete them.  It is
coming along slowly and being filled out.   Currently the CDrom stuff
is probably the most in disrepair and probably needs to be rethought
out(interaction between mdb, browser, and player when dealing with
cdroms).    I was sure this would be done by December, but plans do
change.

So in nutshell, thoughts on the following (and/or help)

1.  Release CVS as is (this week).
2.  Release CVS after disabling musicbrowsermm and mdb (in a few weeks).
3.  Freeze CVS except for gtk2 bug fixes and release end of february.
4.  Push for musicbrowsermm and mdb (release when it's ready).

I am actually for #1, with a nice list of requirements to compile from
source.   #2 would take some automake, configure work.  #3 I am not sure
what bugs really exists, as I use the gtkmm browser more often these
days, please list the bugs you know of.   


-- 
Kristian G. Kvilekval
email:[email protected] office:(805)893-4276 http://www.cs.ucsb.edu/~kris



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn