<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Another point perhaps missed is that these are really release tags, not necessarily developer release stages. So, for example, say we were working on a branch with a major re-write called v4.x, we could create a ‘v4x’ branch (or whatever) and release ota updates to it. Modules subscribing to that tag would get those updates.<div class=""><br class=""></div><div class="">I guess we could address that with v3-beta, v3-alpha, v4-alpha, etc.</div><div class=""><br class=""></div><div class="">Regards, Mark</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 16 Apr 2018, at 9:40 AM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net" class="">mark@webb-johnson.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">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.<div class=""><br class=""></div><div class="">I did consider ‘alpha’, but it just looked strange to me.</div><div class=""><br class=""></div><div class="">The idea is that ‘edge’ will be an automated (at least) nightly build.</div><div class=""><br class=""></div><div class="">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:</div><div class=""><br class=""></div><div class=""><ul class="MailOutline"><li class="">main</li><li class="">eap</li><li class="">edge</li></ul></div><div class=""><br class=""></div><div class="">Steve’s alternative would be:</div><div class=""><br class=""></div><div class=""><ul class="MailOutline"><li class="">main</li><li class="">beta</li><li class="">alpha</li></ul></div><div class=""><br class=""></div><div class="">Other than ‘main’, these are simple to change. Happy to go with the consensus...</div><div class=""><br class=""></div><div class="">Regards, Mark.<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 16 Apr 2018, at 9:26 AM, Stephen Casner <<a href="mailto:casner@acm.org" class="">casner@acm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Mon, 16 Apr 2018, Mark Webb-Johnson wrote:<br class=""><blockquote type="cite" class="">From now on, I’m going to be maintaining two tags for the production<br class="">ota server <a href="http://api.openvehicles.com/" class="">api.openvehicles.com</a> <<a href="http://api.openvehicles.com/" class="">http://api.openvehicles.com/</a>>. These<br class="">are:<br class=""><br class="">main: for stable releases<br class="">edge: for bleeding edge developer releases<br class=""></blockquote><br class="">Why not the "standard" terms release (or stable), beta, alpha?<br class=""><br class=""> -- Steve_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class=""><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class=""></div></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>