Reply to thread

Message

<blockquote data-quote="nst6563" data-source="post: 55596" data-attributes="member: 14655">looks like the point of my post was taken as an &quot;upgrade path&quot; or &quot;simplified patching mechanism&quot; rather than what I really meant it to be.&nbsp; I know what an SVN is, I know what CVS is, etc.&nbsp; I've done software development before.&nbsp; However, I prefer not to hook up a keyboard/mouse to my htpc all the time (isn't one of the points of an HTPC to have full functionality via the convenience of a small remote??) to test out if the latest SVN build addresses any issues I may be having.&nbsp; Having an &quot;automated&quot; option in one of the menus would solve this.&nbsp; My other option is to write the program myself when I have time.&nbsp; I simply figured that since MP is constantly under development, it would also benefit the dedicated testers in a way that's much faster and simpler to grab the newest build and begin testing.</blockquote>

[QUOTE="nst6563, post: 55596, member: 14655"] looks like the point of my post was taken as an "upgrade path" or "simplified patching mechanism" rather than what I really meant it to be. I know what an SVN is, I know what CVS is, etc. I've done software development before. However, I prefer not to hook up a keyboard/mouse to my htpc all the time (isn't one of the points of an HTPC to have full functionality via the convenience of a small remote??) to test out if the latest SVN build addresses any issues I may be having. Having an "automated" option in one of the menus would solve this. My other option is to write the program myself when I have time. I simply figured that since MP is constantly under development, it would also benefit the dedicated testers in a way that's much faster and simpler to grab the newest build and begin testing. [/QUOTE]

Verification