You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Stein <gs...@gmail.com> on 2009/11/09 15:46:18 UTC

[RFC] source repository at Apache

Hi all,

This request-for-comment is about our svn repository on the ASF
hardware. There are two primary options:

1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
is the "big mother" repository with all ASF projects and 834k
revisions in it

2) svn.apache.org/repos/$VAR -- our own repository, potentially
running a custom server


The ASF Infrastructure Team would mildly prefer (1), but would be fine
if we want (2).

There were several svn committers present at a meeting with Infra last
Thursday to discuss these possibilities: cmpilato, dlr, gstein,
jerenkrantz, jrepenning. The recommendation from those present is to
go with the primary repository. This reco comes from a number of
factors:

* standard procedures for Infra. we'll never be forgotten

* in one repository, we can shift code to/from other projects (e.g
should our mod_* move to httpd?)

* Infra is willing to run our release candidates on the main repos, so
we don't need a special server for that. they're pretty much willing
to run anything we ask for (alpha? beta?), but that obviously means we
better be *damned* sure it won't lose or corrupt the repo :-)

* probably more I forgot


Please discuss, comment, etc. I'll run a vote as appropriate;
otherwise, I'll simply give Infra the heads up on our decision.

Note: cmpilato wants to bring along our old CVS history, too. He plans
to pop that through cvs2svn, so we'll have a couple batches of
revisions to load. Because the nearly 50k revisions will take a while,
Infra will be disabling commits during that import (so we don't get a
stray revision in the middle of our series). The hope is we can
translate svn.collab.net revisions to ASF revs with a simple +840000
or somesuch.

Cheers,
-g

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415813

Re: [RFC] source repository at Apache

Posted by Mark Phippard <ma...@gmail.com>.
On Fri, Nov 13, 2009 at 6:25 AM, Fabien Coelho <fa...@coelho.net> wrote:

> Scalability in the future, is indeed one of my concerns, although not my
> problem : I should not care, but I cannot help it... The ASF repository is
> over 800K commits, going at about 100K commits-per-year and accelerating.
> That may be fun, it is good to be scalable, it is very good for subversion
> to have such a large test bed, but I cannot see that as easily manageable
> in 10/20/30 years, especially if more projects are added to the
> repository.

This is a separate conversation.  I agree with you, BTW, that all
Apache projects should have their own repository.  That said,
currently they do not.  My point is that I think we should be handled
like all the other projects at ASF and no other project has their own
repository.  If the ASF later decides to give every project their own
repos, I'd be fine with that.


-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2417534

Re: [RFC] source repository at Apache

Posted by Fabien Coelho <fa...@coelho.net>.
> b) we'll actually deal day-to-day with a repository that's orders of 
> magnitude bigger than our own (death to scalability problems!)

There is no need for subversion to be in the big repos for the big repos 
to use the latest version or even trial ones. My idea of risk management 
would even suggest that it is better to separate them. If the big repos is 
broken by subversion (sure, this will never happen...), you cannot access 
the sources. It is also true of subversion in its own repos, but at least 
less projects are stopped because of that.

Scalability in the future, is indeed one of my concerns, although not my 
problem : I should not care, but I cannot help it... The ASF repository is 
over 800K commits, going at about 100K commits-per-year and accelerating. 
That may be fun, it is good to be scalable, it is very good for subversion 
to have such a large test bed, but I cannot see that as easily manageable 
in 10/20/30 years, especially if more projects are added to the 
repository.

As a developer, I understood that the commits are stopped when a new 
projects is imported : I do not think that this is a useful downtime for 
any project, even if it is quite short (possibly less than 15 mn ?), as it 
could be totally avoided.

Well, it was just my final 0.02 EUR, as I have not convince anyone to 
avoid the repository merges.

-- 
Fabien.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2417512

Re: [RFC] source repository at Apache

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Branko Cibej wrote on Wed, 11 Nov 2009 at 20:23 +0100:
> Ha. So, from a strictly CM-academic point of view, certainly, we should
> keep our history intact during transfer -- and that includes keeping
> revision numbers and implies not grandfathering in the CVS repository.
> 
> I'm leaning the other way because a) we'll get a *lot* more serious
> testing of release candidates; b) we'll actually deal day-to-day with a
> repository that's orders of magnitude bigger than our own (death to
> scalability problems!) and c) it will give /us/ a bit of incentive to be
> extra careful checking the quality of release candidates.
> 

I don't think (a) and (c) are related to whether we're in the Mother
repos or in our own repos; after all, presumably we can run release
candidates on Mother even if we're not in it ourselves.  (We should
upgrade our own repository before upgrading Mother, of course :))

> Sometimes you just have to be pragmatic and break the world for everyone
> so that you can build a better one. ;)
> 

:-)

> -- Brane
> 
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416707
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416880

Re: [RFC] source repository at Apache

Posted by Branko Cibej <br...@xbc.nu>.
Fabien COELHO wrote:
>
>>> (2) I use this ASF repository as an example of what should not be done
>>> with svn when I teach svn:-) I advocate that pretty independent
>>> projects
>>> should be in independant repositories, and connections can be
>>> implemented
>>> with svn:externals quite simply.
>>
>> Heh. Well, I teach people to avoid svn:externals like the plague. :)
>
> Differing opinions, good:-)
>
> I did not have much trouble with externals up to now, and I use them a
> lot. The only issue is that if we want to do a global tag or branch on
> related projects, the references must be updated accordingly, so we
> scripted it.
>
> So, everybody wants a very big repository with hundred of unrelated
> projects put together and dead references everywhere in the source and
> outside... and the strangeness of this very discontinuous choice does
> not strike anyone but me. Well...

Ha. So, from a strictly CM-academic point of view, certainly, we should
keep our history intact during transfer -- and that includes keeping
revision numbers and implies not grandfathering in the CVS repository.

I'm leaning the other way because a) we'll get a *lot* more serious
testing of release candidates; b) we'll actually deal day-to-day with a
repository that's orders of magnitude bigger than our own (death to
scalability problems!) and c) it will give /us/ a bit of incentive to be
extra careful checking the quality of release candidates.

Sometimes you just have to be pragmatic and break the world for everyone
so that you can build a better one. ;)

-- Brane

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416707

Re: [RFC] source repository at Apache

Posted by Fabien COELHO <fa...@ensmp.fr>.
>> (2) I use this ASF repository as an example of what should not be done
>> with svn when I teach svn:-) I advocate that pretty independent projects
>> should be in independant repositories, and connections can be implemented
>> with svn:externals quite simply.
>
> Heh. Well, I teach people to avoid svn:externals like the plague. :)

Differing opinions, good:-)

I did not have much trouble with externals up to now, and I use them a 
lot. The only issue is that if we want to do a global tag or branch on 
related projects, the references must be updated accordingly, so we 
scripted it.

So, everybody wants a very big repository with hundred of unrelated 
projects put together and dead references everywhere in the source and 
outside... and the strangeness of this very discontinuous choice does not 
strike anyone but me. Well...

-- 
Fabien.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416642

Re: [RFC] source repository at Apache

Posted by Branko Cibej <br...@xbc.nu>.
Fabien Coelho wrote:
> (2) I use this ASF repository as an example of what should not be done 
> with svn when I teach svn:-) I advocate that pretty independent projects 
> should be in independant repositories, and connections can be implemented 
> with svn:externals quite simply.
>   

Heh. Well, I teach people to avoid svn:externals like the plague. :)

-- Brane

P.S.: Yes, yes, I'll get around to implementing repos-side aliases one
day, I just have this ever growing stack of previous commitments to wade
through first ...

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416547

Re: [RFC] source repository at Apache

Posted by "Hyrum K. Wright" <hy...@hyrumwright.org>.
On Nov 11, 2009, at 12:21 PM, Fabien Coelho wrote:

>> To be clear, ASF infra is very content with one big repository - there
>> certainly isn't any desire to split it up on infra's end.  Frankly,
>> adding repositories would be more work.  -- justin
> 
> That's a indeed a clear statement from your end.
> 
> I guess that you have looked for usernames issues between the two 
> repositories, that is name clashes for distinct people, or the same person 
> with a different id?

We checked this at SubConf, and there are no known clashes.

-Hyrum

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416682

Re: [RFC] source repository at Apache

Posted by Fabien Coelho <fa...@coelho.net>.
> To be clear, ASF infra is very content with one big repository - there
> certainly isn't any desire to split it up on infra's end.  Frankly,
> adding repositories would be more work.  -- justin

That's a indeed a clear statement from your end.

I guess that you have looked for usernames issues between the two 
repositories, that is name clashes for distinct people, or the same person 
with a different id?

-- 
Fabien.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416676

Re: [RFC] source repository at Apache

Posted by Justin Erenkrantz <je...@apache.org>.
On Wed, Nov 11, 2009 at 4:13 PM, C. Michael Pilato <cm...@collab.net> wrote:
> In short, we don't care, because we aren't the system administrators.  If
> the ASF Infrastructure team says, "We prefer X and are willing to do all the
> work necessary to support X", who are we -- who aren't bearing the burden of
> administration -- to make a fuss?

To be clear, ASF infra is very content with one big repository - there
certainly isn't any desire to split it up on infra's end.  Frankly,
adding repositories would be more work.  -- justin

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416659

Re: [RFC] source repository at Apache

Posted by Fabien Coelho <fa...@coelho.net>.
>> (1) This means breaking all current revision numbers.
>
> That's true.  But the mapping should be a simple offset, since ASF Infra
> will be locking down the repository from outside commits while the load
> happens.  Over time, if we care, we can update old revision logs to point to
> the new revision numbers.

Including outside references in Forums and everywhere.

> svn:externals are just awful.  Terrible design, flawed implementation.

I do not have an opinion about the implementation, I just find it useful 
and efficient for what I do with it, and I'm clearly more on the small 
granularity side.

>> (3) very big repositories add a large burden to system administration,
>
> In short, we don't care, because we aren't the system administrators.

I do hope that subversion devs do care about system administrators when 
they design something.

> If the ASF Infrastructure team says, "We prefer X and are willing to do 
> all the work necessary to support X", who are we -- who aren't bearing 
> the burden of administration -- to make a fuss?

I thought that the preference was rather marginal on their side, and it 
was really a project choice, and I do see that move as a big and 
unnecessary disruption. But evidently I'm alone of that opinion.

>> I would prefer that. No disruption, just a switch/relocate.
>
> You wouldn't be able to just switch/relocate anyway, because we're prefixing
> our Subversion history with the converted CVS history.

Hmmm... you do not have to. If you do so that would indeed mess everything 
in any case, but that's a choice.

-- 
Fabien.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416645

Re: [RFC] source repository at Apache

Posted by Stefan Sperling <st...@elego.de>.
On Wed, Nov 11, 2009 at 08:00:56PM +0100, Fabien Coelho wrote:
> Dear Stefan,
> 
> > So? It's all recorded in history, if necessary in read-only clones
> > of the old repository.
> 
> The history, the file contents, the paths, the bug reports, the archived 
> mails, all refer to this history. If you recreate a new history, it is 
> still a history, but all these reference are dead or have to be fixed, so 
> it is much less useful to have them.

Why are they dead? They simply refer to the original line of
history of Subversion at svn.tigris.org.

> > There's projects that migrate to different version control tools,
> > and when they do this, they hit the same class of problems as you
> > are pointing out, just worse.
> 
> Sure, it could be much worse. I do not see that as a good argument to 
> accept a pain that could be fully avoided.

Sure, it's not a good argument for moving into the ASF mother
repository, but it's not meant to be. Good arguments have already been
stated by others. I just meant to put things into perspective.

> A migration is being planned, which could limit its effect to moving the 
> repos from one server to another, and as we're not changing the tool it 
> could be pretty painless.
> 
> Instead of that, it is going to be a full renumbering, possibly some 
> renaming, and breaking every reference inside and outside of the project, 
> for an added value which is still eluding me.

The arguments for moving into the mother repo have been stated,
so I'm not gonna repeat them here. But I seem to observe that people
who favour moving into the mother repo show a tendency of evaluating
the arguments by looking forward into the future and see the benefits
the mother repo will bring, while you seem to be more focused on preserving
the past. Both approaches are valid, just different points of view.

> Note that you do not have to convince me, I'm just a partial citizen.

For the record, I am simply gonna go with whatever people decide upon.
I'm not gonna argue about mother-repo or not. I'm simply not bothered
enough to care because I know I won't have to do any of the hard work :-P
So I don't want to convince you or anyone else one way or another.

The move to the ASF is happening and many people have been waiting for
it to happen for many years. Any inconveniences we are now facing due
to the move could have been overcome years ago, but it took the community
a long time to get to the point of being able to announce "we're moving
to the ASF _now_". If that had happened years ago, nobody would care today
about little inconveniences such as revision number changes people had to
endure during the migration. So the migration will happen, and it will
cause some temporary disruption, but life will go on.

Stefan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416712

Re: [RFC] source repository at Apache

Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Nov 11, 2009 at 2:39 PM, Fabien COELHO <fa...@ensmp.fr> wrote:
>>> Instead of that, it is going to be a full renumbering, possibly some
>>> renaming, and breaking every reference inside and outside of the project,
>>> for an added value which is still eluding me.
>>
>> The way I see it is yes, it will be a pain, but it is good for us to
>> experience at least the amount of pain that we expect many of our users
>> will (~have to) experience in their real use of Subversion. The idea (to
>> me) is that this will encourage us to make Subversion better at handling
>> this sort of real-life change, and become less blasé about telling users
>> that they can and should just cope with this sort of change without
>> better support from us.
>
> With such a sadistic/masochist argument (it is both of them), we could
> also revert to CVS or copying files around just for the sake of knowing
> that a tool helps a little...
>
> I have done rcs to svn conversions in the past, I have merged distinct svn
> repositories, I already know it may be painful, I also know I have to help
> for that, I assure you I am not at all blasé about it, and you really do
> not need to remind me these issues by breaking the consistency of the
> subversion repository:-)

For me, it comes down to that I do not want our project to be treated
"special".  No other project that joins the ASF is given the option of
having their own repository, so neither should we.  Not only would it
be bad community etiquette on our part to ask for it, it would set a
bad precedent for the future.  What if some other big project wants to
move to Apache but would only do so if they can use Mercurial or some
other version control tool?

If the ASF infrastructure team had told us they would prefer to have
us live in our own repository so that they could isolate our usage of
release candidates, then I would be OK with that.  But given that they
are willing to run the release candidates on the main repository, I
believe we should be treated like all other ASF projects.

I also believe that if we are treated as a special case, it opens up
the door for problems in the future.  Maybe someone forgets to back up
our repository or does not know the special way to handle it.  Maybe
we do not get the geographic mirrors for our repository etc.

The pain we will experience from having to do this will hopefully be
offset by being able to recognize improvements we can make to
Subversion to better support this kind of repository setup.

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416745

Re: [RFC] source repository at Apache

Posted by Fabien COELHO <fa...@ensmp.fr>.
>> Instead of that, it is going to be a full renumbering, possibly some
>> renaming, and breaking every reference inside and outside of the project,
>> for an added value which is still eluding me.
>
> The way I see it is yes, it will be a pain, but it is good for us to
> experience at least the amount of pain that we expect many of our users
> will (~have to) experience in their real use of Subversion. The idea (to
> me) is that this will encourage us to make Subversion better at handling
> this sort of real-life change, and become less blasé about telling users
> that they can and should just cope with this sort of change without
> better support from us.

With such a sadistic/masochist argument (it is both of them), we could 
also revert to CVS or copying files around just for the sake of knowing 
that a tool helps a little...

I have done rcs to svn conversions in the past, I have merged distinct svn 
repositories, I already know it may be painful, I also know I have to help 
for that, I assure you I am not at all blasé about it, and you really do 
not need to remind me these issues by breaking the consistency of the 
subversion repository:-)

-- 
Fabien.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416715

Re: [RFC] source repository at Apache

Posted by Julian Foad <ju...@btopenworld.com>.
Fabien Coelho wrote:
> A migration is being planned, which could limit its effect to moving the 
> repos from one server to another, and as we're not changing the tool it 
> could be pretty painless.
> 
> Instead of that, it is going to be a full renumbering, possibly some 
> renaming, and breaking every reference inside and outside of the project, 
> for an added value which is still eluding me.

The way I see it is yes, it will be a pain, but it is good for us to
experience at least the amount of pain that we expect many of our users
will (~have to) experience in their real use of Subversion. The idea (to
me) is that this will encourage us to make Subversion better at handling
this sort of real-life change, and become less blasé about telling users
that they can and should just cope with this sort of change without
better support from us.

