Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of phil.steitz@gmail.com
 designates 209.85.192.179 as permitted sender)
Message-ID: <54AEAA25.1060501@gmail.com>
Date: Thu, 08 Jan 2015 09:02:45 -0700
From: Phil Steitz <phil.steitz@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: [Math] Next release: 4.0 or 3.5 ?
References: <9d0d72388bc3b4c98b53550809100214@scarlet.be>
 <6F5EB9E5-9AFF-4F83-A0F9-D20E144DBF7F@gmail.com> <54AE2AD3.2090700@gmail.com>
 <54AE930B.8000009@spaceroots.org>
In-Reply-To: <54AE930B.8000009@spaceroots.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

On 1/8/15 7:24 AM, Luc Maisonobe wrote:
> Le 08/01/2015 07:59, Thomas Neidhart a �crit :
>> On 01/08/2015 02:40 AM, Phil Steitz wrote:
>>>
>>>
>>>
>>>> On Jan 6, 2015, at 3:10 PM, Gilles <gilles@harfang.homelinux.org> wrote:
>>>>
>>>> Hi.
>>>>
>>>> Do we head towards 4.0, starting to implement  the dreaded
>>>> breakings?  ;-)
>>> How about starting a new 4.0 branch and keeping head set up for 3.x so we can cut 3.4.1 when the bugs start coming in against 3.4.
>> +1
> Of course a branch is needed, but why consider master should be 3.x and
> 4.0 should be a side branch.

I am OK either way.  We just need to be able to easily cut 3.4.1. 
Due to my mistake, we need to do that ASAP, so whatever git games
need to be played to get it set up so we can release from it, we
need to do it.

Phil
>
> If we consider 4.0 is the future and 3.x is only for bug fixes, then 4.0
> should be master and 3.x a side branch. This side branch could be
> created later on, if needed. It is straightforward to create new
> branches in git even from very old commits, so the branch creation can
> be delayed until needed (and only if needed).
>
> best regards,
> Luc
>
>
>> Thomas
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
> .
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org