Jonas Borgström wrote: > Christian Boos wrote: > >> I propose that we delay 0.10 for one more day or two. >> Now (Monday morning in Europe), we're only starting to see feedback on >> the rc1. >> There's already one that I consider to be critical and which is maybe >> worth some more testing (#3778). >> Others, like #3781 are the kind of polishing that can be quickly done >> and that a "stable" release would deserve. >> > > Yeah, it looks like we might have to delay the release a day or two > after all. since among other things the proposed patch for #3378 hasn't > yet been verified by the reporter, and as far as I can tell not been > tested on all database backends. >
So far I tested it with pysqlite (new env. + ugprade), postgres (only upgrade) and mysql (only new env), but only to see that everything still works, as I didn't have myself an error before the upgrade. On the mysql case, I think this could also solve #3676, as having PRIMARY KEY also enforces a UNIQUE constraints which can't currently be guaranteed if we truncate the paths... > I guess we could wait with this fix until 0.10.1, but in the past we > have tried to avoid changing the db schema on the stable branch. > Yep, that's what I was thinking too, so better fix this now if we can. -- 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 -~----------~----~----~----~------~----~------~--~---
