On Sun, Mar 14, 2010 at 12:35 AM, Krishnakant Mane <[email protected]> wrote:
> So are we expecting to have a final release of pylons 1.0 soon? > Is there a document listing of exact changes I need to do if at all I plan > to upgrade my old application? The links I posted earlier have all the information. It may not be a simple checklist format, but that's why 1.0 final has not been released yet, because the documentation isn't finished. This is not Django. :) We don't have perfectly polished documentation, or a single checklist listing everything that might possibly go wrong and what to do about it. The compexity of using third-party packages means that we may not be able to list every single change that has happened in them. As always with upgrading, plan some extra time to test the application and fix whatever might break. If you find problems that aren't addressed in the docs, ask about them here. But there's no hurry to upgrade. 0.9.7 won't be disappearing anytime soon. The only reason to upgrade is if you want to, or if you're making major changes to the application anyway. > I am thinking of writing all my newer apps using 1.0 release. > In any case testing with the beta is not a bad idea. There's no reason to write a new application with 0.9.7 or 0.10 now. 1.0 will be released by the time your application is. Just use the development version (Mercurial), which is as good as the latest beta or RC. (Pylons has a policy of checking in only changes that pass the tests. So it's rare for a checkin to *increase* bugs, although it's not impossible. Also, Pylons has not had a major restructuring for over a year, so each checkin is just one small change.) -- Mike Orr <[email protected]> -- 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.
