On Mar 12, 2010, at 10:46 AM, Krishnakant Mane wrote: > Ic, this means even pylons 1.0 is RC just like 0.10.
Right, Pylons 1.0 is prolly ready to go straight to final release at this point, just a few remaining documentation updates, but the code itself is fine. Pylons 0.10 might need an RC2 as there's one remaining bug that was fixed for legacy notices. The only known incompatibility at this point is that toscawidgets is NOT compatible with Pylons 1.0. This is because its still relying on Buffet, which has been deprecated since 0.9.7. I'm hoping that toscawidgets get a fix for this and is released soon to address it. > I wan't like to have some unpredictible problems during development, just to > know that its a bug to be resolved in the final release or even worst, I > might discover a so far unknown problem and it might stop the development of > that module or any further dependent modules which needed that broken > feature. If the Pylons development team does not fear any such major > show-stopper with the RC, I think I don't mind. As you rightly said, an > application won't go live on production server till it is completely tested > in terms of its functinality. So if pylons version 1 is not recommended for > production now, I am ok with it. I don't see that as being very likely. Also, I'm aiming to increase releases post-1.0, so if there's a bugfix you can quickly update to 1.0.1, etc. without worrying about other feature changes. Cheers, Ben -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
