As I said in the other thread, I'll take a look ASAP. That is if Deets doesn't beat me to it ;)
If nothing else, I'll merge these in this weekend, but I'm hoping for earlier than that. --Mark On Mon, Jan 25, 2010 at 4:20 AM, Anthony Theocharis <[email protected]> wrote: > I should add that the branch follows up on the following tickets with more > complete solutions and tests: > http://trac.turbogears.org/ticket/2303 > http://trac.turbogears.org/ticket/2313 > > I haven't made a ticket in Trac specifically for this patch-set because > there are a few different issues fixed (in addition to those two). They're > all well described in the commit messages in the branch. > > -- Anthony > > On 24-Jan-10, at 9:28 PM, Anthony Theocharis wrote: >> >> I posted this to the [email protected] list a few days ago, >> having forgotten that we had a specific group for development like this. >> >> Details in the paragraphs below. >> >> -- Anthony >> >> On 21-Jan-10, at 2:14 PM, Anthony Theocharis wrote: >>> >>> On 21-Jan-10, at 2:31 AM, Diez B. Roggisch wrote: >>>> >>>> Hi, >>>> >>>>> I think this is mostly directed at Mark Ramm, but if anyone else has >>>>> authority to approve the changes, I'd love to hear from you. >>>>> >>>>> I've got a bunch of patches (mostly bug fixes, but also patches to >>>>> actually implement routing, all including tests) to TG2 that I'm >>>>> really hoping we can quickly get merged into the TG2.0 official >>>>> branch. >>>>> >>>>> http://bitbucket.org/anthony.theocharis/tg-2_0/ >>>>> >>>>> This is important for me not just because I want to see a functional, >>>>> bug-free TG2.0, but because my company recently launched our first big >>>>> TG2.0 driven open source application (Stuart, our director, posted >>>>> about http://getmediacore.com/ MediaCore the other day), and it really >>>>> needs these fixes to be easily accessible, so other users don't have >>>>> to manually patch TG in order to use the app. >>>> >>>> If you provide them as bundle, I'm happy to apply them if they are >>>> test-covered, and of course don't brake existing tests. >>>> >>>> I can't comment on the when of a TG2.0.4 release though. We ship our own >>>> TG2-egg, and I think you should consider setting up your own package >>>> index >>>> anyway to guarantee stable versions. >>>> >>>> Diez >>> >>> >>> Thanks for the quick reply! Tests are all there, and some of the patches >>> actually fix other tests that were broken in the trunk. >>> >>> What kind of bundle do you need? >>> >>> I can provide separate patches in a .tgz file, but you should be able to >>> merge them in from the forked bitbucket mercurial repository I linked to in >>> the above quote. >>> >>> Thanks again, >>> Anthony > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" 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/turbogears-trunk?hl=en. > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en.
