Hi,

On Thursday October 23, 2008 04:25:47 Mark Ramm wrote:
> I'm working on the docs a lot tonight/tomorrow and I'd rather not try
> to get the docs right for two different releases in 4 days, so I'm
> hoping that it's OK to postpone a TG2 release for a couple more days,
> and just release beta 1 as soon as the docs and tgext.authorization is
> finished.

I think it's OK.

I hope to merge the two branches for the integration of tgext.authentication 
today (the ones for tg.devtools and TG2 itself), so that I can take care of 
the issues I talked about in the thread "Status of tgext.authorization - Help 
needed". After that, we'll be ready regarding tgext.authorization.

> I also went ahead and move the docs out of the TurboGears trunk, and
> fixed up some issues with the full stack tests today.   Tomorrow the
> plan will be to get the wiki back into shape, and to work a bit on
> extending the TW forms doc with some information about filling values
> into forms and other stuff that people have been asking about on the
> list.
>
> If anybody is willing to help out with the FormEncode docs, I would
> really love the help, and Ian said at PloneConf that he'd be more than
> willing to accept documentation help there.   It's one of the less
> well documented pieces of the TG2 dependency chain, and so I really
> want to see what we can do to get it wipped into shape.  And I'd
> mention that this work is helpful to a lot of people including all
> TG2, TG1, and Pylons users.

-- 
Gustavo Narea.
http://gustavonarea.net/

Get rid of unethical constraints! Switch to Freedomware:
http://softwareliberty.com/


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