Confusion over builds.
richmondmathewson at gmail.com
Tue May 24 18:25:55 CEST 2016
I honestly don't know what you are talking about. Here:
I can see 8.0.1 STABLE and 8.1.0 RC1
So, there is no "8.0.2" and no "8.10"
Over in GitHub things are, by the nature of GitHub, likely to be
somewhat more confusing.
This is one of the main reasons when I want to find out the way the
numbering of Livecode
releases is going I stick to the download page.
Certainly, I can see that one could, carelessly, mistake "8.1.0" for
"8.10", but, then, things are always
worth a second look.
"start with removing those builds that are actually released"
No, let's NOT, and let's use them as the road-map, and not the others:
otherwise we'd still all
be sitting around waiting for Hypercard 3.0.
My computers (that means about 4 of the things) and my external
hard-disks are littered with
oddly numbered versions of my Devawriter Pro; some of them did lead to
releases; most of them
are where I went off on some "very clever tangent" which turned out to
be a big mistake.
I would suppose most people have similar situations, unless, unlike me,
they have the self-discipline
to purge their systems of all those "also rans". This is a bit like
evolution; the man with teeth in his bottom
died out (right organ, wrong end of the body); or, if you are a
creationist; please do not tell me that God
didn't fool around with ideas that seemed extremely good on day 4, but
looked pretty awful on the morning of day 5.
After all, we are, supposedly, made in his own image :-)
GitHub is the land of possibilities; and 'tis a marvellous place; but
not for the nervous.
On 24.05.2016 17:24, James Hale wrote:
> Now that 8 is out,things on GitHub should be simpler, right?
> No, not really.
> We still have 8.01rc1 sitting there.
> We have 802rc1 sitting there.
> 8.10dp1 AND 8.10dp2 AND 8.10 future?
> While I really like the action happening I wish we could collapse things a bit and get the different branches consistent.
> For instance let's start with removing those builds that are actually released.
> That would leave us with 8.02rc1, 8.1dp2 and 8.10 future (whatever this is supposed to mean).
> Then could be get some guidance as to whether 8.1 contains the fixes in 8.02 or not.
> In other words, if 8.02 fixes something we wanted fixed but we also want to test against 8.1, can we count on not having worry about a missing fix?
> Which gets me to my main hope. Could we perhaps release the rc' a bit more frequently? I mean there was only one rc for 8.01 and now we are already almost up to 8.02rc1 but before it was released we get an 8.1dp1.
> Can't you move the unfinished bits of 8.02rc1 into a future 8.02rc2 and get 8.02rc1 out?
> Will there be an 8.02rc2 or will you jump to 8.03rc1? Sort makes the 'rc' labels superfluous.
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode