Re: SVN move

[Craig L Russell]

All the code being imported has the org.jsecurity package name, including the trunk, tags, and branches, I think it would be less confusing to put trunk, tags, and branches under a new top level directory called import.

Craig

On Jul 25, 2008, at 12:09 PM, Les Hazlewood wrote:

The new top level trunk, tags, and branches would then be where we migrate the imports/trunk to while changing package names (and licenses as required). It's not clear to me that we should have incubator/jsecurity/tags/0.90- beta2 in the Apache repo. I'd much prefer to see incubator/jsecurity/ import/tags/0.90-beta2. My thoughts on this process are (obviously) evolving. I just want to make it clear to anyone browsing the Apache repository that there is legacy code being imported and there is code that will become the Apache distribution. Just throwing out ideas to make it less opaque.

Actually I don't think that is possible - the existing repo already has

'trunk', 'branches' and 'tags' that need to be preserved in the same
location.


trunk after that point as desired.

Would that be acceptable?

To achieve what you're talking about, I was hoping we could just create an 'import' branch immediately after the migration and then start using the On Fri, Jul 25, 2008 at 2:49 PM, Craig L Russell <[EMAIL PROTECTED] >wrote:

Is it too late to suggest that the top level directory for the imported code be "import" and not "trunk"? Using the import directory would allow

development to continue (in import) and put all of the future Apache
deliverables into trunk.

Craig


On Jul 25, 2008, at 8:43 AM, Les Hazlewood wrote:

Ok, I'll let the infrastructure folks know they can blast away the

existing
one when performing the load.

Thanks,

Les

On Fri, Jul 25, 2008 at 11:04 AM, Alan D. Cabrera <[EMAIL PROTECTED]

wrote:

Crickey, you may be right.  It's simple enough to recreate those few

files.


Regards,
ALan


On Jul 25, 2008, at 7:58 AM, Les Hazlewood wrote:

I want to do it today or tomorrow.  Sunday at the latest for sure.

cause
a

done

if
this is possible?

On Fri, Jul 25, 2008 at 10:49 AM, Alan D. Cabrera <[EMAIL PROTECTED]

Just out of curiosity - I see the new SVN is being used. Won't that conflict for an svnadmin load of the migrated repo? I mean, I've never an svnadmin load on anything other than a fresh repository - anyone know

wrote:

Les, have you been able to make your SVN dump yet? When can we expect

this?


Regards,
Alan

Craig L Russell

Architect, Sun Java Enterprise System http://java.sun.com/products/ jdo

408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

smime.p7s
Description: S/MIME cryptographic signature