On 1/20/2011 10:56 PM, Remy Blank wrote:
Christian Boos wrote:
- #9915 : Extend RST to support additional directive types
patch ready, tested by me, to be reviewed
I should be able to review that tomorrow evening, if you want. Or just
apply the patch, and I'll review it on the branch. Maybe you could make
a note on the release ticket to test explicitly for RST rendering?
Speaking of which, we should create the release ticket :)
Done: http://trac.edgewall.org/ticket/9990
As usual, if you find a glitch while testing, please report it on that
ticket.
Besides the testing period of roughly one week, we also do a string
freeze (no more changes on the messages until the release).
I forgot to put the newly extracted .pot in the rc1, but that's on the
0.12-stable branch now (r10468) and as most of our translators have svn
access this shouldn't be a problem anyway. There are not many changes
since 0.12.1, see for example the diff between trac-0.12.1 and latest
0.12-stable for the french translation
(http://trac.edgewall.org/changeset/10469/branches/0.12-stable/trac/locale/fr/LC_MESSAGES/messages.po?old=10469&old_path=/tags/trac-0.12.1/trac/locale/fr/LC_MESSAGES/messages.po).
- #8790 : [PATCH] trac becomes unuseable after entering a log file
path without proper permissions
there's a patch, but it has some issues
I have moved that one to next-major, at least until the patch is
updated. It's really an installation issue in disguise.
OK.
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".
Fully agree.
I've created milestone 0.12.3, we should be conservative about move
tickets there.
After 0.12.2, I guess it's time to start talking about 0.13. It won't be
as "major" as 0.12, but there's still some good stuff in there that we
should ship. I hope we can finish the time fields in time (pun intended).
Yup, there's already some good stuff, and if we finish all that's been
started we'll have a good release worth upgrading to.
The "big" features I hoped for last June (wiki refactoring,
multi-project) won't obviously be there, but that's not a reason to
delay a new major release, especially given the fact that we have some
disruptive changes that are better exposed sooner than later.
Among the "breaking" changes, there's the switch to Python 2.5 and the
removal of Clearsilver.
The switch to 2.5 enabled us to use context managers for the database
transactions and queries, which results in a more optimal use of the
pool (we don't have to rely on the garbage collection of Connection to
put them back in the pool). The earlier we get 0.13, the more time it
gives plugin developers to use the new API and the sooner we can remove
the now deprecated get_db_cnx() API. More details about the changes and
their rationale in TracDev/DatabaseApi (#Trac0.13API and
#PooledConnections).
-- 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.
