You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Jeff Machols <jm...@comcast.net> on 2003/11/24 19:09:42 UTC

Rethink Subversion

Guys,

I know we talked about this before, but I think we should think about
using subversion instead of CVS for the directory project.  The benefits
are becoming apparent now.  Right off the bat it will help with the
migration from source forge, plus the advantages of the Meta-data and
atomic check-ins.  I know there may be a small learning curve, but I
would rather do this now when we are changing infrastructure anyway,
than have to go through this in the future when we are worried more
important things: the releases, code, etc.  

So I am a +1 to use Subversion instead of CVS.

Jeff


Re: Rethink Subversion

Posted by Phil Steitz <ph...@steitz.com>.
Jeff Machols wrote:
> Guys,
> 
> I know we talked about this before, but I think we should think about
> using subversion instead of CVS for the directory project.  The benefits
> are becoming apparent now.  Right off the bat it will help with the
> migration from source forge, plus the advantages of the Meta-data and
> atomic check-ins.  I know there may be a small learning curve, but I
> would rather do this now when we are changing infrastructure anyway,
> than have to go through this in the future when we are worried more
> important things: the releases, code, etc.  
> 
> So I am a +1 to use Subversion instead of CVS.
> 
> Jeff
> 

I was "out" yesterday; but I will add my +1 this AM.

Always good to learn, always good to help the new stuff along :-)

Phil


Re: Rethink Subversion

Posted by Stephen McConnell <mc...@apache.org>.

Noel J. Bergman wrote:

>>+1 because I want to make Noel happy instead of
>>worrying about a Christmas card.
>>    
>>
>
>??  This wasn't my idea.  It was Alex's.  Came completely out of the blue
>this morning.
>

I know!
But it's low-budget Christmas gift all the same!
:-)

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org

|------------------------------------------------|
| Magic by Merlin                                |
| Production by Avalon                           |
|                                                |
| http://avalon.apache.org/merlin                |
| http://dpml.net/                               |
|------------------------------------------------|





RE: Rethink Subversion

Posted by "Noel J. Bergman" <no...@devtech.com>.
> +1 because I want to make Noel happy instead of
> worrying about a Christmas card.

??  This wasn't my idea.  It was Alex's.  Came completely out of the blue
this morning.

	--- Noel


RE: Rethink Subversion

Posted by Jeff Machols <jm...@comcast.net>.

> -----Original Message-----
> From: Stephen McConnell [mailto:mcconnell@apache.org]
> Sent: Monday, November 24, 2003 7:14 PM
> To: Apache Directory Developers List
> Subject: Re: Rethink Subversion
> 
> 
> +1 because I want to make Noel happy instead of
> worrying about a Christmas card.
> 
> :-)
> 
> (I the meantime I hope there is a way cool
> Windows desktop tool for this)
> 


Haven't tried it yet:
http://tortoisesvn.tigris.org/


> 
> Jeff Machols wrote:
> 
> >Guys,
> >
> >I know we talked about this before, but I think we should think about
> >using subversion instead of CVS for the directory project.  The benefits
> >are becoming apparent now.  Right off the bat it will help with the
> >migration from source forge, plus the advantages of the Meta-data and
> >atomic check-ins.  I know there may be a small learning curve, but I
> >would rather do this now when we are changing infrastructure anyway,
> >than have to go through this in the future when we are worried more
> >important things: the releases, code, etc.
> >
> >So I am a +1 to use Subversion instead of CVS.
> >
> >Jeff
> >
> >
> >
> >
> 
> --
> 
> Stephen J. McConnell
> mailto:mcconnell@apache.org
> 
> |------------------------------------------------|
> | Magic by Merlin                                |
> | Production by Avalon                           |
> |                                                |
> | http://avalon.apache.org/merlin                |
> | http://dpml.net/                               |
> |------------------------------------------------|
> 
> 



Re: Rethink Subversion

Posted by Stephen McConnell <mc...@apache.org>.
+1 because I want to make Noel happy instead of
worrying about a Christmas card.

:-)

(I the meantime I hope there is a way cool
Windows desktop tool for this)


Jeff Machols wrote:

