Alberto,

On 3/26/07, Alberto Valverde <[EMAIL PROTECTED]> wrote:
>
>
> I think we all agree on this. The port to CherryPy 3 is almost done
> in the cp3 branch, just needs the tests adapted as the current ones
> are too closely tied with CP2's internals (I'll give a shot at this
> in a few days) and widgets ported from 1.0 as the ones in trunk give
> the wrong impression if being 100% usable with Genshi which is not
> the case.
>
> Once this is done we can merge that branch with the trunk and release
> a 1.1 alpha. This reminds me of something important: Any patches that
> are merged from 1.0 to trunk should also go into the cp3 branch until
> it's merged. Hopefully this situation will end soon but please try to
> keep an eye on it now so we don't miss anything.


If I am to work on CP3 branch, what's the procedure?

Are there any cp3-specific tickets? Do I need to do any merging from 1.0?



> I think we should release 1.0.2 ASAP (at least give it a date) and
> > toward next step, ex: test CP3 branch and make some docs about genshi/
> > sqlalchemy,
>
> There are a couple of pending tickets and patches which need to be
> commented on, applied or discarded. New features should not be
> committed IMO unless they are 99% risk free and obviously missing
> from what the API suggests should be possible (I know, this can be
> very  subjective.... that's what this ML is for... :)


What are those tickets? Can I help?

Thanks,
Max.

P.S.: I am in process of starting another TurboGears project and I want it
to be on 1.0.2 with SA, Genshi and CP3, just like the rest of us. ;) The
client is willing to sponsor some of the work.

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