Hello Trac-Devs,
It would be nice to finalize our next stable release, milestone 0.12.2.
We have fixed 46 tickets so far, some corresponding to annoying bugs, a
lot more to minor defects, and we have a few new niceties as well. Here
are some highlights:
- improved robustness of Trac installation if Babel is installed after
the fact
- support for Asian character width in notification e-mails
- fix display of milestone progress bar in some corner cases and
respect the overall_completion milestone group setting
- reports and queries look much better, as the columns now keep the
same width across groups; the absence of word wrapping in reports has
been fixed
- improved layout for the admin pages
- ... and more!
Well, a correct ChangeLog entry still needs to be written ;-)
At this time, there are 5 tickets opened:
- #9915 : Extend RST to support additional directive types
patch ready, tested by me, to be reviewed
- #8790 : [PATCH] trac becomes unuseable after entering a log file
path without proper permissions
there's a patch, but it has some issues
- #9705 : Deadlock in delete_session_cookie with MySQL backend
patch ready, tested on t.e.o 0.12 instances - no issues, should be
tested by reporter but no feedback yet
- #9961 : first time easy_install won't compile the catalogs
patch ready, tested, should be ready to commit
- #9916 : TimeoutError: Unable to get database connection within 0
seconds.<trac.core.TracError instance at 0xa19044c>
not fully reproducible, will likely be postponed
The bulk of the changes to the TracGuide in the wiki have already been
synchronized and once the above patches are committed, we'll be ready
for a 0.12.2rc1 version, which will also correspond to a *string freeze*.
After our usual week of testing and the 0.12.2 release itself, I would
say we should really focus on 0.13 and put 0.12-stable in "low
maintenance mode". For this to happen, 0.12.2 really needs to be rock
solid, so please already plan some time ahead for testing 0.12.2rc1 once
it becomes available in a few days.
0.12.3 and further 0.12.x releases are still expected in a 2-3 months
cycle if there's nothing urgent to fix in between, but I don't see much
work happening there. There were 65 tickets for 0.12.1, 51 for 0.12.2,
and I'd like to see this drop to 20 or less for the next minor releases.
This means that most of the remaining next-minor-0.12.x tickets will
likely become next-minor-0.13.x. ones.
Doing a quick triaging to see if we didn't miss anything important (with
a high severity and low effort thereby still worthy of doing for
0.12.2), I see:
- #9907 : PostreSQL error upgrading from 0.11.1 to 0.12 on table
attachment
doc fix mentioning we don't support PostgreSQL 7.x anymore
I think that's about it?
-- 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.