For example, after we did a mass white-space change throughout our
repository a few years ago, we fairly swiftly implemented a "svn blame"
option to ignore whitespace changes.

- Julian

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416706

Re: [RFC] source repository at Apache

Posted by Fabien Coelho <fa...@coelho.net>.
Dear Stefan,

> So? It's all recorded in history, if necessary in read-only clones
> of the old repository.

The history, the file contents, the paths, the bug reports, the archived 
mails, all refer to this history. If you recreate a new history, it is 
still a history, but all these reference are dead or have to be fixed, so 
it is much less useful to have them.

> There's projects that migrate to different version control tools,
> and when they do this, they hit the same class of problems as you
> are pointing out, just worse.

Sure, it could be much worse. I do not see that as a good argument to 
accept a pain that could be fully avoided.

A migration is being planned, which could limit its effect to moving the 
repos from one server to another, and as we're not changing the tool it 
could be pretty painless.

Instead of that, it is going to be a full renumbering, possibly some 
renaming, and breaking every reference inside and outside of the project, 
for an added value which is still eluding me.

Note that you do not have to convince me, I'm just a partial citizen.

-- 
Fabien.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416698

Re: [RFC] source repository at Apache

Posted by Karl Fogel <kf...@red-bean.com>.
Branko Cibej <br...@xbc.nu> writes:
> Karl Fogel wrote:
>> Many of these references can be fixed up.  We are going to be adding an
>> offset (i.e., if Subversion is imported when the ASF repository is
>> already at rev N, then just add N to every rev reference).  So in our
>> log messages and bug comments, we can probably fix this up in a mostly
>> automated way.  I know we can for the log messages; I assume that for
>> the bug exports we can too.
>>
>> There will still be references out there that are wrong, but at least
>> the fix will always be clear: add N and you've got the new revnum.
>
> Plus -- and this is the only reason the above argument can hold water --
> there can't be any overlap between our current and our future revision
> numbers, because the ASF repository already has an order of magniture
> more revisions in it than we do.

This is a very good point, although it is certainly not the only reason
the argument holds water :-).

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416810

Re: [RFC] source repository at Apache

Posted by Branko Cibej <br...@xbc.nu>.
Karl Fogel wrote:
> Stefan Sperling <st...@elego.de> writes:
>   
>>> BTW, I just noticed that they also appear in branch names, say
>>> "branches/1.6.x-r40452".
>>>       
>> So? It's all recorded in history, if necessary in read-only clones
>> of the old repository.
>>
>> There's projects that migrate to different version control tools,
>> and when they do this, they hit the same class of problems as you
>> are pointing out, just worse.
>>     
>
> Many of these references can be fixed up.  We are going to be adding an
> offset (i.e., if Subversion is imported when the ASF repository is
> already at rev N, then just add N to every rev reference).  So in our
> log messages and bug comments, we can probably fix this up in a mostly
> automated way.  I know we can for the log messages; I assume that for
> the bug exports we can too.
>
> There will still be references out there that are wrong, but at least
> the fix will always be clear: add N and you've got the new revnum.
>   

Plus -- and this is the only reason the above argument can hold water --
there can't be any overlap between our current and our future revision
numbers, because the ASF repository already has an order of magniture
more revisions in it than we do.

-- Brane

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416709

Re: [RFC] source repository at Apache

Posted by Karl Fogel <kf...@red-bean.com>.
Stefan Sperling <st...@elego.de> writes:
>> BTW, I just noticed that they also appear in branch names, say
>> "branches/1.6.x-r40452".
>
> So? It's all recorded in history, if necessary in read-only clones
> of the old repository.
>
> There's projects that migrate to different version control tools,
> and when they do this, they hit the same class of problems as you
> are pointing out, just worse.

Many of these references can be fixed up.  We are going to be adding an
offset (i.e., if Subversion is imported when the ASF repository is
already at rev N, then just add N to every rev reference).  So in our
log messages and bug comments, we can probably fix this up in a mostly
automated way.  I know we can for the log messages; I assume that for
the bug exports we can too.

There will still be references out there that are wrong, but at least
the fix will always be clear: add N and you've got the new revnum.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416705

Re: [RFC] source repository at Apache

Posted by Stefan Sperling <st...@elego.de>.
On Wed, Nov 11, 2009 at 06:19:56PM +0100, Fabien Coelho wrote:
> >> (1) This means breaking all current revision numbers.
> >
> > That's true.  But the mapping should be a simple offset, since ASF Infra
> > will be locking down the repository from outside commits while the load
> > happens.  Over time, if we care, we can update old revision logs to point to
> > the new revision numbers.
> 
> BTW, I just noticed that they also appear in branch names, say
> "branches/1.6.x-r40452".

So? It's all recorded in history, if necessary in read-only clones
of the old repository.

There's projects that migrate to different version control tools,
and when they do this, they hit the same class of problems as you
are pointing out, just worse.

Stefan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416681

Re: [RFC] source repository at Apache

Posted by Fabien Coelho <fa...@coelho.net>.
>> (1) This means breaking all current revision numbers.
>
> That's true.  But the mapping should be a simple offset, since ASF Infra
> will be locking down the repository from outside commits while the load
> happens.  Over time, if we care, we can update old revision logs to point to
> the new revision numbers.

BTW, I just noticed that they also appear in branch names, say
"branches/1.6.x-r40452".

-- 
Fabien.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416649

Re: [RFC] source repository at Apache

