I totally understand how that goes! Chris has done a wonderful job on
2.1, and we're mostly very very happy with it. Especially the speed
improvements!
We've updated our previous ticket on routing issues with this latest
problem, and a patch we think should resolve it (including a test case
and a sample app):
http://trac.turbogears.org/ticket/2428
I still would love to hear from someone about a rough time estimate for
another 2.1 release. Also, anything I can do to help drive this process
forward, I am happy to do.
--
Jonathan LaCour
http://cleverdevil.org
Michael Pedersen wrote:
Chris Perkins has been the primary driver for 2.1. He's also been having
some real life issues holding him up in many ways, so hasn't been very
active on IRC or on the ML.
I'm just hoping that RL stops smacking him around soon, so we can get
him back.
I'd offer to take over for him for now, but have my own RL issues
hitting me. I've got ear surgery tomorrow, followed by the recuperation
time from that. By the end of the month, I'm hoping to have RL back in
order, so I can contribute and maybe take some of the load off him.
Between now and then, hopefully I'll complete enough of my own TG
extension that it can be useful for others. I'll be releasing the first
version of that during the beginning of next week.
On Thu, Jan 14, 2010 at 11:33 AM, Jonathan LaCour
<[email protected] <mailto:[email protected]>>
wrote:
Replying to myself here. Any updates on TG 2.1? The silence on this
has been pretty deafening :)
Also, we've discovered another bug with the new routing, and will be
posting a ticket, test case, and patch shortly.
--
Jonathan LaCour
http://cleverdevil.org
Jonathan LaCour wrote:
Greetings!
Things have been quiet in the TG world of late (at least on the
mailing
lists), and I wanted to check in and see what the status is on
TurboGears 2.1b1. Specifically, I'd like to know what the release
timeline looks like, and if the following tickets will be closed
as part
of the release:
http://trac.turbogears.org/ticket/2409
http://trac.turbogears.org/ticket/2428
My team created both of these tickets, and provided patches for both
problems, so I'd love to see them included in the release.
We're working on our schedule for pushing out the next few
versions of
our software, and it'd be great to have some rough timelines to base
things off of.
Thanks for all of your hard work! I'll be at PyCon this year
(speaking
about TG and ShootQ), and would love to buy a round of drinks
for any
TurboGears developers :)
--
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]
<mailto:[email protected]>.
To unsubscribe from this group, send email to
[email protected]
<mailto:turbogears-trunk%[email protected]>.
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk?hl=en.
--
Michael J. Pedersen
My IM IDs: Jabber/[email protected]
<mailto:[email protected]>, ICQ/103345809, AIM/pedermj022171
Yahoo/pedermj2002, MSN/[email protected]
<mailto:[email protected]>
------------------------------------------------------------------------
--
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.
--
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.
