Awesome job guys! Vitaly Babiy
On Sat, Apr 28, 2012 at 9:07 AM, Camilo Nova <camilo.n...@gmail.com> wrote: > Great Job. This will make easier for a lot of people to be involved on the > project. > > > On Friday, April 27, 2012 10:08:09 PM UTC-5, Adrian Holovaty wrote: >> >> On Fri, Apr 27, 2012 at 11:50 AM, Adrian Holovaty <adr...@holovaty.com> >> wrote: >> > We're going to do the migration to GitHub today. This means we'll no >> > longer be committing code to our Subversion repository. Committers, >> > please hold off on making commits until the migration is done. >> >> OK, it's live! >> >> https://github.com/django/**django <https://github.com/django/django> >> >> A few quick points (though this definitely deserves a more in-depth >> writeup): >> >> * I renamed the old (mirror) repository to >> https://github.com/django/**django-old<https://github.com/django/django-old>. >> We had talked about deleting it >> outright to avoid confusion, but I realized at the last minute that >> doing so would have deleted all the pull requests. I didn't want to >> throw all of that out, and I think we can figure out a way to use >> those pull requests in the new repository. >> >> * I only migrated trunk (now called "master"), rather than including >> all of the branches. This was the result of a bunch of discussion on >> IRC with Brian R., et al. The thinking is that it kept the migration a >> lot cleaner/simpler, and we can always add branches later. Of course, >> we'll need to create the latest release branches. Otherwise, we can >> consider the SVN branches on an individual basis. >> >> * As expected, all forks of the old repository are now broken. Can >> somebody volunteer to write some documentation on how to upgrade your >> old fork to use the new upstream repo (rebase? simple patch?)? >> >> * We're going to keep the Subversion repository around indefinitely, >> but it'll no longer be updated. >> >> * We're going to keep using Trac for tickets, but pull requests on >> GitHub are also welcome. >> >> * Clearly there are lots of bits of process that need to be updated >> now, from the django-updates mailing list to our "contributing" >> documentation, etc. We'll take care of all of that in the coming days, >> and we should all expect some degree of confusion and unsettlement in >> the community. That's totally fine, and we'll get through it. :-) >> >> * Finally, big thanks to the folks on IRC today who helped me through >> the process and contributed good ideas. >> >> I'm planning to write up a blog post on how the process went, for the >> benefit of the five open-source projects still using Subversion. >> >> Adrian >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/3AYxf2T_uFgJ. > > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
