Feeling a little sheepish here, myself. I keep my plugin development TW upgraded to the latest beta (mostly so I know if any of the plugins break), but I had always updated that file the "old" way. Wasn't aware of the "BetaUpgradePlugin" existence, and it never occurred to me to look for a way to use backstage to keep my dev TW updated.
When I updated my "real" TW documents to 2.5.1, I was hit by the bug. I would have been hit by it during the beta period if I had upgraded my test TW with backstage too. Live and learn, I guess. At least I have the "plugin" installed in it now. On Jun 24, 8:06 am, FND <[email protected]> wrote: > > 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. > > Well, that's what the beta period is for. We'd love to get more > participation in that from the community. > The upgrade bug wasn't picked up during that period mainly because it > only affects documents with non-ASCII characters. If there were more > people willing to engage in beta testing, that would likely have been > noticed. > > -- F. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