>Guys,
>
>I know we talked about this before, but I think we should think about
>using subversion instead of CVS for the directory project.  The benefits
>are becoming apparent now.  Right off the bat it will help with the
>migration from source forge, plus the advantages of the Meta-data and
>atomic check-ins.  I know there may be a small learning curve, but I
>would rather do this now when we are changing infrastructure anyway,
>than have to go through this in the future when we are worried more
>important things: the releases, code, etc.  
>
>So I am a +1 to use Subversion instead of CVS.
>
>Jeff
>
>
>  
>

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org

|------------------------------------------------|
| Magic by Merlin                                |
| Production by Avalon                           |
|                                                |
| http://avalon.apache.org/merlin                |
| http://dpml.net/                               |
|------------------------------------------------|





Re: Rethink Subversion

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.

> +1 from me, too.  And I say that knowing full well that we will have some
> growing pains with Subversion.

I don't know if this is a project interested in (or appropriate for)
Gumping, but I just added SVN support to Python Gump and am interested in
working with a project in SVN to mature this. If you go with SVN, and are
game for this, let the Gump list know and we'll help out with any
descriptors needed.

regards

Adam


RE: Rethink Subversion

Posted by "Noel J. Bergman" <no...@devtech.com>.
> Be wary of the branch/tag support. In general, it works just fine. If
> you've done some complicated branch/tag funkiness, then you may run
> into some issues.

I don't believe that we have much to worry about in the current CVS.

> What "sub-project" are you referring to? Isn't the Directory just
> a single project? Shouldn't it be?

The directory project will have multiple related deliverables.   We've got
the LDAP server, we'll have JNDI code, we'll have Object and State factories
for useful things, and we agreed that we would be language-agnostic, so we
could have other codebases that are closely related.

> This is the preferred form for any codebase release. i.e. every codebase
> should have branches/tags/trunk.  The site area does not require branching
> or tagging, so it can remain a sibling.

>  /incubator/directory/subproject/branches
>  /incubator/directory/subproject/tags
>  /incubator/directory/subproject/trunk
>  /incubator/directory/site

Talking with Greg online, he explained that the SvnBook is currently "wrong"
in the section I read, and that the above is the desired layout.  What we
call a "subproject" above would be a "codebase" -- something that we plan to
label and release separately.  Anything that we would version independently.
The recommended layout is tied to release management.

> [the mod_authz_svn configuration] should be edited only by a subset
> at this point, similar to editing CVSROOT/avail. (e.g. infra + PMC chairs)

> I would also suggest that we perform access control along the lines of
> PMCs, rather than subproject granularity.

As I mentioned online, I can see reasons for wanting to control who has
access to partitions within the repository.  For example, we might want to
grant someone commit access to the site docs without granting access to the
code.  I do see your point about every PMC member having access across their
entire subtree(s), but that's easy enough to do.  And we still have umbrella
projects, where we don't give everyone commit access to every project in the
umbrella.

	--- Noel


Re: Rethink Subversion

Posted by Greg Stein <gs...@lyra.org>.
On Mon, Nov 24, 2003 at 06:09:58PM -0500, Noel J. Bergman wrote:
> > Here is how I would like to proceed
> 
> > I have brought down our CVS tarball from sourceforge.
> > I will create a local SVN report and use the cvs2svn
> > to get the initial SVN repo created.
> 
> Sounds good to me, although I am not a Subversion expert.  The more we can
> keep our CVS history, the better.

Yup, this is the basic approach. You'll want to produce a dump file which
can then be loaded into the main ASF repos. For testing, you can load it
into a private repos.

Be wary of the branch/tag support. In general, it works just fine. If
you've done some complicated branch/tag funkiness, then you may run into
some issues.

>...
> > I will then run the conversion script to change the
> > package names and add the apache license header to
> > the files.
> 
> Sounds correct.  I don't know if the new licenses are close enough that we
> can start using the short form of the new Apache Software License version 2.

The new license hasn't been approved for use yet. Therefore, the 1.1
license must be used, which also implies a full copy within each file.

> > I will probably only do this with one or two of the root level
> > directories.  Once it looks like everything works, we will do
> > a code freeze, and run the process for the entire CVS tarball,
> > and bring the new subversion repo in.
> 
> You might want to take a look at http://svn.apache.org/repos/asf/, which is
> the official ASF Subversion repository.  As I understand it, there will only
> be one repository, rather than one per project.

Correct. Given the renames and shifting of projects that occurs, having
everything in one repository where we can track those moves will be very
handy.

> So we'll need to be told
> where to put our directory structure.  As a guess:
> 
>   /incubator/directory/branches/sub-project
>   /incubator/directory/tags/sub-project
>   /incubator/directory/trunk/sub-project
>   /incubator/directory/site

