On 5/4/06, Tim Peters <tim.peters at gmail.com> wrote: > > Since I hope we see a lot more of these problems in the future, what Me too. > can be done to ease the pain? I don't know enough about SVN admin to > know what might be realistic. Adding a pile of "temporary > committers" comes to mind, but wouldn't really work since people will > want to keep working on their branches after the sprint ends. Purely > local SVN setups wouldn't work either, since sprint projects will > generally have more than one worker bee, and they need to share code > changes. There: I think that's enough to prove I don't have a clue I guess that means it's my turn to let my ignorance shine yet again. :-) Could we take a snapshot of the SVN repo, hosted on python.org, open it up for public commit during the period? That seems easy to setup. The difficulty would come in when we need to merge back to the real SVN. n
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4