Re: Creating sandbox branches

Thu, 31 Aug 2006 08:09:22 -0700 

Hi Kevin,
The way I've seen other projects handle this is by using branches as the place to do whole sale refactoring/changes and 'sandbox' is a place for additional code that might or might not ever make it to the trunk. If the refactoring/change that was started in a branch does not work out then its easy enough to delete it. 


Another thing to consider is using SVK (http://svk.elixus.org/) to  
manage getting changes made to trunk into the branch and the changes  
from the trunk eventually into the trunk. I've not done it personally  
but I've heard others say it worked well for them. I will try to  
scare up some additional info on it for you if you are interested.


TTFN,

-bd-

On Aug 31, 2006, at 8:07 AM, Kevin Sutter wrote:


Craig,

You are correct.  I can create a sandbox at the same level as  
"trunk", just
like your example showed.  But, I don't think we want to create  
them at the
"trunk" level.  I would think we would want a separate directory  
structure

to place the sandboxes in.  Something like...

openjpa/site
openjpa/trunk
openjpa/tags
openjpa/branches
openjpa/sandboxes


Then, when we get to the position of having official releases and  
fixpacks,

we can use the tags and branches subdirectories to store these.


We could use the "sandboxes" directory to store the development  
sandboxes

without cluttering up the root.

That's my idea anyway...
Kevin

On 8/31/06, Craig L Russell <[EMAIL PROTECTED]> wrote:


IIUC, any committer can create a sandbox by using the svn copy
command. e.g.

svn copy https://svn.apache.org/repos/asf/incubator/openjpa/trunk/
https://svn.apache.org/repos/asf/incubator/openjpa/sandbox

You can then merge back from the sandbox (I'm not really able to give
you details here...)

If this doesn't work for you, I'll be happy to give it a try. Let me
know.

Craig

On Aug 30, 2006, at 10:01 PM, Patrick Linskey wrote:

> +1.
>
> Now, to find the right person....
>
> -Patrick
>
> --
> Patrick Linskey
> BEA Systems, Inc.
>
>> -----Original Message-----
>> From: Kevin Sutter [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, August 30, 2006 2:50 PM
>> To: [email protected]
>> Subject: Re: Creating sandbox branches
>>

>> Still looking for some response to this request...  Looking at  
other

>> incubator projects, some are using "sandbox", some are using
>> "branches",
>> others don't seem to have an alternate folder for misc development
>> branches.  I would create the folders if I had the proper
>> authority.  Who
>> does have the authority?  And, when we find that person, what
>> should we have
>> them create?
>>
>> We already have "site" and "trunk".  I think to be consistent with
>> svn
>> practices, we should have a "branches" and "tags" folder at a
>> minimum.  If
>> we want to keep "branches" pristine for real versions of
>> OpenJPA, then we
>> should also create a "sandbox" folder to house any sandbox
>> development
>> branches.
>>
>> Thanks,
>> Kevin
>>
>> On 8/22/06, Kevin Sutter <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi,

>>> You've probably noticed that I attempted to create a branch  
for the

>>> OPENJPA-24 work (I've been busy with a conference and some
>> of Abe's changes
>>> were starting to overlap..).  But, when I attempted to
>> create this branch in
>>> a "branches" subdirectory, I got an authentication error
>> with creating the
>>> directory.  As you probably noticed, I was allowed to
>> create the OPENJPA-24
>>> branch at the root level (same level as trunk), but I
>> didn't think that was
>>> appropriate.  (I deleted that one.)
>>>
>>> So, what's the scoop with sandbox branches?  Should we be
>> allowed to use
>>> these?  I hope so, since this provides a nice way of sharing and
>>> collaborating on changes that are bigger than a breadbox.
>> If we agree,
>>> could someone with enough authority create the branches
>> folder so that we
>>> have a place to put them?
>>>
>>> Thanks!
>>> Kevin
>>>
>>

>  
_____________________________________________________________________ 
_

> _
> Notice:  This email message, together with any attachments, may
> contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and
> affiliated
> entities,  that may be confidential,  proprietary,  copyrighted
> and/or
> legally privileged, and is intended solely for the use of the
> individual
> or entity named in this message. If you are not the intended
> recipient,
> and have received this message in error, please immediately return
> this
> by email and then delete it.

Craig 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!




























					Reply via email to