What "sub-project" are you referring to? Isn't the Directory just a single
project? Shouldn't it be?

> but one of the Subversion folks could recommend:
> 
>   /incubator/directory/sub-project/branches
>   /incubator/directory/sub-project/tags
>   /incubator/directory/sub-project/trunk

This is the preferred form for any codebase release. i.e. every codebase
should have branches/tags/trunk.  The site area does not require branching
or tagging, so it can remain a sibling.

Assuming you don't have any subprojects, then you'd have:

  /incubator/directory/branches
  /incubator/directory/tags
  /incubator/directory/trunk
  /incubator/directory/site

If you have subprojects, then you'd add a layer:

  /incubator/directory/subproject/branches
  /incubator/directory/subproject/tags
  /incubator/directory/subproject/trunk
  /incubator/directory/site

Of course, you can start without subprojects, reorganize later as needed.

The Apache Commons project keeps its PMC-wide status file at:

  /commons/STATUS

Codebases within Commons have a STATUS file located in their trunk so that
it gets versioned along with the code development.

> instead.  I don't know the Best Practice for laying out a Subversion
> repository.  See also: http://svnbook.red-bean.com/book.html#svn-ch4-sect7.1

See above :-)

>...
> Infrastructure will have to set up access and/or provide instructions for
> the temporary mechanism.  We have mod_authz_svn setup, and controlled by a
> master file.  I'm fairly sure that we are not going to want every Committer
> editing that file.  And I am hoping that we will have SSL to protect the
> passwords soon.

No... it should be edited only by a subset at this point, similar to
editing CVSROOT/avail. (e.g. infra + PMC chairs)

I would also suggest that we perform access control along the lines of
PMCs, rather than subproject granularity. Currently, there are four PMCs
who (plan to) use the SVN repos: Commons, Incubator, XML, and Jakarta.
IMO, our mod_authz_svn config file should reflect that breakdown; I don't
think we should have different sets of access/responsibility.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

Re: Rethink Subversion

Posted by Greg Stein <gs...@lyra.org>.
On Mon, Nov 24, 2003 at 06:09:58PM -0500, Noel J. Bergman wrote:
> > Here is how I would like to proceed
> 
> > I have brought down our CVS tarball from sourceforge.
> > I will create a local SVN report and use the cvs2svn
> > to get the initial SVN repo created.
> 
> Sounds good to me, although I am not a Subversion expert.  The more we can
> keep our CVS history, the better.

Yup, this is the basic approach. You'll want to produce a dump file which
can then be loaded into the main ASF repos. For testing, you can load it
into a private repos.

Be wary of the branch/tag support. In general, it works just fine. If
you've done some complicated branch/tag funkiness, then you may run into
some issues.

>...
> > I will then run the conversion script to change the
> > package names and add the apache license header to
> > the files.
> 
> Sounds correct.  I don't know if the new licenses are close enough that we
> can start using the short form of the new Apache Software License version 2.

The new license hasn't been approved for use yet. Therefore, the 1.1
license must be used, which also implies a full copy within each file.

> > I will probably only do this with one or two of the root level
> > directories.  Once it looks like everything works, we will do
> > a code freeze, and run the process for the entire CVS tarball,
> > and bring the new subversion repo in.
> 
> You might want to take a look at http://svn.apache.org/repos/asf/, which is
> the official ASF Subversion repository.  As I understand it, there will only
> be one repository, rather than one per project.

Correct. Given the renames and shifting of projects that occurs, having
everything in one repository where we can track those moves will be very
handy.

> So we'll need to be told
> where to put our directory structure.  As a guess:
> 
>   /incubator/directory/branches/sub-project
>   /incubator/directory/tags/sub-project
>   /incubator/directory/trunk/sub-project
>   /incubator/directory/site

What "sub-project" are you referring to? Isn't the Directory just a single
project? Shouldn't it be?

> but one of the Subversion folks could recommend:
> 
>   /incubator/directory/sub-project/branches
>   /incubator/directory/sub-project/tags
>   /incubator/directory/sub-project/trunk

This is the preferred form for any codebase release. i.e. every codebase
should have branches/tags/trunk.  The site area does not require branching
or tagging, so it can remain a sibling.

