This all makes sense to me, with one last question. It seems to me that
there needs to be some way of knowing that a build has been blessed as a
release. For someone on prerelease there doesn't seem to be one. Perhaps
the online release notes could state if a given build is blessed as a
release (so for example the current ones would show B71/3937 (pre-release)?
Thanks for the pointer to Extras, I had assumed it would be with the
updates section under Prefs > Application.
Another suggestion, it would be great if there was some way to know what
commit a build is associated with. Perhaps if they were tagged (or
equivalent) in github. That would make it easier to quickly get to the
right version in github when troubleshooting a build.
PS, Once I get all this I will slap it on the wiki
Thanks!
d
On 12/12/12 1:54 PM, Rob McBroom wrote:
On Dec 12, 2012, at 12:20 PM, David Rees <[email protected]
<mailto:[email protected]>> wrote:
If that has been covered somewhere I apologize, but could someone
summarize the relationships between build numbers, versions, and tags?
Good questions. When you know something, it’s easy to miss that it
isn’t documented anywhere. Thanks for bringing it up.
Build versions are essentially milestones towards a release. They are
given the version number of the upcoming release.
Yes, the version (e.g. B71) is just the public identifier for a
release. The build number (e.g. 3937) is the only thing the update
system considers when comparing versions of the app. Over time, we’ve
come to treat the build number as nothing more than a way to signal to
all the installed copies of the app that they need to update. It means
nothing to humans. More detail on the implications of that below.
I'm not sure how a user can tell if a given build is pre or final
though because the version number is the same. I know some groups use
even/odd to indicate that, but that doesn't seem the case from QS's
release notes.
There’s no difference within the application itself between developer
previews, pre-releases, and final releases. Only the on-line update
system makes a distinction.
We do a pre-release when we think things are pretty solid. We wait for
issues to be reported and fix them where possible. But when we get to
the point where everything looks good, we don’t put out another build
as the final release. We just change the type of update in the on-line
system. If you’re running the pre-release, nothing happens. Those
users configured to only get final releases will now see a new version.
This saves us from having to do another (identical) build, saves users
from having to update again for no real reason, and saves bandwidth.
In terms of in-app updates, is there a way to say if you want
pre-releases or just releases/finals? I thought there was, but I
can't seem to find it now.
Preferences → Extras → Application Update Type
In terms of tags, it seems build versions are tagged with BXX-pre or
BXX-final, but the latest B71/3937 isn't tagged yet. I assume that's
just an oversight?
No, we just don’t know if this one will be final or not so it hasn’t
been tagged. Actually, we now know there will be at least one more B71
pre-release. Probably nothing to do with AppleScript. Sorry. :-)
The “BXX-pre” tag is usually set when we first create the “release”
branch, while the “BXX-final” tag is usually set just before merging
“release” back into “master”.
Also adding to my confusion, the online changelog
http://qsapp.com/changelog.php lists B71/3936.
In the past, that wasn’t updated until a release was final. With B70,
I decided we should do it for pre-releases too, but clearly I forgot
this time. :-) I’ll fix it.
--
Rob McBroom
<http://www.skurfer.com/>
--
You received this message because you are subscribed to the Google
Groups "Quicksilver" group.
To post to this group, send email to
[email protected].
To unsubscribe from this group, send email to
[email protected].
Visit this group at
http://groups.google.com/group/blacktree-quicksilver?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Quicksilver" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
Visit this group at http://groups.google.com/group/blacktree-quicksilver?hl=en.
