On Wed, Feb 16, 2011 at 7:00 AM, Darren Dale <dsdal...@gmail.com> 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. 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 ------------------------------------------------------------------------------ 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 Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