Assuming you don't have any subprojects, then you'd have:

  /incubator/directory/branches
  /incubator/directory/tags
  /incubator/directory/trunk
  /incubator/directory/site

If you have subprojects, then you'd add a layer:

  /incubator/directory/subproject/branches
  /incubator/directory/subproject/tags
  /incubator/directory/subproject/trunk
  /incubator/directory/site

Of course, you can start without subprojects, reorganize later as needed.

The Apache Commons project keeps its PMC-wide status file at:

  /commons/STATUS

Codebases within Commons have a STATUS file located in their trunk so that
it gets versioned along with the code development.

> instead.  I don't know the Best Practice for laying out a Subversion
> repository.  See also: http://svnbook.red-bean.com/book.html#svn-ch4-sect7.1

See above :-)

>...
> Infrastructure will have to set up access and/or provide instructions for
> the temporary mechanism.  We have mod_authz_svn setup, and controlled by a
> master file.  I'm fairly sure that we are not going to want every Committer
> editing that file.  And I am hoping that we will have SSL to protect the
> passwords soon.

No... it should be edited only by a subset at this point, similar to
editing CVSROOT/avail. (e.g. infra + PMC chairs)

I would also suggest that we perform access control along the lines of
PMCs, rather than subproject granularity. Currently, there are four PMCs
who (plan to) use the SVN repos: Commons, Incubator, XML, and Jakarta.
IMO, our mod_authz_svn config file should reflect that breakdown; I don't
think we should have different sets of access/responsibility.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

Re: Rethink Subversion

Posted by Peter Donald <pe...@realityforge.org>.
On Tue, 25 Nov 2003 09:02 am, Jeff Machols wrote:
> I will probably only do this with one or two of the root level
> directories.  Once it looks like everything works, we will do a code
> freeze, and run the process for the entire CVS tarball, and bring the
> new subversion repo in.

Wouldn't it be better to do the whole thing in one shebang with a code freeze 
while you do it. That way there is no chance that there will be wasted effort 
(ie doing diffs between two codebases etc). If you get everyone focused on 
getting the code into shape then it should not take too long.

-- 
Cheers,

Peter Donald
"All my life I wanted to be someone; I guess I should have been more 
specific."
-- Jane Wagner


Re: Serverside NIO: Not ready for Prime Time

Posted by Peter Donald <pe...@realityforge.org>.
On Wed, 26 Nov 2003 12:37 pm, Geir Magnusson Jr wrote:
> Ye gads.  Why can't you multithread the reads?  What possible reason
> could one come up with that the reads have to happen on the same thread
> as the select?

Because it doesn't work ;) 

I could offer a reasonable explanation of why that is so but ultimately it 
comes down to the fact that the underlying OSes are inconsistent - 
particularly when there is multiple CPUs. The java layers on top proably 
introduce more ways in which sligt differences can occur. 

Consider the scenario

CPU1 returns Select with FD3

> > See attached files for the sort of thing I mean. Associated with each
> > connection object I have a TcpTransport object. The selector threads
> > does all
> > the nbio and then sends event to "parsing" stage. This seems to work
> > like a
> > charm.
>
> Don't that serialize the I/O?

Not sure what you mean. It is a little bit "unfair" because usually the 
SelectorKeys are returned in order of underlying FDs and thus channels early 
in the set are always early in the set. But as long as you randomizethe 
processing order this should not be an issue.

As long as you dont do memory allocation in selector thread then all that 
thread does is select() and memcpy() which can scale relatively well even if 
you batch it and randomize events when you pass them o0nto next stage.

-- 
Cheers,

Peter Donald
*-----------------------------------------------------*
| Never argue with an idiot, they'll drag you down to |
| their level, and beat you with experience           |
*-----------------------------------------------------* 


Re: Serverside NIO: Not ready for Prime Time

Posted by Geir Magnusson Jr <ge...@4quarters.com>.
On Nov 25, 2003, at 8:25 PM, Peter Donald wrote:

> On Wed, 26 Nov 2003 03:13 am, Wes McKean wrote:
>> The CancelledKeyException seems to be happing because I am removing 
>> the
>> SelectionKey from the iterator.  The other error seems to occur when 
>> I have
>> multiple reads and writes going on with different SocketChannels.  
>> Here is
>> the exception:
>
> I think some of problems will be that you are processing the channels 
> in
> different threads from the select. I can not see a good reason for 
> this.
> Would it not be better to do the reads in the same thread as the 
> selector,
> buffer the data and then send an event that is processed in another 
> thread.

