[Ovmsdev] 3.2.018 release and upcoming 3.3

[Michael Balzer]

EU server now also has 3.2.018 released in "main".

https://dexters-web.de/firmware-release-3.2.018-text_101.en.htm

Regards,
Michael


Am 07.12.21 um 01:36 schrieb Mark Webb-Johnson:
> I have released 3.2.018 to main OTA now, and announced it. @Michael 
> please follow with your EU server. Thanks to everyone that contributed 
> to this.
>
> The certification for our upcoming 3.3 hardware has been fully 
> completed, and results published. You can see the FCC stuff by:
>
>     https://www.fcc.gov/oet/ea/fccid <https://www.fcc.gov/oet/ea/fccid>
>
>     Grantee Code: 2ATDM
>     Product Code: OVMS-33-7
>
>
> Hardware is in production and should be generally available later this 
> month. We have been affected by some component chip shortages, but I 
> am told those have been resolved. We need to release the 3.3 firmware 
> to the factory later this week (or first thing next).
>
> Regards, Mark
>
> On 18 Nov 2021, at 3:06 PM, Mark Webb-Johnson <mark at webb-johnson.net 
> <mailto:mark at webb-johnson.net>> wrote:
>>
>>
>> We need to get the v3.3 release ready for release now, as the new 
>> v3.3 hardware is about to enter production and the factory needs the 
>> firmware.
>>
>> Accordingly, I suggest:
>>
>>  1. I have already updated the for-v3.3 branch with all the recent
>>     changes from v3.2.
>>
>>  2. We now (today/tomorrow) release the current v3.2 branch as tag
>>     3.2.018, OTA release. This would be the (hopefully) last v3.2
>>     release.
>>
>>  3. After release of that, we branch off master to a v3.2 branch, for
>>     historical purposes (and if we need it for anything).
>>
>>  4. We then merge back for-v3.3 into the master branch and start
>>     working through the usual daily builds for that to get it ready
>>     for production. I think there is still some work to do on pouring
>>     the plugins, but the core code (and in particular new modem
>>     support) should be ok now.
>>
>>
>> I think we will need to investigate an approach for dual builds for 
>> v3.3-or-later and pre-v3.3 hardware, to take advantage of the new 
>> ESP32 rev3 chips. I think those will require a different sdkconfig. 
>> We can do that automatically in the OTA system, by building the URL 
>> based on the ESP32 platform revision. Should we do that with the v3.3 
>> release (even if the builds are for the moment the same), or at a 
>> later date?
>>
>> Regards, Mark.
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20211208/431b7813/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20211208/431b7813/attachment.sig>