Posts: 772
Joined: Sep 2008
Reputation:
5
xexe
Posting Freak
Posts: 772
I am not suggesting beta testing anything... simply that the abilty to tag a SVN as good be added. This way users can have SVN versions but not necessarily the latest to the second. It also allows as you have pointed out, stopping people upgrading when one is known to be broke.
Most SVN users care not a jot about beta testing and simply want never features (shiny kit syndrome). Thats just life unfortunately.
The main thing is that if the devs are working on a tricky bug there could be many builds that are broke in a row. Once you have an auto install client you need the ability hold users from grabbing this broke version.
Having problems getting your TV shows recognized?
Try my extra TV show matching REGEX
here
Posts: 156
Joined: Dec 2006
Reputation:
3
I was thinking of a way that this application would allow users to rate builds. that way we could even flag a build as bad if alot of users are rolling back to a previous build.
Posts: 772
Joined: Sep 2008
Reputation:
5
xexe
Posting Freak
Posts: 772
nice idea. go one further and give each instance a unique id (anonymous) and dont rely on human feedback which will be patchy at best
that way you can say things like xxx users on yy build. zzz user have donwgraded to this build etc
ties nicely into the "svn stable" idea we have been discussin
Having problems getting your TV shows recognized?
Try my extra TV show matching REGEX
here
Posts: 156
Joined: Dec 2006
Reputation:
3
for these ratings to be tracked we need some server side support, anywhere we could host a webservice?
if the hostirng service is ASP.net i could write the server side as well.
Posts: 156
Joined: Dec 2006
Reputation:
3
yeah i guess that could be phase 2. but for now, i need a list of build to parse. it could be an xml file, rss or even a simple html page.
can someone get that up and running?
Posts: 156
Joined: Dec 2006
Reputation:
3
i put to gether a sample xml that could be hosted somewhere, the update script could download this xml to figure out which build to download based on user settings.
<?xml version = "1.0" encoding = "utf-8"?>
<!-- Blank XML template -->
<XBMC>
<Build>
<Rev></Rev>
<Compiler></Compiler>
<Url></Url>
<CompileDate></CompileDate>
</Build>
</XBMC>
one thing i can figure out by myself and need you guy's help is what are the build options as previously mentioned, for example external player, intel fix..... i need all the different attributes so i can build it into the program.
Posts: 156
Joined: Dec 2006
Reputation:
3
what do you guys think about only doing the general build for now? if they change all the time i don't think there is going to be a way to fully automate the update.
lets say a user chosee branch 'A'. that branch gets merged into the main 2 weeks latter, that user won't get anymore updates since there wont be updated 'A' Builds!
what do you think?