<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
"alpha" / "beta" imply some underlying development & release
plan, i.e. a list of features to be reached for the "release"
version.<br>
<br>
"stable" and "nightly" are also used, but "nightly" implies a fixed
schedule -- I'd rather have the option to update manually several
times a day --, and "stable" implies some sort of quality check /
warranty, which we also cannot provide.<br>
<br>
So I think "main" and "edge" are appropriate.<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 16.04.2018 um 03:46 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote type="cite"
cite="mid:B66EC8CD-2ADE-4331-A652-3CBF0D88CABC@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
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.
<div class=""><br class="">
</div>
<div class="">I guess we could address that with v3-beta,
v3-alpha, v4-alpha, etc.</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 16 Apr 2018, at 9:40 AM, Mark Webb-Johnson
<<a href="mailto:mark@webb-johnson.net" class=""
moz-do-not-send="true">mark@webb-johnson.net</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">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.
<div class=""><br class="">
</div>
<div class="">I did consider ‘alpha’, but it just looked
strange to me.</div>
<div class=""><br class="">
</div>
<div class="">The idea is that ‘edge’ will be an
automated (at least) nightly build.</div>
<div class=""><br class="">
</div>
<div class="">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:</div>
<div class=""><br class="">
</div>
<div class="">
<ul class="MailOutline">
<li class="">main</li>
<li class="">eap</li>
<li class="">edge</li>
</ul>
</div>
<div class=""><br class="">
</div>
<div class="">Steve’s alternative would be:</div>
<div class=""><br class="">
</div>
<div class="">
<ul class="MailOutline">
<li class="">main</li>
<li class="">beta</li>
<li class="">alpha</li>
</ul>
</div>
<div class=""><br class="">
</div>
<div class="">Other than ‘main’, these are simple to
change. Happy to go with the consensus...</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.<br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 16 Apr 2018, at 9:26 AM, Stephen
Casner <<a href="mailto:casner@acm.org"
class="" moz-do-not-send="true">casner@acm.org</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">On Mon, 16 Apr 2018, Mark
Webb-Johnson wrote:<br class="">
<blockquote type="cite" class="">From now on,
I’m going to be maintaining two tags for the
production<br class="">
ota server <a
href="http://api.openvehicles.com/"
class="" moz-do-not-send="true">api.openvehicles.com</a>
<<a href="http://api.openvehicles.com/"
class="" moz-do-not-send="true">http://api.openvehicles.com/</a>>.
These<br class="">
are:<br class="">
<br class="">
main: for stable releases<br class="">
edge: for bleeding edge developer releases<br
class="">
</blockquote>
<br class="">
Why not the "standard" terms release (or
stable), beta, alpha?<br class="">
<br class="">
--
Steve_______________________________________________<br
class="">
OvmsDev mailing list<br class="">
<a
href="mailto:OvmsDev@lists.openvehicles.com"
class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
class="">
<a
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br
class="">
OvmsDev mailing list<br class="">
<a href="mailto:OvmsDev@lists.openvehicles.com" class=""
moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
class="">
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="160">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
</body>
</html>