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.

I guess we could address that with v3-beta, v3-alpha, v4-alpha, etc.

Regards, Mark

On 16 Apr 2018, at 9:40 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

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.

I did consider ‘alpha’, but it just looked strange to me.

The idea is that ‘edge’ will be an automated (at least) nightly build.

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:

  • main
  • eap
  • edge

Steve’s alternative would be:

  • main
  • beta
  • alpha

Other than ‘main’, these are simple to change. Happy to go with the consensus...

Regards, Mark.

On 16 Apr 2018, at 9:26 AM, Stephen Casner <casner@acm.org> wrote:

On Mon, 16 Apr 2018, Mark Webb-Johnson wrote:
From now on, I’m going to be maintaining two tags for the production
ota server api.openvehicles.com <http://api.openvehicles.com/>. These
are:

main: for stable releases
edge: for bleeding edge developer releases

Why not the "standard" terms release (or stable), beta, alpha?

                                                       -- Steve_______________________________________________
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