[mythtv] SVN Branching

[Paul Wheeler]

One thing that might be good for this sort of thing is tagging the
version just prior to the breakage, that way people can just download
the tagged version rather than the specific revision (in effect the
same thing). I.e. you can periodically tag a release as latest
semi-stable release i.e. before any big changes go in. E.g. before
Daniels reworking of the tuning and before this live tv breakage. Also
before the panned convertion to mythui (through that sounds like it
may not be as disruptive). This is an easy way to stop people whinging
when trunk is broken, they just get the semi stable release.


Paul

On 11/17/05, Ivor Hewitt <ivor at ivor.org> wrote:
> Michael T. Dean wrote:
>  >
> > I don't know about Isaac, but if it were my project and I saw this many
> > people complaining about my not branching, I would purposefully delay
> > the completion of the LiveTV overhaul.  Maybe I'm just mean, but...
> >
> Yeah you're just mean. :)
>
> I think one of the problems is that its just too easy to grab source
> from svn and build it... people just get into the habit and forget the
> whole point is that they are accessing development source code.
>
> Daniel's right, that with hindsight a branch might have made sense since
> it took longer than expected..... on the other hand the longer it takes
> to finish such a pervasive change on a separate branch the more of a
> nightmare it becomes to merge it back in.
>
> After all it's not as if the change was made with no warning.
>
> Seriously though, no-one who is complaining is going to setup their own
> svn server.. (and that is a rather daft idea:) but there's nothing
> stopping them svn-ing to the revision before the live tv update and then
> applying just the later commits that they're interested in.
>
> Cheers,
> --
> Ivor
> http://www.ivor.it
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>