News for hackers. Stuff that matters.
Re:Moving Django to GitHub: the postmortem by zem on Saturday April 28, 2012 @10:46PM (#3904911)
is it really valuable to keep the svn repository up for scripts that do automatic updating? since nothing further will ever be pushed to it, those scripts are now tracking an increasingly out-of-date repo.

the other point of view is that there are servers that the admin has had a reasonable expectation of being able to set up and let run itself, but those servers shouldn't be pulling from anyone's svn repo anyway.

Re:Moving Django to GitHub: the postmortem by yuvadam on Sunday April 29, 2012 @09:16AM (#3905909)
Off the top of my head, here's one (somewhat) common use case that can break:

    pip install -e svn+http://code.djangoproject.com/svn/django/trunk#egg=django
It's definitely reasonable to keep the old repo up, for this case, and others.
Re:Moving Django to GitHub: the postmortem by zem on Sunday April 29, 2012 @10:00AM (#3905980)
but that is now getting an old version of django. is that really what is wanted?
Re:Moving Django to GitHub: the postmortem by StavrosK on Sunday April 29, 2012 @11:59AM (#3906258)
If you're getting a specific version, sure.