Ye gads.  Why can't you multithread the reads?  What possible reason 
could one come up with that the reads have to happen on the same thread 
as the select?

>
> See attached files for the sort of thing I mean. Associated with each
> connection object I have a TcpTransport object. The selector threads 
> does all
> the nbio and then sends event to "parsing" stage. This seems to work 
> like a
> charm.

Don't that serialize the I/O?

>
> Anyways you may want to check out the spice/sandbox/sca project at
> cvs.codehaus.org:/scm/cvs as it contains code that simplifies working 
> with
> selectors etc.
>
> -- 
> Cheers,
>
> Peter Donald
> I think the next best thing to solving a
> problem is finding some humor in it.
>                 - Frank A. Clark
> <TcpTransport.java>
-- 
Geir Magnusson Jr                                   203-247-1713(m)
geir@4quarters.com


Re: Serverside NIO: Not ready for Prime Time

Posted by Peter Donald <pe...@realityforge.org>.
On Wed, 26 Nov 2003 03:13 am, Wes McKean wrote:
> The CancelledKeyException seems to be happing because I am removing the
> SelectionKey from the iterator.  The other error seems to occur when I have
> multiple reads and writes going on with different SocketChannels.  Here is
> the exception:

I think some of problems will be that you are processing the channels in 
different threads from the select. I can not see a good reason for this. 
Would it not be better to do the reads in the same thread as the selector, 
buffer the data and then send an event that is processed in another thread.

See attached files for the sort of thing I mean. Associated with each 
connection object I have a TcpTransport object. The selector threads does all 
the nbio and then sends event to "parsing" stage. This seems to work like a 
charm.

Anyways you may want to check out the spice/sandbox/sca project at 
cvs.codehaus.org:/scm/cvs as it contains code that simplifies working with 
selectors etc. 

-- 
Cheers,

Peter Donald
I think the next best thing to solving a 
problem is finding some humor in it. 
                - Frank A. Clark 

Re: Serverside NIO: Not ready for Prime Time

Posted by Wes McKean <wm...@logictrends.com>.
If you want to look at my code, check out the nio sub project under sandbox0 
on the sf.net site.  To recap at a high level here, I am:

1.  Creating a non blocking server socket which waits for connect events.  
Once a connect event occurs, the resulting SocketChannel is accepted and 
passed off to the input manager.

2.  The InputManager makes the SocketChannel non-blocking, then registers it 
for READ events with its Selector.  This occurs in two different threads 
( the registration and the selecting ).

3.  When a read event occurs, I do the usual.  I get the selected keys, get an 
iterator, process them one at a time, removing them as I do, then loop back 
around to select again.

I am getting two errors, a NullPointerException, and a CancelledKeyException.  

The CancelledKeyException seems to be happing because I am removing the 
SelectionKey from the iterator.  The other error seems to occur when I have 
multiple reads and writes going on with different SocketChannels.  Here is 
the exception:

java.lang.NullPointerException
        at sun.nio.ch.WindowsSelectorImpl
$SubSelector.processFDSet(WindowsSelect
orImpl.java:309)
        at sun.nio.ch.WindowsSelectorImpl
$SubSelector.processSelectedKeys(Window
sSelectorImpl.java:284)
        at sun.nio.ch.WindowsSelectorImpl$SubSelector.access$2600
(WindowsSelecto
rImpl.java:245)
        at 
sun.nio.ch.WindowsSelectorImpl.updateSelectedKeys(WindowsSelectorImpl
.java:427)
        at 
sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:142)

        at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:59)
        at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:70)
        at ldapd.server.input.InputModule.run(InputModule.java:131)
        at java.lang.Thread.run(Thread.java:534)

Wes

On Tuesday 25 November 2003 08:38 am, Peter Donald wrote:
> On Tue, 25 Nov 2003 11:56 pm, Wes McKean wrote:
> > I was running ldapd on a Windows XP box with  the new server side NIO
> > stuff included, and I was getting all kinds of weird messages inside the
> > sun implementation classes.  The same exact code works fine under Linux. 
> > It is my professional opinion that there are some issues with the Windows
> > XP implementation of non-blocking sockets, and we couldn't put this stuff
> > into the server until these issues are addressed.
>
> There are a large number of platform specific issues - but that is no
> different from differences between pre-nio sockets on linux and windows. I
> have been building a NIO based network layer recently so if you describe
> some of the exact issues then I may be able to show how to avoid or give
> code to do just that.


