Text of discourse.matplotlib.org › t › git-migration-this-weekend › 14933 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

git migration this weekend - matplotlib-devel - Matplotlib

git migration this weekend Development matplotlib-devel _Darren_Dale2 January 28, 2011, 2:34am 1 Hi Folks, I'm planning on freezing the sourceforge svn repository Friday evening at 8:00 (NY time), and moving the git repository to its new home on Saturday morning. If you have concerns, please speak up. Darren _Darren_Dale2 January 30, 2011, 1:10pm 2 John discovered a problem with some very early project history that was lost several years ago during the CVS to Subversion migration.

We have an opportunity to recover it during the git migration. However, do to a recent attack, Sourceforge has taken their CVS service down, and based on the latest information at SourceForge Community Blog - What's new on SourceForge.net , they do not expect it to be back before late this week. I do not think I will available to work on the migration this upcoming weekend, Feb 4-6. So it will probably be February 7 or 8 before I have a chance to try to recover the old history, convert the repos to git, and post them to github.

Darren ··· On Thu, Jan 27, 2011 at 9:34 PM, Darren Dale < [email protected] ...> wrote: Hi Folks, I'm planning on freezing the sourceforge svn repository Friday evening at 8:00 (NY time), and moving the git repository to its new home on Saturday morning. If you have concerns, please speak up. _Darren_Dale2 February 16, 2011, 1:00pm 3 It looks like the history we were looking for does not exist in the CVS repository either.

John, could you freeze the svn repo around noon on Friday? I'll convert the repositories and push them up to github on Saturday. Is it possible to close the sourceforge bugtracker, feature requests, etc to new issues as well? Darren ··· On Sun, Jan 30, 2011 at 8:10 AM, Darren Dale < [email protected] ...> wrote: On Thu, Jan 27, 2011 at 9:34 PM, Darren Dale < [email protected] ...> wrote: Hi Folks, I'm planning on freezing the sourceforge svn repository Friday evening at 8:00 (NY time), and moving the git repository to its new home on Saturday morning.

If you have concerns, please speak up. John discovered a problem with some very early project history that was lost several years ago during the CVS to Subversion migration. We have an opportunity to recover it during the git migration. However, do to a recent attack, Sourceforge has taken their CVS service down, and based on the latest information at SourceForge Community Blog - What's new on SourceForge.net , they do not expect it to be back before late this week.

I do not think I will available to work on the migration this upcoming weekend, Feb 4-6. So it will probably be February 7 or 8 before I have a chance to try to recover the old history, convert the repos to git, and post them to github. _Fernando_Perez1 February 16, 2011, 5:39pm 4 Hey, John, could you freeze the svn repo around noon on Friday? I'll convert the repositories and push them up to github on Saturday. Is it possible to close the sourceforge bugtracker, feature requests, etc to new issues as well? are you guys planning on transfering the old bugs to github?

As I mentioned, I have code lying around for the upload (and to download from launchpad, but that's irrelevant here). I'm going to be mosly offline til Monday (conference trip), but if someone pings me on my Berkeley email address, which I monitor even while traveling, I'll be happy to help out. Glad to see eveythong moving over to github! (since scipy is also about to do the same, as soon as 0.9 is out, for which things are already at the RC stage).

A huge thank you to Darren for putting so much hard work into this, I admire your attention to detail (and I wish I'd been so thorough when I transitioned ipython, where we could have recovered from some old history problems, but I'm too lazy for that :). Cheers, f ··· On Wed, Feb 16, 2011 at 5:00 AM, Darren Dale < [email protected] ...> wrote: _Darren_Dale2 February 16, 2011, 6:38pm 5 are you guys planning on transfering the old bugs to github?

Probably at some point. As I mentioned, I have code lying around for the upload (and to download from launchpad, but that's irrelevant here). I'm going to be mosly offline til Monday (conference trip), but if someone pings me on my Berkeley email address, which I monitor even while traveling, I'll be happy to help out. Thanks, that would be very helpful. I'll follow up once I figure out how to extract the information from sourceforge.

Glad to see eveythong moving over to github! (since scipy is also about to do the same, as soon as 0.9 is out, for which things are already at the RC stage). A huge thank you to Hang on, don't jinx it. Darren ··· On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez < [email protected] ...> wrote: _John_Hunter February 16, 2011, 6:57pm 6 I did some poking around and do not see an easy way to freeze the repo. I can disable it, but then I think it won't be available for read access.

One thing I could do is remove commit privs for every developer, making the repo read only going forward. This seems like a reasonable approach. As for the tracker, similarly, I see how to disable it but not to freeze it so that no new issues can be added. Anyone seeing things differently? JDH ··· On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale < [email protected] ...> wrote: John, could you freeze the svn repo around noon on Friday?

I'll convert the repositories and push them up to github on Saturday. Is it possible to close the sourceforge bugtracker, feature requests, etc to new issues as well? Eric_Firing2 February 16, 2011, 7:19pm 7 are you guys planning on transfering the old bugs to github? Probably at some point. As I mentioned, I have code lying around for the upload (and to download from launchpad, but that's irrelevant here). I'm going to be mosly offline til Monday (conference trip), but if someone pings me on my Berkeley email address, which I monitor even while traveling, I'll be happy to help out.

Thanks, that would be very helpful. I'll follow up once I figure out how to extract the information from sourceforge. Darren, Just a heads-up on that: In November the tracker was heavily spammed. Recently I marked a few hundred items with the "delete" disposition, but I don't think that actually gets rid of them. If it doesn't, then maybe they can be filtered out during the transfer. Eric ··· On 02/16/2011 08:38 AM, Darren Dale wrote: On Wed, Feb 16, 2011 at 12:39 PM, Fernando Perez< [email protected] ...> wrote: Glad to see eveythong moving over to github! (since scipy is also about to do the same, as soon as 0.9 is out, for which things are already at the RC stage).

A huge thank you to Hang on, don't jinx it. Darren ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Matplotlib-devel mailing list [email protected] matplotlib-devel List Signup and Options _Sandro_Tosi3 February 16, 2011, 7:30pm 8 a pre-commit hook that just "exit 1" ? it prevents commits but not checkouts.

Just my 2c, ··· On Wed, Feb 16, 2011 at 19:57, John Hunter < [email protected] ...> wrote: On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale < [email protected] ...> wrote: John, could you freeze the svn repo around noon on Friday? I'll convert the repositories and push them up to github on Saturday. Is it possible to close the sourceforge bugtracker, feature requests, etc to new issues as well? I did some poking around and do not see an easy way to freeze the repo.

I can disable it, but then I think it won't be available for read access. One thing I could do is remove commit privs for every developer, making the repo read only going forward. This seems like a reasonable approach. -- Sandro Tosi (aka m

The rest of this page is on the live site.