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