[Ovmsdev] Time for release 3.2.016?

[Mark Webb-Johnson]

Craig,

> What's the status of the "for-v3.3" branch?

That’s on me. I’ve been ill for the last month (not COVID, thankfully), and master has diverged from for-v3.3 causing conflicts. I hope to resolve this week.

> Another question I had is what is the difference between:


The v3.0 / v3.1 / v3.2 in the URL path refers to the _hardware_ version, not firmware. For all current hardware we should be using:

http://api.openvehicles.com/firmware/ota/v3.1/ <http://api.openvehicles.com/firmware/ota/v3.1/>...

The v3.2 path is not currently used. I’ve renamed it as ‘v3.2.obsolete’ in api.openvehicles.com <http://api.openvehicles.com/> to try to avoid confusion.

Regards, Mark

> On 8 Feb 2021, at 10:11 AM, Craig Leres <leres at xse.com> wrote:
> 
> 
> What's the status of the "for-v3.3" branch? Last weekend after I upgraded the esp32-wroom module in my dev ovms box I tried updating and I couldn't get it to run. It would be nice to get the simcom refactoring into master (or at least catch for-v3.3 up with things like the persistent metrics update, etc). I'm not advocating this for 3.2.016, just expressing an interest in it happening in the near term.
> 
> Another question I had is what is the difference between:
> 
>    http://api.openvehicles.com/firmware/ota/v3.1/main/ovms3.bin
>    http://api.openvehicles.com/firmware/ota/v3.1/main/ovms3.ver
> 
> and:
> 
>    http://api.openvehicles.com/firmware/ota/v3.2/main/ovms3.bin
>    http://api.openvehicles.com/firmware/ota/v3.2/main/ovms3.ver
> 
> The v3.1 version currently points to 3.2.15 and the v3.2 version points to 3.2.008 which wasn't what I was expecting when I was looking for a 3.2.008 image to flash in the factory partition of my modules.
> 
> 		Craig
> _______________________________________________
> 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/20210208/fa10d9b7/attachment-0001.htm>