On 10/16/2011 9:07 PM, Remy Blank wrote:
I would like to release 0.12.3 in the very near future, as we have quite
a lot of fixes in there that I would like to push to our users.

We are currently down to 10 open tickets, some already containing
patches that just need to be applied,

Down to 6...

I also think we should enter string freeze by now and make a call to the translators.

I tried to look at the stats on Transifex, but somehow the interface has changed and I didn't find yet a way to trigger an update of the stats, as they seem quite out of date.

The translation stats from 0.12-stable at r10856,
as obtained via `make summary` and sorted:

----------------------------------------
l10n/sv: translations updated (99%)
l10n/ja: translations updated (99%)
l10n/fr: translations updated (99%)
l10n/en_GB: translations updated (99%)
l10n/de: translations updated (99%)
l10n/ru: translations updated (98%)
l10n/pt_BR: translations updated (98%)
l10n/hu: translations updated (98%)
l10n/es_AR: translations updated (98%)
l10n/ca: translations updated (98%)
l10n/tr: translations updated (97%)
l10n/it: translations updated (97%)
l10n/he: translations updated (97%)
l10n/zh_TW: translations updated (95%)
l10n/zh_CN: translations updated (95%)
l10n/sl: translations updated (95%)
l10n/nl: translations updated (95%)
l10n/hy: translations updated (95%)
l10n/es: translations updated (95%)
l10n/eo: translations updated (95%)
l10n/cs: translations updated (95%)
l10n/nb: translations updated (94%)
l10n/fi: translations updated (87%)
l10n/pl: translations updated (76%)
l10n/ko: translations updated (62%)
l10n/gl: translations updated (58%)
l10n/vi: translations updated (40%)
l10n/el: translations updated (39%)
l10n/fa: translations updated (35%)
l10n/pt: translations updated (34%)
l10n/ro: translations updated (29%)
----------------------------------------

(well r10856 actually added a message ;-) )



others that still require a bit of
work. They are currently assigned as follows:

cboos:
------
http://trac.edgewall.org/ticket/9976

This is an issue with authz checks and intra-repository copies.
Christian, what's the way forward?

So the idea is now to keep the semantic of the checks as close as possible as Subversion does. Basically this means giving up on checking the create_path/rev. I've not looked yet at the code change implied.



http://trac.edgewall.org/ticket/10048

This is actually already fixed. One question is pending, whether or not
`Href` should prevent from generating URLs with empty segments. We don't
currently use empty segments, but we do use an empty trailing segment,
leading to a trailing /. I would suggest leaving the code as-is.

We should be more conservative about the kind of links we generate.
If some are known to be problematic, better be restrictive and not generate them. This means applying Remy's patch.



http://trac.edgewall.org/ticket/10121

This is an issue with the timeline and repository browser with
repository names containing non-ASCII characters. This requires some
more work. I may try to look into this.


I suspect this is related to the above to the extent the generated links are not seen in the browser the same way they're generated, but I can be wrong as I didn't take the time yet to work on that one. So feel free to look into this.


fschwarz:
---------
http://trac.edgewall.org/ticket/10137
http://trac.edgewall.org/ticket/10400

Both tickets are minor translation issues. Felix, could you please make
a decision for each and apply any remaining changes?


Not a blocker but still would be nice if done during the string freeze.



jomae:
------

There's now http://trac.edgewall.org/ticket/7821
which is on the way to be fixed again.

I would like to ask each of the ticket owners to either apply their
patches, or to comment on their tickets how they want to move forward
(and possibly move tickets to later milestones if necessary). The goal
would be to be down to zero tickets within one or two weeks, so that we
can do a string freeze, followed by a week of testing and translation,
and finally a nice 0.12.3 release.

Testing! Testing! We want testing!


I would also like to push 0.13 closer to a release, but that's a subject
for another e-mail :)

0.13, the unlucky release ;-)

-- 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.

Reply via email to