[mythtv-users] SVN question, possibly OT

[Michael T. Dean]

On 10/08/2007 05:24 AM, William Munson wrote:
> Todd Ferris wrote:
>   
>> I have a question about the mythtv SVN that I am hoping someone here 
>> can help out with.
>>
>> I was browsing the mythtv source trees and was looking at the 
>> release-0-20-2 tag.  Then I popped over to the release-0-20-fixes in 
>> the branches tree.  The release-0-20-2 last change was 1 month ago 
>> (makes sense given the release date), the release-0-20-fixes shows 6 
>> days since the last change.
>>
>> My question is, how can I tell what has changed between 
>> tag/release-0-20-2 and what is now in branch/release-0-20-fixes.  I 
>> assume that I should be able to just run a simple SVN command and it 
>> will spit out all of the changed files with the comments...
>>     

As William mentions, the -commits list has all of that information, but
also has information about commits to trunk (bleeding edge
development--which has a lot of commits) and branches--including
branches other than 0.20-fixes (these other branches being where new
major changes are tested before being rolled into trunk) as well as the
occasional tag (which marks a group of files as a "version" for release).

You may be happier just looking at the revision log for the branch. 
http://svn.mythtv.org/trac/log/branches/release-0-20-fixes (note that
the information on that page will include all updates to 0.20 since the
0.20 release (i.e. those already in 0.20.1 and 0.20.2).  For the "old"
updates (those in released versions), see the release notes: 
http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.20.2 .

Anyone know why hitting "Go" on the search of the wiki with the search
string "release notes" takes you to the 0.20 release notes instead of
the current 0.20.2 release notes?  Or, even better, does anyone know how
to fix that to take you to the current release notes?  Thanks.

>> In addition, can anyone point me towards (couldn't find on the wiki) a 
>> short description how the three directories (branch, tag, trunk) are 
>> used by the developers.  I searched the wiki, but didn't come up with 
>> anything.
>>     

The best description is
http://svnbook.red-bean.com/en/1.4/svn.branchmerge.html (though the
above may give you what you want),

> For that info you should be reading the commits and the dev list. They 
> are both archived. In general terms, the fixes branch should be used as 
> the official release branch and you should normally just compile the 
> latest fixes anytime you update.
>
> That said, the trunk branch which is the bleed edge development code has 
> some nice new features that may make it worth while to upgrade however 
> it is not nearly as stable as -fixes.

But if you decide to use SVN trunk, please sign up for and start to read
all the messages that come through the mythtv-dev and mythtv-commits
lists so that the devs can spend their time making fixes and adding
great new features rather than provider user-support for questions that
are clearly answered in their commit logs or in discussions on the -dev
list.

If you just want a working MythTV box without the effort, your best bet
is to stick with 0.20-fixes.

Mike