Posted by "C. Michael Pilato" <cm...@collab.net>.
Fabien Coelho wrote:
> I do not think I have a vote, but I have an opinion:-)
> 
>> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
>> is the "big mother" repository with all ASF projects and 834k
>> revisions in it
> 
> I think that it is a bad idea.
> 
> (1) This means breaking all current revision numbers.

That's true.  But the mapping should be a simple offset, since ASF Infra
will be locking down the repository from outside commits while the load
happens.  Over time, if we care, we can update old revision logs to point to
the new revision numbers.

> (2) I use this ASF repository as an example of what should not be done 
> with svn when I teach svn:-) I advocate that pretty independent projects 
> should be in independant repositories, and connections can be implemented 
> with svn:externals quite simply.

svn:externals are just awful.  Terrible design, flawed implementation.  A
band-aid over the gaping hole in functionality known as "cvs modules" that
unfortunately fails to stop the bleeding.

> (3) very big repositories add a large burden to system administration, 

In short, we don't care, because we aren't the system administrators.  If
the ASF Infrastructure team says, "We prefer X and are willing to do all the
work necessary to support X", who are we -- who aren't bearing the burden of
administration -- to make a fuss?

>> 2) svn.apache.org/repos/$VAR -- our own repository, potentially
>> running a custom server
> 
> I would prefer that. No disruption, just a switch/relocate.

You wouldn't be able to just switch/relocate anyway, because we're prefixing
our Subversion history with the converted CVS history.

-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416606

Re: [RFC] source repository at Apache

Posted by Fabien Coelho <fa...@coelho.net>.
I do not think I have a vote, but I have an opinion:-)

> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
> is the "big mother" repository with all ASF projects and 834k
> revisions in it

I think that it is a bad idea.

(1) This means breaking all current revision numbers.

All comments in the logs and some files (say CHANGES) will point to 
nowhere, or have to be changed, and there are some ugly syntaxes (eg 
r6382-6). All outside references to revision numbers would also be dead.

Maybe it would make sense to have the apache svn modules in that 
repository, but it does not make much sense for the whole project.

The initial revision number can be kept as a revision property, but that 
does not help much, one would have to search to find it.

(2) I use this ASF repository as an example of what should not be done 
with svn when I teach svn:-) I advocate that pretty independent projects 
should be in independant repositories, and connections can be implemented 
with svn:externals quite simply.

(3) very big repositories add a large burden to system administration, 
e.g. if you want to dump/reload or the like it would take ages of 
disruption. Moreover, the ASF repository uses subversion, subversion uses 
subversion. From a  system admin perspective, I'm not sure that I would 
like to change the tool for the big repository as often I could test it 
on a smaller one. I would have a different policy to maintain them.
If some new feature requires a dump/load some day, the main asf repository 
will have to schedule some down time to enable it, while it could be 
very quickly handled on a smaller repos.

> 2) svn.apache.org/repos/$VAR -- our own repository, potentially
> running a custom server

I would prefer that. No disruption, just a switch/relocate.

-- 
Fabien.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416456

Re: [RFC] source repository at Apache

Posted by Greg Stein <gs...@gmail.com>.
On Mon, Nov 9, 2009 at 11:08, Larry Shatzer, Jr. <fu...@zyx.net> wrote:
> On Mon, Nov 9, 2009 at 8:58 AM, C. Michael Pilato <cm...@collab.net> wrote:
>> Mark Phippard wrote:
>>> On Mon, Nov 9, 2009 at 10:46 AM, Greg Stein <gs...@gmail.com> wrote:
>>>
>>>> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
>>>> is the "big mother" repository with all ASF projects and 834k
>>>> revisions in it
>>>
>>> I think this is the best option overall, with this probably being the
>>> main reason:
>>>
>>>> * standard procedures for Infra. we'll never be forgotten
>>
>> What he said.
>>
>>> That said, having our code in this large shared repository might also
>>> cause us to learn something new about using Subversion that drives new
>>> feature ideas in the future.
>>>
>>> For example, when our repository is loaded into the ASF repository
>>> will all of the contents of our svn:mergeinfo properties become
>>> magically rewritten to the new paths and revisions?
>>
>> I believe so.  Issue #2983 tracked this behavior.
>>
>
> As an outsider watching this with some interest, I hope this also
> might provoke someone to solve
> http://www.apache.org/dev/version-control.html#date-revisions (Issue
> 752). I've seen this at my last job, and current job, due to either
> merging a bunch of repositories into one, or importing various CVS
> repositories into an existing Subversion repository.

Unfortunately, I suspect that it won't. The Subversion devs have a
large crossover with Apache, so we've been very well aware of it ever
since the Apache repository was constructed. And still... nobody has
been motivated to tackle it :-(

And I guess you can blame that on me. I advocated for the mother repos
at the ASF. Suckers bought into it. ;-)

Cheers,
-g

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415834

Re: [RFC] source repository at Apache

Posted by Larry Shatzer <fu...@zyx.net>.
On Mon, Nov 9, 2009 at 8:58 AM, C. Michael Pilato <cm...@collab.net> wrote:
> Mark Phippard wrote:
>> On Mon, Nov 9, 2009 at 10:46 AM, Greg Stein <gs...@gmail.com> wrote:
>>
>>> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
>>> is the "big mother" repository with all ASF projects and 834k
>>> revisions in it
>>
>> I think this is the best option overall, with this probably being the
>> main reason:
>>
>>> * standard procedures for Infra. we'll never be forgotten
>
> What he said.
>
>> That said, having our code in this large shared repository might also
>> cause us to learn something new about using Subversion that drives new
>> feature ideas in the future.
>>
>> For example, when our repository is loaded into the ASF repository
>> will all of the contents of our svn:mergeinfo properties become
>> magically rewritten to the new paths and revisions?
>
> I believe so.  Issue #2983 tracked this behavior.
>

