Re: Status of the trunk? Ok to use it?
Hello, > However, that doesn't mean that Django trunk is unstable - it just > means you need to be careful to check the changelogs before you do an > SVN update, because an update could have consequences that require > some fixes to your application. If you keep a close eye on the > changesets, and follow the advice on the wiki page, using and tracking > the SVN trunk should not be a major problem. Whether this is feasible > depends entirely on how much time you are able to dedicate to checking > and fixing the consequences of following the changes required by > trunk. Sorry for the long time after your answer. Thanks a lot for the info, I will go the trunk way with regular updates as for the moment it is not for production purposes that I need it. That way I will be able to report bugs too. Thanks, loïc --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Status of the trunk? Ok to use it?
On 5/8/07, Loïc d'Anterroches <[EMAIL PROTECTED]> wrote: > > Hello, > > As of the 6th of April I read that it was maybe not that good to use > the trunk as under heavy changes[1]. But looking at the incompatible > changes page[2] it looks like it is not that heavy (I have already a > small app running using the newforms) for the moment. I just wonder if > a big storm is planned and I have better to stick on a given changeset > or following the stream of changes seams feasible. "Heavy" is a relative term. There have been more backwards incompatible changes in the last month than there were in the entire 0.95 development process. There are still a few more changes to come. We (the core developers) are very conscious of the fact that people are using Django on live projects. Given that we knew in advance that there were some backwards-incompatible changes in the pipeline, we warned people that there were going to be some changes, and if they are relying upon Django for a production site, it might be wise to use the 0.96 stable release for a while (or at least, stop updating SVN regularly). However, that doesn't mean that Django trunk is unstable - it just means you need to be careful to check the changelogs before you do an SVN update, because an update could have consequences that require some fixes to your application. If you keep a close eye on the changesets, and follow the advice on the wiki page, using and tracking the SVN trunk should not be a major problem. Whether this is feasible depends entirely on how much time you are able to dedicate to checking and fixing the consequences of following the changes required by trunk. Yours, Russ Magee %-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Status of the trunk? Ok to use it?
Hello, As of the 6th of April I read that it was maybe not that good to use the trunk as under heavy changes[1]. But looking at the incompatible changes page[2] it looks like it is not that heavy (I have already a small app running using the newforms) for the moment. I just wonder if a big storm is planned and I have better to stick on a given changeset or following the stream of changes seams feasible. Thanks, loïc [1] http://www.djangoproject.com/weblog/2007/apr/06/changes/ [2] http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
