On Tuesday 11 September 2007, Christian Boos wrote: > > Noah Kantrowitz wrote: > > Actually kill the AJAX one, the stuff I was going to commit into it I > > ended up figuring out how to degrade. > > > > Ok, done in r6002 and r6003 (in r6004, I removed the obsolete > sandbox/security branch as well). > There's even now a http://trac.edgewall.org/wiki/TicketNinja page > awaiting some docs (a screenshot will be a good start). > > Another remark about branches: I'm fully +1 for creating branches as one > sees fit in the sandbox, but not just to declare the intent of some > future changes, only when there's some actual changes to check-in.. I > hate to "svn update sandbox" (yes, I have a full checkout of the sandbox > ;-) ) just to get one more pristine copy of trunk (wiki-blame and > notification are the one left in this situation). > > Also, I couldn't relate the milestone-edit-tmp branch with a ticket... > any hint?
That one's mine. And I'd forgotten to get back to it. There is no ticket for it. The core of the changes can be seen with: svn diff -x -b https://svn.edgewall.com/repos/trac/[EMAIL PROTECTED] https://svn.edgewall.com/repos/trac/sandbox/milestone-edit-tmp Basically, we have two independent implementations of 'edit a milestone'. That branch was an attempt to consolidate them. The problem I was running into was returning the user to the appropriate page after editing the milestone, since we have two ways to get to the same functionality. Looks like bringing the branch up-to-date with trunk has a conflict with trac/upgrades/db20.py (newline change?) which I can fix up in a bit. Eli --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