As an outsider watching this with some interest, I hope this also
might provoke someone to solve
http://www.apache.org/dev/version-control.html#date-revisions (Issue
752). I've seen this at my last job, and current job, due to either
merging a bunch of repositories into one, or importing various CVS
repositories into an existing Subversion repository.

-- Larry

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415830

Re: [RFC] source repository at Apache

Posted by Mark Phippard <ma...@gmail.com>.
On Mon, Nov 9, 2009 at 2:03 PM, Greg Stein <gs...@gmail.com> wrote:
> On Mon, Nov 9, 2009 at 13:55, Mark Phippard <ma...@gmail.com> wrote:
>> On Mon, Nov 9, 2009 at 12:05 PM, Paul Burba <pt...@gmail.com> wrote:
>>
>>> Confirming this is indeed handled, see also issue #3020, which
>>> concerns revision rewriting,
>>> http://subversion.tigris.org/issues/show_bug.cgi?id=3020.
>>
>> I dumped/loaded a mirror of our repository into another repository and
>> can confirm this was all handled OK.  I even loaded it into a new
>> folder named "subversion".
>>
>> I tested that things like log/blame -g work properly.
>
> Cool.
>
> To clarify/expand... Projects at the ASF load their code into:
>
> /PROJNAME/SUBPROJ/{trunk,tags,branches}
>
> If there is no subproject, then that portion is elided (as we will).
> In this case, PROJNAME corresponds to the Top Level Project name,
> which will be "subversion" for us.

Right, in my example after loading I had paths like:

/subversion/trunk
/subversion/branches/1.6.x

etc...

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415876

Re: [RFC] source repository at Apache

Posted by Branko Cibej <br...@xbc.nu>.
Blair Zajac wrote:
> Peter Samuelson wrote:
>   
>> [Greg Stein]
>>     
>>> To clarify/expand... Projects at the ASF load their code into:
>>>
>>> /PROJNAME/SUBPROJ/{trunk,tags,branches}
>>>
>>> If there is no subproject, then that portion is elided (as we will).
>>> In this case, PROJNAME corresponds to the Top Level Project name,
>>> which will be "subversion" for us.
>>>       
>> This is almost OT, but given that we will be going to the trouble to
>> dump / reload the repository and re-check-out all our working copies,
>> can someone remind me why we have a 'branches' directory?  Is it just
>> to preserve the ability to name a branch 'trunk' or 'tags'?  In all
>> these years I've never figured out why conventional wisdom says that
>> all branches except trunk need a separate subdir.
>>
>> (Especially if ^/branches/1.6.x becomes ^/subversion/branches/1.6.x,
>> it would be nice to shorten that and save some typing.)
>>     
>
> Are you suggesting the branches are siblings of the trunk then?  If so, then why 
> not have the tags at the same level then?  That would get messy then and you 
> couldn't tell a branch from a tag then.
>   

