On 10/10/07, Ben Sizer <[EMAIL PROTECTED]> wrote: > [...]
> > What is the status of 1.1? How many changes to 1.0 code are typically > needed? Does it aid eventual migration to 2.0? And is it even > imminent? Unless I've missed something (which is entirely possible, I We will begin the real work on the 1.1 version when 1.0.4 final is out. We still have one or two details to manage for the release (http://trac.turbogears.org/ticket/1310_ and friends. Remove the _ at the end of the URL, it is meant as an antispam method) but it should be for the end of this week or so... > concede), there was supposed to be a beta released 'in the next few > weeks', which was about 4 months ago. The beta for 1.1 will then appear a short time behind, but we have some changes that will break some things in the 1.0 based app. I already talked of this on this list but should post a good explanation when 1.0.4 final is released. Basically, 1.1 will introduce SQLAlchemy as the default orm (using the 0.4 API) and thus will break code based on the 0.3 version. The good thing is that since 1.0.4beta1 you can already install SQLAlchemy 0.4 and make your application ready to go for 1.1 Next breaking change will certainly (still in testing...) be the removal of the implicit transactions (in SA at the least) and session. This means people who want transactions will just create their own in the beginning of their controller code and then rollback or commit according to their need. For the session it is even easier, if you need one you'll just use create_session from turbogears.database... (still in testing lab but will be there for sure). This change will make TG code easier to maintain and understand for human beings and will allow for future evolutions in a much cleaner way. > > As someone who cannot develop web apps full time, I need to know that > the proverbial rug will not be pulled out from under my feet if it > takes me 6 months to finish my project. I don't expect things to be > fully stable, but I'd at least like to know which of the various > moving targets it's best to aim for. 1.0 is stable. 1.0.4 should be out pretty soon and will let you migrate to SA 0.4 if you want without imposing you the burden if don't want. 1.1 will break the things I mentioned above, but we will provide migration advices to change your app so it can run on 1.1. If the breakage is too much of a burden you will have the choice to stay on 1.0 for a least one or two years... This is the time we plan supporting the 1.0 stack. 2.0: Mark has already answered :) As per the evolution path. As you see, 1.0 and 1.1 are already being though with an evolution path. 1.1 is meant to help migrate to 2.0. I don't know the full details yet, but the implicit transaction going out and the implicit session creation are good examples of things that could help. Since 1.1 will provide also genshi (and we hope toscawidgets) by default, it will be one more step further in the direction of 2.0. I hope I clarified the situation a bit :) Don't hesitate to ask more questions, we'll be pleased to answer you. Florent. PS: I should say that the documentation team did a wonderful job on our documentation pages and many things which where not explained at all are now explained in details in the wiki. I know of someone who made me this remark that the doc was poor (He will recognize himself). When I prompted him to look again in the wiki he was surprised by the quantity and quality of the documentation compared to what he remembered being present. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
