Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Fri, 10 Jun 2016 00:56:10 +0200
From: Gilles <gilles@harfang.homelinux.org>
To: <dev@commons.apache.org>
Subject: Re: [Math] Commons Math (r)evolution
In-Reply-To: <5C4D5824-2762-469E-9BDF-C52A8AA11310@dslextreme.com>
References: <2e32ba99e52f26d0470246b7cc7f0e01@scarlet.be>
 <b15f0ea3fe848dd383d4d5ebf9803c44@scarlet.be>
 <3149c51f-6b28-c2c4-2356-6a5b9a5d5d6d@apache.org>
 <e40e7cb9170d6013e0f93c6297b2298a@scarlet.be>
 <c6277563-ba2d-2f8f-c7d2-b855dfe18062@apache.org>
 <e70e2e9cb81562dce1f678d51f7ce692@scarlet.be>
 <8d00333d-0ed3-b58d-daf6-a44d26bd0fec@apache.org>
 <3fcbc91f44dfe04f86a7bae4b8075e13@scarlet.be>
 <09fe39b0-2638-ee0b-c381-0a9500a4ae1f@apache.org>
 <882b02ac5e2898c00f0bada2dce1345d@scarlet.be>
 <CAG3-T37ejzd=Vg5vtxK4SmSNbqikTze8mxRU5nZhtUtOP2+B1g@mail.gmail.com>
 <ebb40b366b4b8fcaedde4064d42a7c0a@scarlet.be>
 <CAG3-T360_gzPqEdD2QxS=qiTY--wMQaBsauMU5zKMRm=-XMVzg@mail.gmail.com>
 <c5898107ae112d10d6d416cbbc54fc13@scarlet.be> <njb6qj$evj$1@ger.gmane.org>
 <9f280285c7ffb12f37840b146cd49449@scarlet.be>
 <5C4D5824-2762-469E-9BDF-C52A8AA11310@dslextreme.com>
Message-ID: <7f867c644d0153a11f0efaec48409def@scarlet.be>
User-Agent: Scarlet Webmail
X-DCC-scarlet.be-Metrics: eir; whitelist
X-Virus-Scanned: clamav-milter 0.98.1-exp at eir
X-Virus-Status: Clean
archived-at: Thu, 09 Jun 2016 22:56:22 -0000

On Thu, 9 Jun 2016 14:53:20 -0700, Ralph Goers wrote:
>> On Jun 9, 2016, at 2:12 PM, Gilles <gilles@harfang.homelinux.org> 
>> wrote:
>>
>> Hello Jörg.
>>
>> On Thu, 09 Jun 2016 09:43:06 +0200, Jörg Schaible wrote:
>>> Hi Gilles,
>>>
>>> Gilles wrote:
>>>
>>>> Hi.
>>>>
>>>> On Wed, 8 Jun 2016 23:50:00 +0300, Artem Barger wrote:
>>>>> On Wed, Jun 8, 2016 at 12:25 AM, Gilles
>>>>> <gilles@harfang.homelinux.org>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> According to JIRA, among 180 issues currently targeted for the
>>>>>>>> next major release (v4.0), 139 have been resolved (75 of which
>>>>>>>> were not in v3.6.1).
>>>>>>>>
>>>>>>>>
>>>>>>> ​Huh, it's above of 75% completion :)​
>>>>>>>
>>>>>>
>>>>>> Everybody is welcome to review the "open" issues and comment
>>>>>> about them.
>>>>>>
>>>>>>
>>>>> ​I guess someone need to prioritize them​ according to they
>>>>> importance for
>>>>> release.
>>>>
>>>> Importance is relative... :-}
>>>>
>>>> IMO, it is important to not release unsupported code.
>>>
>>> Unit test *are* kind of support.
>>
>> Unit tests are not what I mean by "support".  They only increase the
>> probability that the code behaves as expected. [And sometimes they 
>> do
>> not because they can be buggy too, as I discovered when refactoring
>> the "random" package.]
>
> Now that is a funny argument.  If you can write a proper unit test
> for the code typically you understand what the code is doing and 
> could
> fix it if needed.

Yes.  Where did I say otherwise?

>>
>> But anyways, my reservations have nothing to do with the 
>> functionality
>> of released code: users who are satisfied with the service provided 
>> by
>> v3.6.1 (or any of the previous versions of CM) have no reason to 
>> upgrade
>> to 4.0.  [By upgrading, all they get is the obligation to change the
>> "import" statements.]
>>
>> And we have no reason to release a v4.0 of a code that
>> 1. has not changed
>> 2. is not supported
>
> What you seem to be proposing is tossing code that “isn’t supported”
> even if it works just fine. I don’t understand why you would want to
> do that.

No, you misunderstood: I want to work on, and release, code which we
can support.
Code which we can't support will stay in the "develop" branch until
someone feels confident to release it.

> What I am seeing here is a bunch of people coming on board who seem
> to really want to help and get involved. Before doing radical things
> like dumping a large portion of the code base please take the time to
> see how things play out.

I did take the time (and I'm not going to continue wasting my time the
way I did all these years).

I just gave two examples of unsolvable issues due to code being
unsupported.  Please let us know how you'd handle them.

Also, to conclude a discussion that go in circles: I'm not preventing
(how could I?) you to release CM v4.0 with whatever contents you see
fit.
I gave my arguments for discouraging such a step and others in favour
of my preferred alternative, which I'd like to start working on,
concretely, in order to see how it'll play out indeed.

Gilles

> Ralph


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