Re: Serverside NIO: Not ready for Prime Time

Posted by Peter Donald <pe...@realityforge.org>.
On Tue, 25 Nov 2003 11:56 pm, Wes McKean wrote:
> I was running ldapd on a Windows XP box with  the new server side NIO stuff
> included, and I was getting all kinds of weird messages inside the sun
> implementation classes.  The same exact code works fine under Linux.  It is
> my professional opinion that there are some issues with the Windows XP
> implementation of non-blocking sockets, and we couldn't put this stuff into
> the server until these issues are addressed.

There are a large number of platform specific issues - but that is no 
different from differences between pre-nio sockets on linux and windows. I 
have been building a NIO based network layer recently so if you describe some 
of the exact issues then I may be able to show how to avoid or give code to 
do just that.

-- 
Cheers,

Peter Donald
"Education is a progressive discovery of 
   our own ignorance." - Will Durant 


Serverside NIO: Not ready for Prime Time

Posted by Wes McKean <wm...@logictrends.com>.
Hi Folks!

I was running ldapd on a Windows XP box with  the new server side NIO stuff 
included, and I was getting all kinds of weird messages inside the sun 
implementation classes.  The same exact code works fine under Linux.  It is 
my professional opinion that there are some issues with the Windows XP 
implementation of non-blocking sockets, and we couldn't put this stuff into 
the server until these issues are addressed.

I fully expect the issues to be my fault :-)

Wes


RE: Rethink Subversion

Posted by "Noel J. Bergman" <no...@devtech.com>.
> Here is how I would like to proceed

> I have brought down our CVS tarball from sourceforge.
> I will create a local SVN report and use the cvs2svn
> to get the initial SVN repo created.

Sounds good to me, although I am not a Subversion expert.  The more we can
keep our CVS history, the better.

> Once this is done, I will work on moving the directory
> structures to the new layout (Which we still to define!).
> This is the part I will probably need some help with.

> I will then run the conversion script to change the
> package names and add the apache license header to
> the files.

Sounds correct.  I don't know if the new licenses are close enough that we
can start using the short form of the new Apache Software License version 2.

> I will probably only do this with one or two of the root level
> directories.  Once it looks like everything works, we will do
> a code freeze, and run the process for the entire CVS tarball,
> and bring the new subversion repo in.

You might want to take a look at http://svn.apache.org/repos/asf/, which is
the official ASF Subversion repository.  As I understand it, there will only
be one repository, rather than one per project.  So we'll need to be told
where to put our directory structure.  As a guess:

  /incubator/directory/branches/sub-project
  /incubator/directory/tags/sub-project
  /incubator/directory/trunk/sub-project
  /incubator/directory/site

but one of the Subversion folks could recommend:

  /incubator/directory/sub-project/branches
  /incubator/directory/sub-project/tags
  /incubator/directory/sub-project/trunk

instead.  I don't know the Best Practice for laying out a Subversion
repository.  See also: http://svnbook.red-bean.com/book.html#svn-ch4-sect7.1

Also, there is http://svn.apache.org/repos/test/, a test repository that I
had asked be setup so that people can play with Subversion without having to
install a server.

Infrastructure will have to set up access and/or provide instructions for
the temporary mechanism.  We have mod_authz_svn setup, and controlled by a
master file.  I'm fairly sure that we are not going to want every Committer
editing that file.  And I am hoping that we will have SSL to protect the
passwords soon.

	--- Noel


Re: Rethink Subversion

Posted by Jeff Machols <jm...@comcast.net>.
On Mon, 2003-11-24 at 16:27, Daniel Rall wrote:
> +1 from me, meaning I'm willing to help ease those growing pains.  I spoke about 
> this a bit with Alex at ApacheCon, and he also seemed very interested in trying 
> out Subversion.
> 
Thanks Daniel.  Here is how I would like to proceed, let me know what
you think.  

I have brought down our CVS tarball from sourceforge.  I will create a
local SVN report and use the cvs2svn to get the initial SVN repo
created.

Once this is done, I will work on moving the directory structures to the
new layout (Which we still to define!).  This is the part I will
probably need some help with.

I will then run the conversion script to change the package names and
add the apache license header to the files.

