home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
SVN Upgrades & testing
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="gloomyandy" data-source="post: 99028" data-attributes="member: 24855"><p>Hi,</p><p>First a little background...</p><p>I use MP all of the time and really like it. I try to help out as much as I can and being a software dev in my real life I'm very much aware of the process and potential problems. I've submitted a number of patches and bug reports for mp over the last few months. </p><p></p><p>So what is this posting all about. Well I'd like some input on the best way to keep up to date with svns etc. Here is the way I currently work....</p><p></p><p>I tend to use recent svns all of the time (I understand the risks of doing this). I happy with this and like to try and provide feedback. The way I normally do this is to check the change logs and source forge updates. If there is something that looks interesting then I download the latest svn and take a look. I normally just load this over the top of my current configuration (making a backup as part of the process). If I see a problem of some sort I tend to do the following....</p><p>1. Get the latest svn to see if the problem still exists.</p><p>2. Try and narrow down the process to create the problem.</p><p>3. Once I can do 2. and the problem still exists I will then...</p><p>a) Backup my svn channels, and program settings.</p><p>b) Rename my MP install dir.</p><p>c) Install a fresh copy of the current stable base MP version</p><p>d) Update this to the latest svn.</p><p>e) If possible reproduce the problem and report it...</p><p>f) If the problem needs more of my settings then I re-import the channels from (a).</p><p>g) if needed I may add more of my configuration by hand (either using the setup program or by adding config from my saved svn by hand).</p><p>h) repeat e, f, g until the problem is reproduced or until I have my complete config available with no bug!</p><p>Once I have a system up and working I then continue normal usage until I start the cycle again.</p><p></p><p>So does the above make sense? Is it reasonably safe to update from one svn to the next? Is there a better way to move from one version to the next and then to revert to a stable build plus svn to test against? What do others do?</p><p></p><p>All the best</p><p></p><p>Andy</p></blockquote><p></p>
[QUOTE="gloomyandy, post: 99028, member: 24855"] Hi, First a little background... I use MP all of the time and really like it. I try to help out as much as I can and being a software dev in my real life I'm very much aware of the process and potential problems. I've submitted a number of patches and bug reports for mp over the last few months. So what is this posting all about. Well I'd like some input on the best way to keep up to date with svns etc. Here is the way I currently work.... I tend to use recent svns all of the time (I understand the risks of doing this). I happy with this and like to try and provide feedback. The way I normally do this is to check the change logs and source forge updates. If there is something that looks interesting then I download the latest svn and take a look. I normally just load this over the top of my current configuration (making a backup as part of the process). If I see a problem of some sort I tend to do the following.... 1. Get the latest svn to see if the problem still exists. 2. Try and narrow down the process to create the problem. 3. Once I can do 2. and the problem still exists I will then... a) Backup my svn channels, and program settings. b) Rename my MP install dir. c) Install a fresh copy of the current stable base MP version d) Update this to the latest svn. e) If possible reproduce the problem and report it... f) If the problem needs more of my settings then I re-import the channels from (a). g) if needed I may add more of my configuration by hand (either using the setup program or by adding config from my saved svn by hand). h) repeat e, f, g until the problem is reproduced or until I have my complete config available with no bug! Once I have a system up and working I then continue normal usage until I start the cycle again. So does the above make sense? Is it reasonably safe to update from one svn to the next? Is there a better way to move from one version to the next and then to revert to a stable build plus svn to test against? What do others do? All the best Andy [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
SVN Upgrades & testing
Contact us
RSS
Top
Bottom
