Thanx for your quick response.

--tags did the trick for the local version when compiling. Nevertheless the tags are not pushed back with "git push origin master" into my fork on github. There the "releases" and "tags" are still on 3.2.010 ...

I will google that ...

Am Mittwoch, den 10.06.2020, 21:17 +0800 schrieb Mark Webb-Johnson:

You probably need to include —tags as an option on your git fetch.

The version is in the tag.

Regards, Mark

On 10 Jun 2020, at 8:59 PM, Chris van der Meijden <chris@arachnon.de> wrote:



Hi all,

sorry for a perhaps silly question, but I don't understand the version numbering between master and fork.

I regulary merge the changes from the ovms repository to my fork. So far so good and I am up to date at the moment. OVMS is now on release 3.2.013. When I perform a pull request on my fork and do a "make" on my local machine, I'm still on release 3.2.010. Even though the code is absolutely up to date.

Could someone give me a hint on how to get the release numbers synced between the ovms master and my fork?

Thanx in advance.

Greetinx

Chris

Am Mittwoch, den 10.06.2020, 07:40 +0200 schrieb Michael Balzer:

Followed.

Regards,
Michael

Am 10.06.20 um 03:28 schrieb Mark Webb-Johnson:

No issues reported, so just released this to MAIN.

Regards, Mark.

On 5 Jun 2020, at 1:15 PM, Michael Balzer <dexter@expeedo.de> wrote:

Followed.

Regards,
Michael

Am 05.06.20 um 07:06 schrieb Mark Webb-Johnson:

I have release this 3.2.013 to EAP.

Regards, Mark.

On 31 May 2020, at 5:34 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Getting ready to release 3.2.013. I’ve tagged it, and built for api.openvehicles.com edge.

The main changes here are:

1. TPMS subsystem (including Tesla Roadster support with new optional K-line expansion board)
2. Change to config for server.v2

For #2, I moved the server password from server.v2/password to password/server.v2, and made the server.v2 config parameter read-write. That better matches how server.v3 does it. The change is done via a config migration, so should be transparent.

Absent any issues, I plan to move to EAP early in the coming week.

Regards, Mark

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev

_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev