> History for those components will not be migrated. Is there some reason why you would discard this information? Is it not correct? Even if it's very old, the modification history can be *vital* to determining what changed and why.. and, VERY old versions of TiddlyWiki are still relevant. (I just responded to a question about someone using TW1.2.12, from 2006). Please don't throw away the past in an attempt to move towards a better future.
> trac and the tickets therein will also be frozen in a read only state. > tickets will _not_ be migrated. The goal here is to get rid of stale > tickets and the most straightforward way to do that is to let > important tickets be recreated, in the github issues system[1]. I *strongly* object to this. There are HUNDREDS of open tickets that have simply been deferred over and over and over again, due to "short term priorities" at Osmosoft. These tickets may be old, but they are NOT irrelevant. In many cases, there are extensive discussions and detailed information in these tickets, not only about the outstanding problems, but also, in many cases, solutions that can be readily implemented *if* there is the will to do so! Forcing the re-entry of all of this information is NOT the way to review the issues. Certainly, some of these open tickets are not important any more, but that cannot be said for MOST of them. Perhaps there is a way to migrate the tickets but declare them as 'migrated' and subject to review before being marked as 'active'. -e -- 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.
