<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div>I think I may have a solution for this (going forward).<div><br></div><div>If we use the git 'tags' feature, to tag each released firmware build, github will allow us to publish the tree at that time. For example, see:</div><div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><a href="https://github.com/markwj/Open-Vehicle-Monitoring-System/tree/v2.2.2/vehicle/firmware">https://github.com/markwj/Open-Vehicle-Monitoring-System/tree/v2.2.2/vehicle/firmware</a></div></blockquote><div><br></div><div>And an example link to the v2.2.2 V2 production firmware is:</div><div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><a href="https://github.com/markwj/Open-Vehicle-Monitoring-System/raw/v2.2.2/vehicle/firmware/V2_production.hex">https://github.com/markwj/Open-Vehicle-Monitoring-System/raw/v2.2.2/vehicle/firmware/V2_production.hex</a></div></blockquote><div><br></div><div>That link is quite clean and should be stable going forward. It will just take some discipline to set things up correctly during a release:</div><div><br></div><div><ol class="MailOutline"><li>Build all firmware</li><li>Copy the .hex files to the firmware folder</li><li>Update the change log</li><li>Commit</li><li>Tag the commit</li><li>push (--tags) to github</li><li>Announce the new version</li></ol></div><div><br></div><div>What do people think? Sensible?</div><div><br></div><div>Regards, Mark.</div><div><br><div><div>On 15 Jan, 2013, at 8:38 AM, Mark Webb-Johnson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>I think this approach is ok, and given github's approach probably the best way.<br><br>I really wish that github had a 'files' repository (like sourceforge) that we could put fixed (not revision controlled) files. Release, not development, files. I tried to create symlinks (in the 'firmware' folder), but they don't work (the symlink text file is just downloaded, not the thing it linked to), and anyway that doesn't give us history.<br><br>I've got a git guru on staff here at work - I'll ask him for his advise.<br><br>Regards, Mark.<br><br>On 15 Jan, 2013, at 5:49 AM, Tom Saxton wrote:<br><br><blockquote type="cite">That directory structure changes about as often as there are new official<br></blockquote><blockquote type="cite">releases, as you can tell by all of the orphan build directories. Linking<br></blockquote><blockquote type="cite">straight into the repository won't let me pick up new vehicles, and will<br></blockquote><blockquote type="cite">break when vehicles go from "experimental" to "production" status.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The release notes aren't in the repository (AFAIK), so I have to enter those<br></blockquote><blockquote type="cite">links manually as well.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Given that I have to manually update the page, I figure it's more reliable<br></blockquote><blockquote type="cite">to ferret out the right versions for each vehicle and copy them to my site.<br></blockquote><blockquote type="cite">This way, my page keeps working even if the repository changes, which means<br></blockquote><blockquote type="cite">less work maintaining the page between releases (which is currently zero<br></blockquote><blockquote type="cite">effort).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Anyone who's really into getting the latest builds can just grab the files<br></blockquote><blockquote type="cite">from the repository. My page is to support those who don't care enough to<br></blockquote><blockquote type="cite">climb that learning curve.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Tom<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">on 1/14/13 1:23 PM, Michael Balzer wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">Thanks, Tom!<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Hm... to optimize the rollout, have you tried to link directly to the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">repository files?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">The links in vehicle/firmware don't work, but using the github file<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">browser I can get for example...<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/master/vehicle/OV">https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/master/vehicle/OV</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">MS.X/dist/V2_Experimental/production/OVMS.X.production.hex<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I'm new to github, but that URL scheme looks like being designed as a<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">permanent link.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Regards,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Michael<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Am 14.01.2013 21:13, schrieb Tom Saxton:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">The firmware update guide page now has version 2.2.2 builds up.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://www.idleloop.com/tesla/ovms/">http://www.idleloop.com/tesla/ovms/</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> Tom<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">OvmsDev mailing list<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">OvmsDev mailing list<br></blockquote><blockquote type="cite"><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br></blockquote><blockquote type="cite"><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br></blockquote><br>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br></div></blockquote></div><br></div></body></html>