I just started TextMate and it prompted me to install this new version 2.0 beta 12. That's all great. But I'd like to know what changed from the previous version. I've looked at the various TextMate places (textmate.org and github) but can't find any kind of list of "what changed" in the new version, and not even a list of issues that got closed.
Just curious because TextMate is a great tool that I rely on and I'd like to know what's going on.
On 8 Aug 2016, at 22:01, Erik Neumann wrote:
I just started TextMate and it prompted me to install this new version 2.0 beta 12. That's all great. But I'd like to know what changed from the previous version. I've looked at the various TextMate places (textmate.org and github) but can't find any kind of list of "what changed" in the new version, and not even a list of issues that got closed.
From the menu select TextMate → About TextMate → Changes for a list of changes. Here you can also see what changes are happening in bundles (the Bundles tab).
Normally TextMate shows this automatically but anyone who started using TextMate after beta 8.4 (or wiped their settings since this build) would not see the changes.
Future versions will show changes automatically.
On 08 Aug 2016, at 22:17, Allan Odgaard mailinglist@textmate.org wrote:
From the menu select TextMate → About TextMate → Changes for a list of changes. Here you can also see what changes are happening in bundles (the Bundles tab).
Normally TextMate shows this automatically but anyone who started using TextMate after beta 8.4 (or wiped their settings since this build) would not see the changes.
Future versions will show changes automatically.
But not all versions include a changelog, IIRC?
-- /Jacob Carlborg
On 9 Aug 2016, at 9:28, Jacob Carlborg wrote:
But not all versions include a changelog, IIRC?
Correct, especially the nightly builds, I may skip it, and TextMate only show the changelog if it has changed since the user last viewed it.
One can always visit the GitHub page to see exactly which commits a build contains.
On 09 Aug 2016, at 10:21, Allan Odgaard mailinglist@textmate.org wrote:
One can always visit the GitHub page to see exactly which commits a build contains.
Are you sometimes deploying builds without having updated GitHub? I’m pretty sure I’ve seen a new release without seeing any new commits on GitHub.
-- /Jacob Carlborg
On 9 Aug 2016, at 10:26, Jacob Carlborg wrote:
Are you sometimes deploying builds without having updated GitHub? I’m pretty sure I’ve seen a new release without seeing any new commits on GitHub.
That happens, but I always push the release tag, which does push the new commits (just doesn’t update `master`). You can see the tagged commit at https://github.com/textmate/textmate/releases from where it is possible to see the content of the commits.
Hello Allan,
On 09 Aug 2016, at 10:21 AM, Allan Odgaard mailinglist@textmate.org wrote:
But not all versions include a changelog, IIRC?
Correct, especially the nightly builds, I may skip it, and TextMate only show the changelog if it has changed since the user last viewed it.
One can always visit the GitHub page to see exactly which commits a build contains.
On a related note: would it be possible to show the list of changes in the update notification dialog? It always pops up announcing a new version without giving any details besides the version numbers. The user can only learn about the changes after the update is installed.
That's a bit like playing Russian roulette.
A change included in an update might directly influence or even (temporarily) break the user's workflow, see the recent blacklisting of some bundle which broke the workflow of a fellow subscriber here on the mailing list. With knowledge about the changes beforehand the user could defer the update and potentially avoid unnecessary trouble and hassle at an unsuitable point of time (e.g. when busy with important work.) If required, that's it. :-)
regards, Christian
If that worries you, don't subscribe to the nightly builds. The major builds are vetted and safe. m.
On Aug 9, 2016, at 7:00 AM, Christian Rosentreter karibu@gmx.net wrote:
Hello Allan,
On 09 Aug 2016, at 10:21 AM, Allan Odgaard mailinglist@textmate.org wrote:
But not all versions include a changelog, IIRC?
Correct, especially the nightly builds, I may skip it, and TextMate only show the changelog if it has changed since the user last viewed it.
One can always visit the GitHub page to see exactly which commits a build contains.
On a related note: would it be possible to show the list of changes in the update notification dialog? It always pops up announcing a new version without giving any details besides the version numbers. The user can only learn about the changes after the update is installed.
That's a bit like playing Russian roulette.
A change included in an update might directly influence or even (temporarily) break the user's workflow, see the recent blacklisting of some bundle which broke the workflow of a fellow subscriber here on the mailing list. With knowledge about the changes beforehand the user could defer the update and potentially avoid unnecessary trouble and hassle at an unsuitable point of time (e.g. when busy with important work.) If required, that's it. :-)
regards, Christian _______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-- matt neuburg, phd = http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 9! http://shop.oreilly.com/product/0636920044352.do iOS 9 Fundamentals! http://shop.oreilly.com/product/0636920044345.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
That's what I got told when I asked the same thing, still think it would be an awesome feature :)
On Tue, 9 Aug 2016 at 18:35 Matt Neuburg matt@tidbits.com wrote:
If that worries you, don't subscribe to the nightly builds. The major builds are vetted and safe. m.
On Aug 9, 2016, at 7:00 AM, Christian Rosentreter karibu@gmx.net
wrote:
Hello Allan,
On 09 Aug 2016, at 10:21 AM, Allan Odgaard mailinglist@textmate.org
wrote:
But not all versions include a changelog, IIRC?
Correct, especially the nightly builds, I may skip it, and TextMate
only show the changelog if it has changed since the user last viewed it.
One can always visit the GitHub page to see exactly which commits a
build contains.
On a related note: would it be possible to show the list of changes in
the update notification dialog? It always pops up announcing a new version without giving any details besides the version numbers. The user can only learn about the changes after the update is installed.
That's a bit like playing Russian roulette.
A change included in an update might directly influence or even
(temporarily) break the user's workflow, see the recent blacklisting of some bundle which broke the workflow of a fellow subscriber here on the mailing list. With knowledge about the changes beforehand the user could defer the update and potentially avoid unnecessary trouble and hassle at an unsuitable point of time (e.g. when busy with important work.) If required, that's it. :-)
regards, Christian _______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-- matt neuburg, phd = http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 9! http://shop.oreilly.com/product/0636920044352.do iOS 9 Fundamentals! http://shop.oreilly.com/product/0636920044345.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 9 Aug 2016, at 16:00, Christian Rosentreter wrote:
On a related note: would it be possible to show the list of changes in the update notification dialog? It always pops up announcing a new version without giving any details besides the version numbers. The user can only learn about the changes after the update is installed.
That's a bit like playing Russian roulette.
I don’t hope updating TextMate feels like playing Russian roulette :)
As a user I prefer to see the changes after update because I want to update my software, and it can take me longer to read the list of changes than it takes to download the new version, or if the list of changes is long, I’ll read it later.
As a developer having to provide the changes to older clients is a bit of added complexity because I have multiple update channels and I do revise the changes (e.g. the list included with beta 12 is revised compared to the nightly build that preceded it).
As a developer, I would also rather not see people skip updates because they think it brings nothing of interest. The list of changes is somewhat limited to what I want to call attention to, so I generally leave out fixes and changes that are easy to discover.
A change included in an update might directly influence or even (temporarily) break the user's workflow, see the recent blacklisting of some bundle which broke the workflow of a fellow subscriber here on the mailing list.
It “broke” only because I did not mention it in the changes, as the relevant change entry mention that it was simply a blacklist that could be changed by the user.
IOW had the user in question seen the list of changes, it would not have helped, since I had not mentioned it. Once it was mentioned, it should not have made the user skip the update, since it included the proper info about how to override the blacklist.
But if you are on nightly builds and something breaks, you can easily go back to regular builds via Preferences → Software Update → Check Now (TextMate then offers you to downgrade when you click “Check Now”).
Furthermore, if something breaks your workflow, it should be in your interest to report it rather than just stop updating TextMate :)
-
Allan Odgaard -
Christian Rosentreter -
Erik Neumann -
George McGinley Smith -
Jacob Carlborg -
Matt Neuburg