Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
Date: Thu, 10 Aug 2006 02:41:54 +0200
From: Kristian Waagan <Kristian.Waagan@Sun.COM>
Subject: Re: Beta Announcement and encouraging user testing
In-reply-to: <44DA7C23.7000200@sun.com>
Sender: Kristian.Waagan@Sun.COM
To: derby-dev@db.apache.org
Cc: kmarsdenderby@sbcglobal.net
Message-id: <44DA80D2.1060809@Sun.com>
Organization: Sun Microsystems Inc.
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <44D7B2AB.60006@sbcglobal.net> <44DA4500.7000400@sun.com>
 <44DA61E5.4050708@sun.com>
 <54ac72d70608091539q1a89572ck2af5aaa4a726e24@mail.gmail.com>
 <44DA6854.7050607@sun.com> <44DA6A6F.5030509@apache.org>
 <44DA737E.4090909@sun.com> <44DA7748.3020909@sbcglobal.net>
 <54ac72d70608091718n4f9260a3yf341b9d1fa02974b@mail.gmail.com>
 <44DA7C23.7000200@sun.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; no-NO;
 rv:1.8.0.5) Gecko/20060730
 Thunderbird/1.5.0.5 Mnenhy/0.7.4.0

David Van Couvering wrote:
> Interesting idea.  I feel like I'm really missing something.  If no 
> other changes go into the svn copy, why are we making the copy?

I guess the goal is to flip the beta flag in the copy.
Trunk would still be alpha as usual.
This would be approach 4) Other options, where the following cons are gone:
- The beta candidate says that it is alpha.
- The trunk says it is beta, which may be confusing.

Based on Andrews suggestion, the copy is "thrown away"/forgotten when 
the time comes to create the real branch.


-- 
Kristian

> 
> David
> 
> Andrew McIntyre wrote:
>> On 8/9/06, Kathey Marsden <kmarsdenderby@sbcglobal.net> wrote:
>>>
>>> I say this is not true.  We make the branch and just make that one beta
>>> flag flip.
>>> Everyone gets their builds setup and running but we keep working on the
>>> trunk.
>>> Nobody bothers with merging fixes to the branch.
>>>
>>> Then at whatever point we feel we need a real branch  someone does  one
>>> biggish merge
>>> with the range for all that has gone into the trunk so far and just
>>> reverse merge the one change
>>> for the 10.3 version bump.
>>
>> There's another option, too, that I just thought of. svn copy the
>> trunk into tags/10.2.1.0_beta. Flip the beta flag, roll the beta
>> distributions. No other changes go into this copy of the trunk.
>>
>> When the time comes, branch the new 10.2.1.0 branch off the trunk, and
>> do any reverse merging as necessary.
>>
>> SVN copies are cheap, we should take advantage of that.
>>
>> andrew