-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Terje S. wrote: > On Thu, Jul 08, 2010 at 12:41:21AM +0200, Steffen Hoffmann wrote: >> Don't let this be your last word on this topic. > > With John kindly proposing his time, maybe it's not! [...]
Right, so let the "shooting" end and the coding begin. :-) >> That said I like your idea about bringing Trac's database to a (more) >> relational structure. Even if I'm not remotely trained to do i/o related >> programming with Python, I wouldn't mind lending a helping hand for testing. > > That's great news, thank you for offering :) Yeah, since I'm a Mercurial fellow I'll have to see how to interface with Git, once you branch at Github, but this should be doable. [...] > Can anyone demonstrate prior art of a project that successfully acheived such > a feat with an incremental approach? > > Rewrite is the only cost-effective way, in terms of reaching the stated > final goals of the project. If you are not doing the rewrite, you must > change the goals (or knowingly spend your time with very low ROI). > > I dispute your case that this functionality is realistically present today at > all. Please show 20 different lists, each containing a combo of 5 or more > plugins from trac-hacks or elsewhere, that will work as flawlessly as you > describe in a move from 0.11 to 0.12 in a production environment today ;-) I'll not take the time to exactly do that, but tell you, about what I experienced on moving to 0.12 instead. This is what I use: Abbr - Macro (0.11.1) Access (0.1) AccountManager (0.2.1dev-r7165) Acronyms (0.1) AdvancedTicketWorkflow - Plugin (0.10dev-r3940) AllAttachments - Macro Anchor Announcer - Plugin (0.12-p2) AutocompleteUsers (0.4.1) BackLinks BackLinksMenu BreadCrumbsNav - Plugin (0.1-p1dev-r3065) cc-selector (0.0.2) CustomFieldAdmin (0.2.2-p1) DateField (1.0.1) Developer (0.2) FlexibleAssignTo (0.6) FlexWiki - Plugin (0.2dev-r5589) FootNote - Macro (1.0) ForceComment (0.1-p1) graphviz (0.7.6dev) KeywordSuggest (0.2) LogViewer - Plugin (0.2) OverrideEdit - Plugin (0.0.2) PDFRedirector (0.1) PdfRenderer - Plugin (0.0) PermRedirect (2.0-p1) SampleValidOwnerProvider (0.5-p1) Screenshots (0.7-p2) SecurePluginPanel (0.11.5-r276) ServerSideRedirect - Plugin (0.3.7303) STractistics (0.4.3) SubTickets - Plugin (0.1.1.dev-20100527) Tags (0.6) ticket-clone (Rev) TicketTemplate (0.6) Toc - Macro (11.0.0.3) Watchlist - Plugin (0.4.7110dev-r7110) WikiCalendar - Macro WikiRename (2.1.1-p1) WikiTicketCalendar - Macro (1.1.6dev) The single space indentation mark only partial use. Double space mark no use, since I wasn't able to configure/make it work at all - regardless of the Trac version. I had to find a fixed version or fix it myself for Watchlist WikiTicketCalendar for the new POSIX microseconds date/time values, noticed no others breaking so far. Even if all the marked macros/plugins would end up as "broken by upgrade", the list would still show a quite impressive number = smooth transition from 0.11 to 0.12, right? That there might be no prior case of seamless upgrades is always _not_ true. Look i.e. at the Debian GNU/Linux distribution. As long as you stick to the stable release, they test and test and test to guarantee for inexpensive incremental full system dist-upgrades. There is always a user/admin-friendly plan. You even need a reboot only in case you switch the Linux kernel in this process. I own a system I did install back in 1999 and just upgraded, not re-installed, until today. Hardware got old or broken, but the system never broke or got cluttered by unused files too much. I think I still got your points about the house, the Trac system, the least expensive way to develop, etc. Even if all the above doesn't count for your, I've just suggested to keep migration in mind, if we come to migration planning. I'll support any experimental branch, but in the end we should do better than just recommending a start from zero for someone asking about project migration. This is b/w by intention, I know, Trac developers can and will do much better, regardless what others do or did before. Sincerely Steffen Hoffmann (hasienda) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkw1zIAACgkQ31DJeiZFuHddDwCdG2Uc7zwSgA5P/J3iR+WXBNMH if0An1Samxsd8K+finj5vXX9EMsYODnu =TnNQ -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-...@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
