<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="">Soko,<div class=""><br class=""></div><div class="">From the original announcement on this:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">To try to avoid a repeat of the 3.1.007 issue with OTA updates, I’ve set things up as below:</span><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><ul class="MailOutline"><li class="">edge: Bleeding edge developer, built automatically each night with 3.1.XXX-N-HHHHHH style versioning</li><li class="">eap: Early Access Program pre-releases, usually with 3.1.XXX style versioning</li><li class="">main: Stable releases that have completed testing in EAP, with 3.1.XXX style versioning.</li></ul></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Before moving things edge -> eap, I’ll have a checklist of regression tests to run (including ota update). Other functional problems should have been picked up by developer cars while in ‘edge’ release. I suggest to leave a particular build in ‘edge’ for a week, to make sure no problems reported to those early real-world testers, before moving to ‘main’.</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">I have an automated nightly build script that runs at 4pm UTC (midnight HKT). That pulls the latest masters for esp-idf and ovms firmware, then builds as appropriate. If there is something to build (something in git changed), it does it automatically and produces an email summary like this:</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><blockquote class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); margin: 0px 0px 0px 40px; border: none; padding: 0px;"><div class=""><font face="Andale Mono" class="">Subject: OVMS Nightly Firmware Build 3.1.008-13-g272697e</font></div><div class=""><font face="Andale Mono" class=""><br class=""></font></div><div class=""><font face="Andale Mono" class="">3.1.008-13-g272697e<br class="">Thu Jun 28 00:57:19 UTC 2018 Automated build (markhk8)<br class=""><br class="">Total sizes:<br class="">DRAM .data size: 17116 bytes<br class="">DRAM .bss size: 33536 bytes<br class="">Used static DRAM: 50652 bytes ( 130084 available, 28.0% used)<br class="">Used static IRAM: 102096 bytes ( 28976 available, 77.9% used)<br class=""> Flash code: 1279002 bytes<br class=""> Flash rodata: 598168 bytes<br class="">Total image size:~1996382 bytes (.bin may be padded larger)<br class=""><br class="">* 272697e (HEAD, origin/master, origin/HEAD, master) Twizy: no sufficient level info on charge done<br class="">* 8497d9f Web dashboard: range display min/max exchanged<br class="">* 5d8f96d Webserver: fix u64 alignment<br class="">* 5363ab8 TeslaRoadster: Vehicle cooldown command and implementation<br class="">* bf3b0d5 TeslaRoadster: Digital Speedo implementation<br class="">* d0221bf TeslaRoadster: Refuse to lock a car that is ON<br class="">* 7179600 Update project status files<br class="">* b3bef78 TeslaRoadster: Digital Speedo implementation<br class="">* cfbd297 TeslaRoadster: Vehicle cooldown command and implementation<br class="">* ec4bc37 Add VehicleModeKey helper function</font></div></blockquote><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">At the moment, that summary comes to me. Is there any use sending it to the ovmsdev mailing list?</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">With developer cars set to ‘edge’, and automatically updating each night, hopefully with this three stage process we can pickup on problems before they hit the main stable trunk.</div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">Regards, Mark.</div></div></blockquote><div class=""><br class=""></div><div class="">This is all from ‘master’ and unrelated to braches (which are experimental and usually hand-built).</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><a href="https://www.openvehicles.com/node/2592" class="">https://www.openvehicles.com/node/2592</a> shows v3.2.015 since a couple of minutes. Is this the "main” channel</blockquote><br class=""></div><div class="">Usually, unless we explicitly say ’to early access program’.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">changes.txt shows v3.2.015 for 2nd of Sep. Website says 8th…</blockquote><br class=""></div><div class="">The v3.2.015 code was fixed and tagged on 2nd Sep, then release to EAP.</div><div class=""><br class=""></div><div class="">It went to MAIN on 8th Sep (after EAP testing).</div><div class=""><br class=""></div><div class="">Regards, Mark</div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 8 Sep 2020, at 3:47 PM, Soko <<a href="mailto:ovms@soko.cc" class="">ovms@soko.cc</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hey guys,<br class=""><br class="">I'm wondering a while now how the firmware release process is working in OVMS.<br class=""><br class="">I have found in the OVMS settings that I can choose "main", "eap" or "edge" as the update channel...<br class=""><br class="">How does this relate to the github branches?<br class=""><br class=""><a href="https://www.openvehicles.com/node/2592" class="">https://www.openvehicles.com/node/2592</a> shows v3.2.015 since a couple of minutes. Is this the "main" channel? VWUP.OBD is not listed there... but in the user docs it is already: <a href="https://docs.openvehicles.com/en/latest/components/vehicle_vweup_obd/docs/index.html" class="">https://docs.openvehicles.com/en/latest/components/vehicle_vweup_obd/docs/index.html</a><br class=""><br class="">changes.txt shows v3.2.015 for 2nd of Sep. Website says 8th...<br class=""><br class="">Not that all the details here need to be perfectly matching. Was just wondering about a coarse grained info about the process...<br class=""><br class="">thanks<br class=""><br class="">Soko<br class=""><br class="">_______________________________________________<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></div></blockquote></div><br class=""></div></body></html>