[Ovmsdev] v2.2.2

[Mark Webb-Johnson]

I think I may have a solution for this (going forward).

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:

https://github.com/markwj/Open-Vehicle-Monitoring-System/tree/v2.2.2/vehicle/firmware

And an example link to the v2.2.2 V2 production firmware is:

https://github.com/markwj/Open-Vehicle-Monitoring-System/raw/v2.2.2/vehicle/firmware/V2_production.hex

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:

Build all firmware
Copy the .hex files to the firmware folder
Update the change log
Commit
Tag the commit
push (--tags) to github
Announce the new version

What do people think? Sensible?

Regards, Mark.

On 15 Jan, 2013, at 8:38 AM, Mark Webb-Johnson wrote:

> 
> I think this approach is ok, and given github's approach probably the best way.
> 
> 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.
> 
> I've got a git guru on staff here at work - I'll ask him for his advise.
> 
> Regards, Mark.
> 
> On 15 Jan, 2013, at 5:49 AM, Tom Saxton wrote:
> 
>> That directory structure changes about as often as there are new official
>> releases, as you can tell by all of the orphan build directories. Linking
>> straight into the repository won't let me pick up new vehicles, and will
>> break when vehicles go from "experimental" to "production" status.
>> 
>> The release notes aren't in the repository (AFAIK), so I have to enter those
>> links manually as well.
>> 
>> Given that I have to manually update the page, I figure it's more reliable
>> to ferret out the right versions for each vehicle and copy them to my site.
>> This way, my page keeps working even if the repository changes, which means
>> less work maintaining the page between releases (which is currently zero
>> effort).
>> 
>> Anyone who's really into getting the latest builds can just grab the files
>> from the repository. My page is to support those who don't care enough to
>> climb that learning curve.
>> 
>>   Tom
>> 
>> on 1/14/13 1:23 PM, Michael Balzer wrote:
>> 
>>> Thanks, Tom!
>>> 
>>> Hm... to optimize the rollout, have you tried to link directly to the
>>> repository files?
>>> 
>>> The links in vehicle/firmware don't work, but using the github file
>>> browser I can get for example...
>>> 
>>> https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/master/vehicle/OV
>>> MS.X/dist/V2_Experimental/production/OVMS.X.production.hex
>>> 
>>> I'm new to github, but that URL scheme looks like being designed as a
>>> permanent link.
>>> 
>>> Regards,
>>> Michael
>>> 
>>> 
>>> Am 14.01.2013 21:13, schrieb Tom Saxton:
>>>> The firmware update guide page now has version 2.2.2 builds up.
>>>> 
>>>> http://www.idleloop.com/tesla/ovms/
>>>> 
>>>>    Tom
>>>> 
>>>> 
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> 
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20130117/296e2a72/attachment.htm>