The 2.0 development is in a 2.0 branch in svn, and all work in that
branch has been bugfixes.   We should do a release out of that branch
very soon because I *need* one myself, and I won't let anything but
code stability issues block that from happening, and the 2.0 code base
has been stable, so I think that there should not be an issue with
making a release.

We can continue to improve our marketing materials forever, but we
can't keep postponing the release forever ;)

--Mark Ramm

On Sat, May 23, 2009 at 10:07 PM, Luciano Ramalho <[email protected]> wrote:
>
> Hello, I am very glad to see TG2 nearing it's release, but I wonder
> what the pace is at this time, since the homepage [0] still mentions
> an RC1 release dated March 23 with "final release in the next couple
> of weeks".
>
> However, Trac [1] shows no activity on trunk for the last two months.
> I've found a "tg 2.1" repo by Mark Ramm on Bitbucket [2] and that has
> more recent activity.
>
> But where is the actual work being done for the 2.0 release? Have you
> decided to skip that release an go straight to 2.1?
>
> I was at PyCon 2009, talked to Mark once during the sprints, and was
> very happy to learn that TG2 is going well, but the lack of apparent
> progress is worrisome.
>
> I believe it's very important for the Python web story that TG2
> succeeds, but you need to do better in the communications front!
>
> Best regards,
>
> Luciano Ramalho
>
> [0] http://www.turbogears.org/
> [1] http://trac.turbogears.org/browser/trunk
> [2] http://bitbucket.org/mramm/tg-21/
>
> >
>



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

Reply via email to