I will probably only do this with one or two of the root level
directories.  Once it looks like everything works, we will do a code
freeze, and run the process for the entire CVS tarball, and bring the
new subversion repo in.
> 
> Noel J. Bergman wrote:
> > +1 from me, too.  And I say that knowing full well that we will have some
> > growing pains with Subversion.
> > 
> > I am cc'ing Greg and the infrastructure folks to give them a heads up that
> > we may need some help ASAP to get started, if no one objects to using
> > Subversion.
> > 
> > 	--- Noel
> > 
> > -----Original Message-----
> > From: Jeff Machols [mailto:jmachols@comcast.net]
> > Sent: Monday, November 24, 2003 13:10
> > To: Apache Directory Developers List
> > Subject: Rethink Subversion
> > 
> > 
> > Guys,
> > 
> > I know we talked about this before, but I think we should think about
> > using subversion instead of CVS for the directory project.  The benefits
> > are becoming apparent now.  Right off the bat it will help with the
> > migration from source forge, plus the advantages of the Meta-data and
> > atomic check-ins.  I know there may be a small learning curve, but I
> > would rather do this now when we are changing infrastructure anyway,
> > than have to go through this in the future when we are worried more
> > important things: the releases, code, etc.
> > 
> > So I am a +1 to use Subversion instead of CVS.
> > 
> > Jeff
> 
> 


Re: Rethink Subversion

Posted by Daniel Rall <dl...@finemaltcoding.com>.
+1 from me, meaning I'm willing to help ease those growing pains.  I spoke about 
this a bit with Alex at ApacheCon, and he also seemed very interested in trying 
out Subversion.


Noel J. Bergman wrote:
> +1 from me, too.  And I say that knowing full well that we will have some
> growing pains with Subversion.
> 
> I am cc'ing Greg and the infrastructure folks to give them a heads up that
> we may need some help ASAP to get started, if no one objects to using
> Subversion.
> 
> 	--- Noel
> 
> -----Original Message-----
> From: Jeff Machols [mailto:jmachols@comcast.net]
> Sent: Monday, November 24, 2003 13:10
> To: Apache Directory Developers List
> Subject: Rethink Subversion
> 
> 
> Guys,
> 
> I know we talked about this before, but I think we should think about
> using subversion instead of CVS for the directory project.  The benefits
> are becoming apparent now.  Right off the bat it will help with the
> migration from source forge, plus the advantages of the Meta-data and
> atomic check-ins.  I know there may be a small learning curve, but I
> would rather do this now when we are changing infrastructure anyway,
> than have to go through this in the future when we are worried more
> important things: the releases, code, etc.
> 
> So I am a +1 to use Subversion instead of CVS.
> 
> Jeff



RE: Rethink Subversion

Posted by "Noel J. Bergman" <no...@devtech.com>.
+1 from me, too.  And I say that knowing full well that we will have some
growing pains with Subversion.

I am cc'ing Greg and the infrastructure folks to give them a heads up that
we may need some help ASAP to get started, if no one objects to using
Subversion.

	--- Noel

-----Original Message-----
From: Jeff Machols [mailto:jmachols@comcast.net]
Sent: Monday, November 24, 2003 13:10
To: Apache Directory Developers List
Subject: Rethink Subversion


Guys,

I know we talked about this before, but I think we should think about
using subversion instead of CVS for the directory project.  The benefits
are becoming apparent now.  Right off the bat it will help with the
migration from source forge, plus the advantages of the Meta-data and
atomic check-ins.  I know there may be a small learning curve, but I
would rather do this now when we are changing infrastructure anyway,
than have to go through this in the future when we are worried more
important things: the releases, code, etc.

So I am a +1 to use Subversion instead of CVS.

Jeff


Re: Rethink Subversion

Posted by Robb Penoyer <rp...@timgia.com>.
Yes, I am around, and +1.

R-

At 01:09 PM 11/24/2003 -0500, Jeff Machols wrote:
>Guys,
>
>I know we talked about this before, but I think we should think about
>using subversion instead of CVS for the directory project.  The benefits
>are becoming apparent now.  Right off the bat it will help with the
>migration from source forge, plus the advantages of the Meta-data and
>atomic check-ins.  I know there may be a small learning curve, but I
>would rather do this now when we are changing infrastructure anyway,
>than have to go through this in the future when we are worried more
>important things: the releases, code, etc.
>
>So I am a +1 to use Subversion instead of CVS.
>
>Jeff