Actually, since you ask -- yes, branches should be siblings of trunk;
but in their own directory. Our proposed trunk/ branches/ tags/ is
broken IMHO because it makes trunk somehow special (it's not), makes
relative symbolic links to come common tree not work on branches and
tags, etc. etc. For projects I work on, I've long proposed a simpler
structure with just branches/ and tags/, and mainline development
happening on, e.g., branches/mainline.

But I strongly disagree with the idea of historically (more like
hysterically) renaming all our branches or anything else in the
repository in any way. A fine example we'd make for everyone if we went
changing our history! And we'd quickly go insane, too.

-- Brane

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415967

Re: [RFC] source repository at Apache

Posted by Peter Samuelson <pe...@p12n.org>.
[Blair Zajac]
> Are you suggesting the branches are siblings of the trunk then?

Yes.  Or, more to the point, trunk is not special, it is just another
branch.  But moving trunk into 'branches' will involve more typing for
everyone than just moving the other branches out of it.

> If so, then why not have the tags at the same level then?  That
> would get messy then and you couldn't tell a branch from a tag then.

You answered your own question.  The reason not to have tags at the
same level is that it would get messy then and you couldn't tell a
branch from a tag then.

I don't think having one special subdir 'tags' is any more confusing,
or less consistent, than having two special subdirs 'tags' and
'branches', the latter containing all branches except one.
-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415958

Re: [RFC] source repository at Apache

Posted by Blair Zajac <bl...@orcaware.com>.
Peter Samuelson wrote:
> [Greg Stein]
>> To clarify/expand... Projects at the ASF load their code into:
>>
>> /PROJNAME/SUBPROJ/{trunk,tags,branches}
>>
>> If there is no subproject, then that portion is elided (as we will).
>> In this case, PROJNAME corresponds to the Top Level Project name,
>> which will be "subversion" for us.
> 
> This is almost OT, but given that we will be going to the trouble to
> dump / reload the repository and re-check-out all our working copies,
> can someone remind me why we have a 'branches' directory?  Is it just
> to preserve the ability to name a branch 'trunk' or 'tags'?  In all
> these years I've never figured out why conventional wisdom says that
> all branches except trunk need a separate subdir.
> 
> (Especially if ^/branches/1.6.x becomes ^/subversion/branches/1.6.x,
> it would be nice to shorten that and save some typing.)

Are you suggesting the branches are siblings of the trunk then?  If so, then why 
not have the tags at the same level then?  That would get messy then and you 
couldn't tell a branch from a tag then.

Blair

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415956

Re: [RFC] source repository at Apache

Posted by Mark Phippard <ma...@gmail.com>.
On Mon, Nov 9, 2009 at 6:02 PM, Peter Samuelson <pe...@p12n.org> wrote:
> [Greg Stein]
>> To clarify/expand... Projects at the ASF load their code into:
>>
>> /PROJNAME/SUBPROJ/{trunk,tags,branches}
>>
>> If there is no subproject, then that portion is elided (as we will).
>> In this case, PROJNAME corresponds to the Top Level Project name,
>> which will be "subversion" for us.
>
> This is almost OT, but given that we will be going to the trouble to
> dump / reload the repository and re-check-out all our working copies,
> can someone remind me why we have a 'branches' directory?  Is it just
> to preserve the ability to name a branch 'trunk' or 'tags'?  In all
> these years I've never figured out why conventional wisdom says that
> all branches except trunk need a separate subdir.
>
> (Especially if ^/branches/1.6.x becomes ^/subversion/branches/1.6.x,
> it would be nice to shorten that and save some typing.)

I'd say it is basically a form of sharding for people browsing the
repository.  In terms of the extra typing, I think that is an example
of why being in the Apache repository will be good for us.  Maybe it
will motivate someone to come up with a new feature so that you can
type less than that.

That said, given how long we lived with typing the full URL I doubt it.

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415960

Re: [RFC] source repository at Apache

Posted by Peter Samuelson <pe...@p12n.org>.
[Greg Stein]
> To clarify/expand... Projects at the ASF load their code into:
> 
> /PROJNAME/SUBPROJ/{trunk,tags,branches}
> 
> If there is no subproject, then that portion is elided (as we will).
> In this case, PROJNAME corresponds to the Top Level Project name,
> which will be "subversion" for us.

This is almost OT, but given that we will be going to the trouble to
dump / reload the repository and re-check-out all our working copies,
can someone remind me why we have a 'branches' directory?  Is it just
to preserve the ability to name a branch 'trunk' or 'tags'?  In all
these years I've never figured out why conventional wisdom says that
all branches except trunk need a separate subdir.

(Especially if ^/branches/1.6.x becomes ^/subversion/branches/1.6.x,
it would be nice to shorten that and save some typing.)

Peter

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415948

Re: [RFC] source repository at Apache

Posted by Greg Stein <gs...@gmail.com>.
On Mon, Nov 9, 2009 at 13:55, Mark Phippard <ma...@gmail.com> wrote:
> On Mon, Nov 9, 2009 at 12:05 PM, Paul Burba <pt...@gmail.com> wrote:
>
>> Confirming this is indeed handled, see also issue #3020, which
>> concerns revision rewriting,
>> http://subversion.tigris.org/issues/show_bug.cgi?id=3020.
>
> I dumped/loaded a mirror of our repository into another repository and
> can confirm this was all handled OK.  I even loaded it into a new
> folder named "subversion".
>
> I tested that things like log/blame -g work properly.

Cool.

To clarify/expand... Projects at the ASF load their code into:

/PROJNAME/SUBPROJ/{trunk,tags,branches}

If there is no subproject, then that portion is elided (as we will).
In this case, PROJNAME corresponds to the Top Level Project name,
which will be "subversion" for us.

Our svn-org repos will go away, and/or portions into the ASF's
"private" repository (every PMC can have a private area for recording
stuff). Our security repository will get moved into the ASF-wide
security management (I'm unclear on this part).

Cheers,
-g

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415875

Re: [RFC] source repository at Apache

Posted by Mark Phippard <ma...@gmail.com>.
On Mon, Nov 9, 2009 at 12:05 PM, Paul Burba <pt...@gmail.com> wrote:

> Confirming this is indeed handled, see also issue #3020, which
> concerns revision rewriting,
> http://subversion.tigris.org/issues/show_bug.cgi?id=3020.

I dumped/loaded a mirror of our repository into another repository and
can confirm this was all handled OK.  I even loaded it into a new
folder named "subversion".

I tested that things like log/blame -g work properly.

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415872

Re: [RFC] source repository at Apache

Posted by Paul Burba <pt...@gmail.com>.
On Mon, Nov 9, 2009 at 10:58 AM, C. Michael Pilato <cm...@collab.net> wrote:
> Mark Phippard wrote:
>> On Mon, Nov 9, 2009 at 10:46 AM, Greg Stein <gs...@gmail.com> wrote:
>>
>>> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
>>> is the "big mother" repository with all ASF projects and 834k
>>> revisions in it
>>
>> I think this is the best option overall, with this probably being the
>> main reason:
>>
>>> * standard procedures for Infra. we'll never be forgotten
>
> What he said.
>
>> That said, having our code in this large shared repository might also
>> cause us to learn something new about using Subversion that drives new
>> feature ideas in the future.
>>
>> For example, when our repository is loaded into the ASF repository
>> will all of the contents of our svn:mergeinfo properties become
>> magically rewritten to the new paths and revisions?
>
> I believe so.  Issue #2983 tracked this behavior.

Confirming this is indeed handled, see also issue #3020, which
concerns revision rewriting,
http://subversion.tigris.org/issues/show_bug.cgi?id=3020.

Paul

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415846

Re: [RFC] source repository at Apache

Posted by "C. Michael Pilato" <cm...@collab.net>.
Mark Phippard wrote:
> On Mon, Nov 9, 2009 at 10:46 AM, Greg Stein <gs...@gmail.com> wrote:
> 
>> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
>> is the "big mother" repository with all ASF projects and 834k
>> revisions in it
> 
> I think this is the best option overall, with this probably being the
> main reason:
> 
>> * standard procedures for Infra. we'll never be forgotten

What he said.

> That said, having our code in this large shared repository might also
> cause us to learn something new about using Subversion that drives new
> feature ideas in the future.
> 
> For example, when our repository is loaded into the ASF repository
> will all of the contents of our svn:mergeinfo properties become
> magically rewritten to the new paths and revisions?

I believe so.  Issue #2983 tracked this behavior.

-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415823

Re: [RFC] source repository at Apache

Posted by Mark Phippard <ma...@gmail.com>.
On Mon, Nov 9, 2009 at 10:46 AM, Greg Stein <gs...@gmail.com> wrote:

> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
> is the "big mother" repository with all ASF projects and 834k
> revisions in it

I think this is the best option overall, with this probably being the
main reason:

> * standard procedures for Infra. we'll never be forgotten

That said, having our code in this large shared repository might also
cause us to learn something new about using Subversion that drives new
feature ideas in the future.

For example, when our repository is loaded into the ASF repository
will all of the contents of our svn:mergeinfo properties become
magically rewritten to the new paths and revisions?

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415820

Re: [RFC] source repository at Apache

Posted by Paul Burba <pt...@gmail.com>.
On Mon, Nov 9, 2009 at 10:46 AM, Greg Stein <gs...@gmail.com> wrote:
> Hi all,
>
> This request-for-comment is about our svn repository on the ASF
> hardware. There are two primary options:
>
> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
> is the "big mother" repository with all ASF projects and 834k
> revisions in it
>
> 2) svn.apache.org/repos/$VAR -- our own repository, potentially
> running a custom server
>
>
> The ASF Infrastructure Team would mildly prefer (1), but would be fine
> if we want (2).
>
> There were several svn committers present at a meeting with Infra last
> Thursday to discuss these possibilities: cmpilato, dlr, gstein,
> jerenkrantz, jrepenning. The recommendation from those present is to
> go with the primary repository. This reco comes from a number of
> factors:
>
> * standard procedures for Infra. we'll never be forgotten
>
> * in one repository, we can shift code to/from other projects (e.g
> should our mod_* move to httpd?)
>
> * Infra is willing to run our release candidates on the main repos, so
> we don't need a special server for that. they're pretty much willing
> to run anything we ask for (alpha? beta?), but that obviously means we
> better be *damned* sure it won't lose or corrupt the repo :-)

This last bullet is compelling enough on it's own for me to favor option 1.

Paul

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416678

Re: [RFC] source repository at Apache

Posted by Branko Cibej <br...@xbc.nu>.
Greg Stein wrote:
> Hi all,
>
> This request-for-comment is about our svn repository on the ASF
> hardware. There are two primary options:
>
> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
> is the "big mother" repository with all ASF projects and 834k
> revisions in it
>   

+1 for Apache Big Mama. We'll still be able to eat our own dogfood, and
get more of it, too. Yum.

-- Brane

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415858

Re: [RFC] source repository at Apache

Posted by Senthil Kumaran S <se...@collab.net>.
Greg Stein wrote:
> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
> is the "big mother" repository with all ASF projects and 834k
> revisions in it

+1 for this.

-- 
Senthil Kumaran S
http://www.stylesen.org/

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416040

Re: [RFC] source repository at Apache

Posted by Justin Erenkrantz <je...@apache.org>.
On Tue, Nov 10, 2009 at 9:51 AM, Bert Huijben <rh...@sharpsvn.net> wrote:
> +1 on the main repository.. and "Hi" to
> svn.eu.apache.org/repos/asf/subversion/ :)

