Re: How often do you update your django?
> So, my specific answer is: use the current revision. update when/if you need > to. Thanks for the advice, both of you - we'll go with the current revision and freeze it there unless we find any problems. Thanks again, Steve --~--~-~--~~~---~--~~ 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: How often do you update your django?
SteveMc wrote: On this topic, our company's moving over to Python and Django. A lot of our developers are understandably wary of using trunk code, but there are a lot of features we'd like that aren't in 0.96. Does anyone have any advice on a trunk revision to stick with that's stable and includes most of the big changes from 0.96? We would rather choose a revision and stick with it rather than taking the risk of being on the bleeding edge. The most important features we'd like are the unicode support and to reduce the API changes when the next release is made. I'm converting a django project that was designed with 0.96 and oldforms. The big part is converting to newforms. It really isn't terribly complicated. Most of the other changes I've made were rather painless. Just test the site after doing an svn up. The things that will be some work to port is when newforms-admin is merged into trunk. I'm not sure if queryset refactor will make any api changes or not. Pretty much everything else is just bugfixes. Not too many backwards incompatible things. One thing I am doing is create an svn checkout for one project I work on. While I'm developing, I keep it on the bleeding edge. Once I'm done with that project, it has its own checkout of django that is the appropriate revision. I can leave the project live on my server for six months, and not worry about it breaking. When/if I have time I can do the svn up, test the code, make any changes, and then put it out there live. It does become a little redundant with each project running on my server with its own checkout of django, but it ensures that things won't break behind my back. So, my specific answer is: use the current revision. update when/if you need to. Good luck! Jeff Anderson signature.asc Description: OpenPGP digital signature
Re: How often do you update your django?
Just take the current revision, it is as stable as any other revision(probably moreso), I would stick to that, and track the trunk and if a new feature comes out that you want, review the backwards incompatible changes page, and then SVN up. On Apr 2, 12:02 pm, SteveMc <[EMAIL PROTECTED]> wrote: > On this topic, our company's moving over to Python and Django. A lot > of our developers are understandably wary of using trunk code, but > there are a lot of features we'd like that aren't in 0.96. Does anyone > have any advice on a trunk revision to stick with that's stable and > includes most of the big changes from 0.96? We would rather choose a > revision and stick with it rather than taking the risk of being on the > bleeding edge. The most important features we'd like are the unicode > support and to reduce the API changes when the next release is made. > > Thanks, > > Steve --~--~-~--~~~---~--~~ 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: How often do you update your django?
On this topic, our company's moving over to Python and Django. A lot of our developers are understandably wary of using trunk code, but there are a lot of features we'd like that aren't in 0.96. Does anyone have any advice on a trunk revision to stick with that's stable and includes most of the big changes from 0.96? We would rather choose a revision and stick with it rather than taking the risk of being on the bleeding edge. The most important features we'd like are the unicode support and to reduce the API changes when the next release is made. Thanks, Steve --~--~-~--~~~---~--~~ 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: How often do you update your django?
Svn externals for django, so i update pretty much continously. Can't go without those sweet and new feautures :) Besides Django trunk is pretty stable --~--~-~--~~~---~--~~ 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: How often do you update your django?
And if you are on windows, TortoiseSvn is a great way to get strated with svn. On Mar 26, 3:06 pm, James Tauber <[EMAIL PROTECTED]> wrote: > It might be worth adding that this approach works for Django because > development takes place on branches not the trunk. Other open source > projects may use the trunk for development, in which case what people > are saying about how often they update Django won't apply to those > projects. > > Just thought I'd add that as the original poster is new to getting > stuff from svn. > > James > > On Mar 25, 2008, at 12:58 PM, Justin Lilly wrote: > > > I update it every time I'm reminded of it (I just updated), at the > > end of a sprint or when I get errors (in hopes it was a bug that was > > fixed). > > > -justin > > > On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop > > <[EMAIL PROTECTED]> wrote: > > > How often do you use svn to get the latest django and update your > > implementation? I'm new to all of this and never have used cvs or svn > > and am trying to figure out the best way to use it. > > > -- > > Justin Lilly > > Web Developer/Designer > >http://justinlilly.com --~--~-~--~~~---~--~~ 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: How often do you update your django?
It might be worth adding that this approach works for Django because development takes place on branches not the trunk. Other open source projects may use the trunk for development, in which case what people are saying about how often they update Django won't apply to those projects. Just thought I'd add that as the original poster is new to getting stuff from svn. James On Mar 25, 2008, at 12:58 PM, Justin Lilly wrote: > I update it every time I'm reminded of it (I just updated), at the > end of a sprint or when I get errors (in hopes it was a bug that was > fixed). > > -justin > > On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop > <[EMAIL PROTECTED]> wrote: > > How often do you use svn to get the latest django and update your > implementation? I'm new to all of this and never have used cvs or svn > and am trying to figure out the best way to use it. > > > > > -- > Justin Lilly > Web Developer/Designer > http://justinlilly.com > > --~--~-~--~~~---~--~~ 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: How often do you update your django?
cd into the directory where you have django, then do svn update, it will update the checkout there. To be able to this you can not have used setup.py instead you should be symlinking django/ into your site- packages directory. On Mar 25, 2:31 pm, jmDesktop <[EMAIL PROTECTED]> wrote: > How do you do this? I tried and just ended up with svn cohttp://and > got my latest copy .97. I then deleted the old directory django and > copied the new one. I thought I could do svn up somehow, but couldn't > figure it out. > > On Mar 25, 3:09 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > I update pretty much daily locally, I'm going to be deploying a site > > pretty soon and I doubt that I will update it ever except for security > > released, qs-rf, and nfa merges, and of course if I need to update the > > site with a new feature. > > > On Mar 25, 1:04 pm, "Joseph Heck" <[EMAIL PROTECTED]> wrote: > > > > Justin does have a very valid point here - there's a LOT of > > > functionality that isn't in the 0.96.1 release, and there's no word on > > > when a next release will be coming. Just make sure you keep up with > > > changes in the trunk when the developers get into making backwards > > > incompatible updates. > > > > -joe > > > > On Tue, Mar 25, 2008 at 10:40 AM, Justin Lilly <[EMAIL PROTECTED]> wrote: > > > > I would suggest the exact opposite, really. I found it much harder in > > > > terms > > > > of documentation / help with .96 than trunk. Besides, hearing "Oh. > > > > You're on > > > > .96? You don't have that feature." can get a bit tiresome. > > > > > In terms of updating, its (for me) as easy as going to the directory and > > > > running git-svn fetch (or most probably in your case: svn up ). > > > > > -justin > > > > > On Tue, Mar 25, 2008 at 1:26 PM, Joseph Heck <[EMAIL PROTECTED]> wrote: > > > > > > It's more than a file - it's more like a directory :-) > > > > > > If you're new to django, you might find it a lot easier to start with > > > > > the release version. The trunk has been reasonably stable lately, but > > > > > there's no promise that it will remain so - and you might find > > > > > yourself in a bind if you loose track of the trunk for a while and > > > > > don't keep up with changes. They can be backward incompatible. > > > > > > -joe > > > > > > On Tue, Mar 25, 2008 at 10:23 AM, jmDesktop <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > Do you just copy over the old file and restart your server? > > > > > > > On Mar 25, 12:58 pm, "Justin Lilly" <[EMAIL PROTECTED]> wrote: > > > > > > > I update it every time I'm reminded of it (I just updated), at > > > > > > the > > > > end of a > > > > > > > sprint or when I get errors (in hopes it was a bug that was > > > > > > fixed). > > > > > > > > -justin > > > > > > > > On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > How often do you use svn to get the latest django and update > > > > > > your > > > > > > > > implementation? I'm new to all of this and never have used > > > > > > cvs or > > > > svn > > > > > > > > and am trying to figure out the best way to use it. > > > > > > > > -- > > > > > > > Justin Lilly > > > > > > > Web Developer/Designerhttp://justinlilly.com > > > > > -- > > > > Justin Lilly > > > > Web Developer/Designer > > > > >http://justinlilly.com-Hide quoted text - > > > - Show quoted text - --~--~-~--~~~---~--~~ 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: How often do you update your django?
How do you do this? I tried and just ended up with svn co http://and got my latest copy .97. I then deleted the old directory django and copied the new one. I thought I could do svn up somehow, but couldn't figure it out. On Mar 25, 3:09 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I update pretty much daily locally, I'm going to be deploying a site > pretty soon and I doubt that I will update it ever except for security > released, qs-rf, and nfa merges, and of course if I need to update the > site with a new feature. > > On Mar 25, 1:04 pm, "Joseph Heck" <[EMAIL PROTECTED]> wrote: > > > > > Justin does have a very valid point here - there's a LOT of > > functionality that isn't in the 0.96.1 release, and there's no word on > > when a next release will be coming. Just make sure you keep up with > > changes in the trunk when the developers get into making backwards > > incompatible updates. > > > -joe > > > On Tue, Mar 25, 2008 at 10:40 AM, Justin Lilly <[EMAIL PROTECTED]> wrote: > > > I would suggest the exact opposite, really. I found it much harder in > > > terms > > > of documentation / help with .96 than trunk. Besides, hearing "Oh. You're > > > on > > > .96? You don't have that feature." can get a bit tiresome. > > > > In terms of updating, its (for me) as easy as going to the directory and > > > running git-svn fetch (or most probably in your case: svn up ). > > > > -justin > > > > On Tue, Mar 25, 2008 at 1:26 PM, Joseph Heck <[EMAIL PROTECTED]> wrote: > > > > > It's more than a file - it's more like a directory :-) > > > > > If you're new to django, you might find it a lot easier to start with > > > > the release version. The trunk has been reasonably stable lately, but > > > > there's no promise that it will remain so - and you might find > > > > yourself in a bind if you loose track of the trunk for a while and > > > > don't keep up with changes. They can be backward incompatible. > > > > > -joe > > > > > On Tue, Mar 25, 2008 at 10:23 AM, jmDesktop <[EMAIL PROTECTED]> > > > wrote: > > > > > > Do you just copy over the old file and restart your server? > > > > > > On Mar 25, 12:58 pm, "Justin Lilly" <[EMAIL PROTECTED]> wrote: > > > > > > I update it every time I'm reminded of it (I just updated), at the > > > end of a > > > > > > sprint or when I get errors (in hopes it was a bug that was fixed). > > > > > > > -justin > > > > > > > On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > How often do you use svn to get the latest django and update your > > > > > > > implementation? I'm new to all of this and never have used cvs > > > > > or > > > svn > > > > > > > and am trying to figure out the best way to use it. > > > > > > > -- > > > > > > Justin Lilly > > > > > > Web Developer/Designerhttp://justinlilly.com > > > > -- > > > Justin Lilly > > > Web Developer/Designer > > > >http://justinlilly.com- Hide quoted text - > > - Show quoted text - --~--~-~--~~~---~--~~ 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: How often do you update your django?
I update pretty much daily locally, I'm going to be deploying a site pretty soon and I doubt that I will update it ever except for security released, qs-rf, and nfa merges, and of course if I need to update the site with a new feature. On Mar 25, 1:04 pm, "Joseph Heck" <[EMAIL PROTECTED]> wrote: > Justin does have a very valid point here - there's a LOT of > functionality that isn't in the 0.96.1 release, and there's no word on > when a next release will be coming. Just make sure you keep up with > changes in the trunk when the developers get into making backwards > incompatible updates. > > -joe > > On Tue, Mar 25, 2008 at 10:40 AM, Justin Lilly <[EMAIL PROTECTED]> wrote: > > I would suggest the exact opposite, really. I found it much harder in terms > > of documentation / help with .96 than trunk. Besides, hearing "Oh. You're on > > .96? You don't have that feature." can get a bit tiresome. > > > In terms of updating, its (for me) as easy as going to the directory and > > running git-svn fetch (or most probably in your case: svn up ). > > > -justin > > > On Tue, Mar 25, 2008 at 1:26 PM, Joseph Heck <[EMAIL PROTECTED]> wrote: > > > > It's more than a file - it's more like a directory :-) > > > > If you're new to django, you might find it a lot easier to start with > > > the release version. The trunk has been reasonably stable lately, but > > > there's no promise that it will remain so - and you might find > > > yourself in a bind if you loose track of the trunk for a while and > > > don't keep up with changes. They can be backward incompatible. > > > > -joe > > > > On Tue, Mar 25, 2008 at 10:23 AM, jmDesktop <[EMAIL PROTECTED]> > > wrote: > > > > > Do you just copy over the old file and restart your server? > > > > > On Mar 25, 12:58 pm, "Justin Lilly" <[EMAIL PROTECTED]> wrote: > > > > > I update it every time I'm reminded of it (I just updated), at the > > end of a > > > > > sprint or when I get errors (in hopes it was a bug that was fixed). > > > > > > -justin > > > > > > On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop <[EMAIL PROTECTED]> > > wrote: > > > > > > > How often do you use svn to get the latest django and update your > > > > > > implementation? I'm new to all of this and never have used cvs or > > svn > > > > > > and am trying to figure out the best way to use it. > > > > > > -- > > > > > Justin Lilly > > > > > Web Developer/Designerhttp://justinlilly.com > > > -- > > Justin Lilly > > Web Developer/Designer > > >http://justinlilly.com --~--~-~--~~~---~--~~ 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: How often do you update your django?
Justin does have a very valid point here - there's a LOT of functionality that isn't in the 0.96.1 release, and there's no word on when a next release will be coming. Just make sure you keep up with changes in the trunk when the developers get into making backwards incompatible updates. -joe On Tue, Mar 25, 2008 at 10:40 AM, Justin Lilly <[EMAIL PROTECTED]> wrote: > I would suggest the exact opposite, really. I found it much harder in terms > of documentation / help with .96 than trunk. Besides, hearing "Oh. You're on > .96? You don't have that feature." can get a bit tiresome. > > In terms of updating, its (for me) as easy as going to the directory and > running git-svn fetch (or most probably in your case: svn up ). > > -justin > > > On Tue, Mar 25, 2008 at 1:26 PM, Joseph Heck <[EMAIL PROTECTED]> wrote: > > > > > It's more than a file - it's more like a directory :-) > > > > If you're new to django, you might find it a lot easier to start with > > the release version. The trunk has been reasonably stable lately, but > > there's no promise that it will remain so - and you might find > > yourself in a bind if you loose track of the trunk for a while and > > don't keep up with changes. They can be backward incompatible. > > > > -joe > > > > > > > > > > On Tue, Mar 25, 2008 at 10:23 AM, jmDesktop <[EMAIL PROTECTED]> > wrote: > > > > > > Do you just copy over the old file and restart your server? > > > > > > > > > On Mar 25, 12:58 pm, "Justin Lilly" <[EMAIL PROTECTED]> wrote: > > > > I update it every time I'm reminded of it (I just updated), at the > end of a > > > > sprint or when I get errors (in hopes it was a bug that was fixed). > > > > > > > > -justin > > > > > > > > > > > On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop <[EMAIL PROTECTED]> > wrote: > > > > > > > > > How often do you use svn to get the latest django and update your > > > > > implementation? I'm new to all of this and never have used cvs or > svn > > > > > and am trying to figure out the best way to use it. > > > > > > > > -- > > > > Justin Lilly > > > > Web Developer/Designerhttp://justinlilly.com > > > > > > > > > > > > > > > > > > > > > > > -- > Justin Lilly > Web Developer/Designer > > http://justinlilly.com > > > --~--~-~--~~~---~--~~ 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: How often do you update your django?
I would suggest the exact opposite, really. I found it much harder in terms of documentation / help with .96 than trunk. Besides, hearing "Oh. You're on .96? You don't have that feature." can get a bit tiresome. In terms of updating, its (for me) as easy as going to the directory and running git-svn fetch (or most probably in your case: svn up ). -justin On Tue, Mar 25, 2008 at 1:26 PM, Joseph Heck <[EMAIL PROTECTED]> wrote: > > It's more than a file - it's more like a directory :-) > > If you're new to django, you might find it a lot easier to start with > the release version. The trunk has been reasonably stable lately, but > there's no promise that it will remain so - and you might find > yourself in a bind if you loose track of the trunk for a while and > don't keep up with changes. They can be backward incompatible. > > -joe > > On Tue, Mar 25, 2008 at 10:23 AM, jmDesktop <[EMAIL PROTECTED]> > wrote: > > > > Do you just copy over the old file and restart your server? > > > > > > On Mar 25, 12:58 pm, "Justin Lilly" <[EMAIL PROTECTED]> wrote: > > > I update it every time I'm reminded of it (I just updated), at the > end of a > > > sprint or when I get errors (in hopes it was a bug that was fixed). > > > > > > -justin > > > > > > > > On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop <[EMAIL PROTECTED]> > wrote: > > > > > > > How often do you use svn to get the latest django and update your > > > > implementation? I'm new to all of this and never have used cvs or > svn > > > > and am trying to figure out the best way to use it. > > > > > > -- > > > Justin Lilly > > > Web Developer/Designerhttp://justinlilly.com > > > > > > > > > > > > > -- Justin Lilly Web Developer/Designer http://justinlilly.com --~--~-~--~~~---~--~~ 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: How often do you update your django?
It's more than a file - it's more like a directory :-) If you're new to django, you might find it a lot easier to start with the release version. The trunk has been reasonably stable lately, but there's no promise that it will remain so - and you might find yourself in a bind if you loose track of the trunk for a while and don't keep up with changes. They can be backward incompatible. -joe On Tue, Mar 25, 2008 at 10:23 AM, jmDesktop <[EMAIL PROTECTED]> wrote: > > Do you just copy over the old file and restart your server? > > > On Mar 25, 12:58 pm, "Justin Lilly" <[EMAIL PROTECTED]> wrote: > > I update it every time I'm reminded of it (I just updated), at the end of a > > sprint or when I get errors (in hopes it was a bug that was fixed). > > > > -justin > > > > > On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop <[EMAIL PROTECTED]> wrote: > > > > > How often do you use svn to get the latest django and update your > > > implementation? I'm new to all of this and never have used cvs or svn > > > and am trying to figure out the best way to use it. > > > > -- > > Justin Lilly > > Web Developer/Designerhttp://justinlilly.com > > > > > --~--~-~--~~~---~--~~ 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: How often do you update your django?
Do you just copy over the old file and restart your server? On Mar 25, 12:58 pm, "Justin Lilly" <[EMAIL PROTECTED]> wrote: > I update it every time I'm reminded of it (I just updated), at the end of a > sprint or when I get errors (in hopes it was a bug that was fixed). > > -justin > > On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop <[EMAIL PROTECTED]> wrote: > > > How often do you use svn to get the latest django and update your > > implementation? I'm new to all of this and never have used cvs or svn > > and am trying to figure out the best way to use it. > > -- > Justin Lilly > Web Developer/Designerhttp://justinlilly.com --~--~-~--~~~---~--~~ 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: How often do you update your django?
I update it every time I'm reminded of it (I just updated), at the end of a sprint or when I get errors (in hopes it was a bug that was fixed). -justin On Tue, Mar 25, 2008 at 12:50 PM, jmDesktop <[EMAIL PROTECTED]> wrote: > > How often do you use svn to get the latest django and update your > implementation? I'm new to all of this and never have used cvs or svn > and am trying to figure out the best way to use it. > > > -- Justin Lilly Web Developer/Designer http://justinlilly.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
How often do you update your django?
How often do you use svn to get the latest django and update your implementation? I'm new to all of this and never have used cvs or svn and am trying to figure out the best way to use it. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
