[Ovmsdev] Fwd: [openvehicles/Open-Vehicle-Monitoring-System-3] 29e333: Issue #36: Add support for ota/tag in config

Mark Webb-Johnson mark at webb-johnson.net
Mon Apr 16 09:40:28 HKT 2018

The original idea was to have these as release tags that users could subscribe to. The factory firmware we have has everyone as ‘main’, so that one is hard to change.

I did consider ‘alpha’, but it just looked strange to me.

The idea is that ‘edge’ will be an automated (at least) nightly build.

I think there is room for one more like Tesla’s ‘early access program’ (pre-release candidates that should be stable but have not had widescale testing). So, my overall suggestion is for something like:


Steve’s alternative would be:


Other than ‘main’, these are simple to change. Happy to go with the consensus...

Regards, Mark.

> On 16 Apr 2018, at 9:26 AM, Stephen Casner <casner at acm.org> wrote:
> On Mon, 16 Apr 2018, Mark Webb-Johnson wrote:
>> From now on, I’m going to be maintaining two tags for the production
>> ota server api.openvehicles.com <http://api.openvehicles.com/>. These
>> are:
>> main: for stable releases
>> edge: for bleeding edge developer releases
> Why not the "standard" terms release (or stable), beta, alpha?
>                                                        -- Steve_______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

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

More information about the OvmsDev mailing list