On Tuesday 22 February 2005 02:47 pm, Brad Templeton wrote:
> If the snapshot in the release has a "crash on delete" bug I would put that
> in the major class.

It doesn't crash, it just refuses to delete recordings that don't exist.  
Takes a bit of time to time out while it retries things, but, it certainly 
doesn't crash.

> I do think their case is compelling.  I believe a good approach, which I
> know you have said you don't like, would be to take a snapshot at a good
> time, put it out as 0.17-rc, tag it in CVS, and then apply only bug
> fixes to that branch of CVS while continuing the main branch.  Then,
> after a while, release 0.17 for the atrpms and knoppmyths of the world.

Bugs don't get fixed without people testing them.  People won't test them if 
it's just a branch in CVS, as this entire thread shows.  In my experience, 
people won't test an actual pre-release, either, for the same reason they 
won't test CVS now.

> Using CVS is not a good alternative for many users.  Leave aside
> that not all are at the skill level to do it, a live CVS is
> deliberately unstable.  Bugs can be introduced one day that majorly
> break things, ideally fixed very quickly but at any time they can be
> there.
>
> One idea that might make sense is to have somebody track when serious
> bug reports are low, and throw tags into the cvs server to declare that
> point a suitable testing release.

Funnily enough, that's pretty much exactly what I do when I decide to put 
together a release.  I'd link to the bugzilla graph, but, the graph config 
was eaten when the website switched servers a few months back. =)

It's simple, really.  If people don't see the need to participate in the 
development process (which happens to include testing CVS, especially when 
I've announced that a release is close), then I don't think they have any 
right to complain about bugs in a release, and certainly shouldn't bitch 
about how I go about making releases.

Isaac
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Reply via email to