Disregard, I was on the wrong branch (master vs release). Here is the right one - https://github.com/quicksilver/Quicksilver/blob/release/Quicksilver/SharedSupport/CHANGELOG.
On Saturday, January 12, 2013 9:25:44 PM UTC-5, David Rees wrote: > > On a related note, where is http://qsapp.com/changelog.php generated > from? I found > https://github.com/quicksilver/Quicksilver/blob/master/Quicksilver/SharedSupport/CHANGELOG, > > but it hasn't been updated since B70. > > I'm interested because I want to see what changed in 3939 from 3938. > > Thanks, > dave > > On Wednesday, December 12, 2012 4:11:04 PM UTC-5, Rob McBroom wrote: >> >> On Dec 12, 2012, at 3:03 PM, David Rees <[email protected]> wrote: >> >> > 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. >> >> Not a good one. The most reliable way is to check the downloads page and >> see if the available version is the one you’re running. There will also be >> at least one tweet from LoveQuicksilver and probably an announcement here >> when the release goes final. >> >> You can also look at the same place the application checks. >> http://qs0.qsapp.com/plugins/check.php should always show the build >> number for the latest final release. >> >> > 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)? >> >> Maybe. That file is generated from a version controlled file, but isn’t >> version controlled itself, so I’m more willing to change it. But that’s one >> more step we might forget, and if you’re willing to go to a web page to >> find out, you could just go to the downloads page or the other link above. >> :-) >> >> > Thanks for the pointer to Extras, I had assumed it would be with the >> updates section under Prefs > Application. >> >> Your assumption makes more sense than the reality. Not sure why it’s >> under Extras or how hard it would be to move, but we should. All that >> results list stuff (under Command) should go under Appearance, too. >> >> > 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. >> >> We could tag them with build numbers I guess, but if we write good commit >> messages, you should be able to tell from that. For instance, >> https://github.com/quicksilver/Quicksilver/commit/1389340076c5ed808fec9b47b736e98ccddf1a1a >> >> >> (That’s on the release branch. Maybe you were looking at master?) >> >> -- >> 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.
