www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting" <jukka.zitt...@gmail.com>
Subject Re: [scm] Use case: code review/audit/study
Date Wed, 12 Mar 2008 17:48:12 GMT
Hi,

On Wed, Mar 12, 2008 at 5:46 PM, Justin Erenkrantz
<justin@erenkrantz.com> wrote:
> On Wed, Mar 12, 2008 at 6:03 AM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
>  >  Could we streamline this process somehow in cooperation with the
>  >  Cenqua people? For example, could we decide some "safe hours" when it
>  >  would be OK for Cenqua to do the initial FishEye import of an Apache
>  >  project without an explicit OK or ACK from Infrastructure?
>
>  Due to their past behavior, the Cenqua team *wants* an explicit ACK so
>  we don't block them again.  =)
>
>  Adding a new project to Fisheye is not frequent enough that we need to
>  change anything, IMO - they're fine and we're fine with explicit
>  sign-off.

Cool if everyone's fine with that.

I assume the bulk load issue would affect also people doing git-svn
imports or other similar things that need the full version history of
a project. See below for a quick draft of an FAQ entry on the current
best practice as far as I've understood it.

Are there other things we could do to reduce the hit from such bulk
load operations? I know there was the initiative to provide copies of
the entire repository to interested parties for research purposes, but
I guess that doesn't apply to the random developer who wants to
experiment with a cool new visualization tool.

Would it for example be possible to provide periodic (say montly)
per-project repository dumps? I'm not sure how technically feasible
that would be and how easy it would be to use such dumps to bootstrap
things like FishEye or git-svn.

BR,

Jukka Zitting


Index: dev/version-control.xml
===================================================================
--- dev/version-control.xml     (revision 636431)
+++ dev/version-control.xml     (working copy)
@@ -262,6 +262,19 @@
 mailing list.
         </p>
     </section>
+
+    <section id="bulk">
+        <title>
+          May I do bulk loads like extracting the entire version history
+          (including diffs) of an Apache project?
+        </title>
+        <p>
+Preferably not. Bulk access puts a lot of load on our repository, and should
+only be used for a good reason. Please
+<a href="http://www.apache.org/dev/infra-mail.html#lists">contact</a>
+the Apache Infrastructure team for an OK before proceeding with a bulk load.
+        </p>
+    </section>
 </section>
 </body>
 </document>

Mime
View raw message