Remy Blank wrote: > Felix Schwarz wrote: > >> Actually I wanted to reference this ticket but obviously I removed it >> from my email while reworking the text. I wanted to have a bit more >> visibility for this discussion which is why I did not ask in the ticket >> comments. >> > > I do find that this is an important issue to fix. The question is how > complex the solution will be. If we can find a relatively easy solution > (like changing the column type from integer to floating-point) that > works, I'm all for fixing it in 0.12, or possibly in 0.12.1.
If we change the column type, that must be for 0.12, not 0.12.1, as the usual policy is to avoid making db upgrades in minor releases, except for critical issues. > OTOH, if > the solution involves making major changes to the database schema, I > feel that it would be better to postpone that to 0.13. > Yep, that nice little discussion prompted me to make some significant updates to the GenericTrac page, thanks ;-) > What I'm concerned about is the shipping date of 0.12. We should really > concentrate on fixing the remaining critical issues, and IMO this is not > one of them. > Right. Also, quite a number of issues have surfaced for 0.11.6, stability and performance wise, and those currently have highest priority. For 0.12, the priorities are finishing the i18n and multirepos, and more performance related work. After that, lots of exciting work ahead: generic trac, multiproject, new wiki engine, etc. (am I too optimistic here? Well, I didn't say how many more years all this will take ;-) ). -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
