I see I am too late to add my +1.  Thanks for the work Craig.  I will
try and test this on Monday.

Sean

ps. The continuum server is just sitting idly.  We could start adding
projects to it now if we wanted.

On 6/16/06, James Mitchell <[EMAIL PROTECTED]> wrote:
+1 -- Everything looks great.

--
James Mitchell




On Jun 16, 2006, at 9:58 PM, Craig McClanahan wrote:

> On 6/16/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>>
>> On 6/16/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
>>
>> >  I think It's now to the point where I'd like to make
>> > this the trunk, and get back to fixing bugs and implementing
>> RFEs.  What
>> say
>> > ye?  If there's no objections, my plan is to copy the current
>> trunk to a
>> > "pre-maven" branch as is, then copy the "mvn_reorg" to the regular
>> trunk.
>> > I'd like to do this by tomorrow (Saturday June 17) evening, Pacific
>> time, so
>> > we can start addressing the backlog of issues.
>>
>> +1 on the general idea, but I would just:
>>
>>   svn mv shale/trunk      shale/tags/SHALE_PRE_MAVEN2
>>   svn mv shale/branches/mvn_reorg     shale/trunk
>>
>> (Done remotely, as no one is likely to have all the tags and branches
>> checked out.)
>
>
> That's pretty much what I had in mind, except
> "shale/branches/SHALE_PRE_MAVEN2".  The thinking was that we might
> still
> have to update the website out of the old tree, until all the
> wrinkles are
> ironed out in the new tree.
>
> As for "branches" versus "tags", that is basically just a
> convention anyway
> ... Subversion treats them identically.
>
> I don't think we need either a branch for the pre-Maven code (just a
>> tag) or to keep a copy of what is now mvn_reorg in branches.  Maybe
>> there were some implied "deletes" in your original plan. :)
>
>
> Agree that we don't need to keep any separate copy of the "mvn_reorg"
> branch.
>
> --
>> Wendy
>
>
> Craig


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to