Jonas Borgström wrote: > Hi all, > > 0.11.3 unfortunately contained a few regressions so we need to get > 0.11.4 out pretty soon. > > Most issues seems to have been fixed in 0.11-stable already but are > there any other bug fixes that need to go into 0.11.4 as well? >
* Stopped sync in 0.11.2.1 http://trac.edgewall.org/ticket/8067 Not sure the proposed patch really helps, as the rollback should happen anyway. Clarification of the installation requirements for MySQL seems to be the really important point there. * Trac does not send object names in quotes to PostgreSQL http://trac.edgewall.org/ticket/7600 ecarter fixed it in r7923, independently from the provided patch, but there's also a contributed unit test on that ticket that could be checked in as well. > And to avoid similar regressions in the future we need to do something > to improve our pre-release testing. > What is the best approach? Pre-release testing checklists, release > candidates or both? > Besides what has already been proposed so far, I'd say we should also make official release candidates (tagged as "rc1"), then freeze the stable branch. If there's no complaints in the next week, which is usually the time frame during which the issues escaping our own testing are found, we simply redo the packages without the "rc1" tag. If a change is needed, the procedure repeats with a "rc2", eventually with a shorter freeze period, if we're confident the fix was trivial (but as usual, beware of trivial fixes ;-) ). -- 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 -~----------~----~----~----~------~----~------~--~---
