On Jun 24, 6:39 pm, Martin Budden <[email protected]> wrote: > we uploaded 2.5.1 on Monday and were planning to announce that day as > well. Unfortunately a bug was found: upgrading did not work for any > TiddlyWiki that contained non-ascii characters. The decision we took > was: > > i) don't pull the 2.5.1 release > ii) don't announce the upgrade, so we don't get a lot of people upgrading > iii) find a fix as soon as possible, and do a 2.5.2 release containing the fix
Wouldn't it be a wiser choice to announce a release and let volunteers check for bugs for a reasonable time before including it as the upgrade. As an upgrade unsuspecting users would expect that it has already been debugged by a range of experts who have exhaustively tested it. It is understandable that as many people as possible need to try a new release to evaluate it in a variety of uses to debug it. However is it good practice to let people who routinely upgrade be unsuspecting beta users? The practice in the past gave users a choice whether to be testers or not. The changes now are more than routine bug fixes and tweaks, they are a dramatic deviation from what has gone before. There is a big difference between a new release and a routine upgrade. And lacking any commercial or other pressures there is no reason why the upgrade should not lag behind new beta releases by a safe degree. Fortunately the first release, after the reasonably stable 2.5.0, caused several people, that we know of, to denude their TiddlyWiki of content should be a word to the wise. I hope this criticism is considered constructive, Morris On Jun 24, 6:39 pm, Martin Budden <[email protected]> wrote: > Ton, > > we uploaded 2.5.1 on Monday and were planning to announce that day as > well. Unfortunately a bug was found: upgrading did not work for any > TiddlyWiki that contained non-ascii characters. The decision we took > was: > > i) don't pull the 2.5.1 release > ii) don't announce the upgrade, so we don't get a lot of people upgrading > iii) find a fix as soon as possible, and do a 2.5.2 release containing the fix > > We now have a fix, and are planning to do a 2.5.2 release today. > > Sorry about the confusion. > > As for the translation, I'll get an updated version of the English > master version up today. There are a few minor changes compared to > 2.4. > > Martin > > 2009/6/23 Ton van Rooijen <[email protected]>: > > > > > What happened to TW 2.5.0? > > There hasn't been any announcement to the contrary, so TW 2.5.1 is > > supposed to still be Beta. > > On the official homepage of TW however, all of a sudden there is TW > > 2.5.1. > > But in the Timeline in the Sidebar there is no recent change, although > > the NewFeatures-tiddler clearly has been updated. > > Question-1: What's going on? > > Furthermore I noticed the publication of Chinese TWs for 2.5.1, but I > > haven't seen any change in "http://svn.tiddlywiki.org/Trunk/ > > association/locales/core/en/locale.en.js" since TW 2.4. > > Question-2: Do we translaters need to create new versions, and where > > then is our English master-copy, or are there no changes indeed as > > compared to v2.4? > > Btw. don't take me wrong: I'm not criticizing, but since I feel > > responsible for 2 translations I am just curious. > > Thanks in advance for your replies. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWikiDev?hl=en -~----------~----~----~----~------~----~------~--~---
