Christian Boos wrote: > Besides that, I'll go through some of the pending patches that can > finished soon, then upgrade the version numbers, prepare the beta > release and get some feedback from the field.
I have just updated the version numbers. > And then, what I'd really like to finish before the final 1.0 are the > other tickets listed in TracDev/ToDo#Trac1.0. I have triaged my remaining tickets for 1.0 (and fixed a few) this week-end, and I'm down to the following: - http://trac.edgewall.org/ticket/7145 (concurrent edits) I have implemented the "revert" operation for individual changes, and I'm quite happy with the result. Patch available for review. - http://trac.edgewall.org/ticket/10451 (DB access in upgrade check) Patch available for review that should at least mitigate the issue. - http://trac.edgewall.org/ticket/7894 (X-Sendfile) Patch refreshed and ready for testing. Unfortunately, I still don't have a setup to test it. I will try to set this up this week, but I won't be angry if anyone beats me to it :) It's very low risk, as the code won't be active if `[trac] use_xsendfile = false` (the default). So from my side, all I need is some review and testing, and I'm done. I see there are currently 58 tickets assigned to milestone 1.0. I have created a temporary milestone "1.0-triage" and moved most of the tickets with no recent activity there, for later triage. To prepare for 1.0, I suggest we keep only those tickets on 1.0 that we know we will fix before the release. This leaves us with 15 tickets (including the 3 above). I'd like to ask each of the owners to go through your tickets in 1.0 and move those that you don't think you can fix within a week or two to a different milestone. You may also want to browse through 1.0-triage to make sure I didn't move any important ones out. But please only move tickets to 1.0 if you are confident that you will fix them shortly. This should leave us with very few tickets, and we can hope to fix them all in a short time, therefore opening the way to a 1.0beta1 release in the very near future. Oh, and one more thing: batch modifications rock! Thanks Peter for integrating this very useful feature. -- Remy
signature.asc
Description: OpenPGP digital signature