Yah, whenever you are on this side of the pond, having an EU mirror rocks.  =)

You shouldn't need to specify svn.eu as as we use geo-preference DNS -
so svn.a.o will resolve to the 'best' location.

I don't know how many Australians we have here, but ASF infra is
planning on deploying another SVN mirror in Australia in the next 3-6
months.  Depending upon routing, we may end up routing Asia traffic to
the Aussie mirror; not sure yet.  -- justin

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416088

RE: [RFC] source repository at Apache

Posted by Bert Huijben <rh...@sharpsvn.net>.
> -----Original Message-----
> From: Greg Stein [mailto:gstein@gmail.com]
> Sent: maandag 9 november 2009 16:46
> To: dev@subversion.tigris.org
> Subject: [RFC] source repository at Apache
> 
> Hi all,
> 
> This request-for-comment is about our svn repository on the ASF
> hardware. There are two primary options:
> 
> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
> is the "big mother" repository with all ASF projects and 834k
> revisions in it

+1 on the main repository.. and "Hi" to
svn.eu.apache.org/repos/asf/subversion/ :)

	Bert

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2416050

Re: [RFC] source repository at Apache

Posted by Arfrever Frehtes Taifersar Arahesis <Ar...@GMail.Com>.
2009-11-09 16:46:18 Greg Stein napisał(a):
> Hi all,
> 
> This request-for-comment is about our svn repository on the ASF
> hardware. There are two primary options:
> 
> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
> is the "big mother" repository with all ASF projects and 834k
> revisions in it

-0

> 2) svn.apache.org/repos/$VAR -- our own repository, potentially
> running a custom server

+1

-- 
Arfrever Frehtes Taifersar Arahesis

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2417422

Re: [RFC] source repository at Apache

Posted by Justin Erenkrantz <je...@apache.org>.
On Mon, Nov 9, 2009 at 4:46 PM, Greg Stein <gs...@gmail.com> wrote:
> 1) svn.apache.org/repos/asf/subversion/{trunks,tags,branches} -- this
> is the "big mother" repository with all ASF projects and 834k
> revisions in it

+1.  -- justin

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2415829