[mythtv] Using Release Candidates to minimize user trouble?

[Kenneth Aafløy]

On Thursday 25 December 2003 01:19 pm, Isaac Richards wrote:
> On Thursday 25 December 2003 12:12 am, Kenneth Aafløy wrote:
> > I was wondering if the use of MythTV release candidates 
> > would actually help MythTV's releases mature before the
> > actual release, or if the would just hinder the current
> > main focus for MythTV development, which is major feature
> > enhancements.
> >
> > I would argue that release candidates would make the 
> > release version as bugfree as possible, but this would
> > imply a increased load on support questions and the like.
> > So what about an intermediate sollution, which would be
> > to just tag the CVS reposotory with release-0-14-rcX, in a
> > greater period of time, so that all developers actually 
> > could follow the last steps of bugfixing a bit more close
> > than a mere 'I'm planning a release next week.' type of
> > message on the forum?
> >
> > I'm unsure of wheter this would actually ease the release 
> > cycle or put a larger strain on the MythTV team, so
> > comments on this subject is wery welcome.
> 
> Well, I'd say that just a release candidate tag kind of 
> defeats the purpose of doing a release candidate, as
> people testing with it would not be getting any 
> bugfixes done since tagging unless the tag was moved after 
> each commit.

I might be speaking out of just my head, but wouldn't this
just be a cvs management problem (which developers are
supposed to keep track of), that involves the cvs commands
'cvs up -A', 'cvs up -r <rel>' and 'cvs up -f' to be
used in the correct cases. Since a tag merily match a set
of files, the 'cvs up -f' will force a head tag, which
will include the last set of patches since the last rc.

> I don't really like doing actual release candidates, mainly 
> because of the time commitment.  Takes me quite a while to
> go through and get everything ready..  Also, it breaks my
> version numbering scheme =)

Actually, with the cvs tag approach, the effect on the version
numbering scheme would be next to none, except for the fact
that those involved in release candidate testing *should* be a
part of the development of mythtv community (or has been).

Also, the cvs tag approach would also limit any binary packages
(hopefully), of any release candidate to reach the web.

This is offcourse the real commitment, on your part, unless
you assign the payload of prepping a release tag to someone
else that might not be as heavily loaded with tasks.

Also, the primary focus (on the first rc, or so) could only
be focused only on the main mythtv program and library,
as it's the largest one yet. Also in this phase any
inconsistencies between the main mythtv module and the
mythtv plugins could be resolved, if any, which would ease
the task of preparing further release (candidates).

This might also have the side effect of waking up the
developer that might be deeply incorperated into a patch
that he or she is working on, and bringing them forth to the
testing phase of the release cycle.

> I dunno, I just consider my 'I'm going to put out a release 
> in a week' emails to be a release candidate type thing.

I'm actually unsure myself, but I felt that my own arguements
was so on bordeline that I might as well try to put my points
through on the board instead of my head.

Kenneth