Executive summary (to the best of my knowledge):
Ready (IMHO) for release ("no known issues"):
* Module "core"
* Module "angle"
* Module "arrays"
* Class "Complex"
Not to be released:
* Class "ComplexUtils" (outdated API to be replaced by "streams",
insufficient coverage, ...)
* Module
On Thu, 10 May 2018 18:08:13 -0600, Gary Gregory wrote:
On Thu, May 10, 2018 at 5:10 PM, Gilles
wrote:
On Thu, 10 May 2018 08:22:40 -0600, Gary Gregory wrote:
How about releasing as "beta" i.e. 1.0-beta1?
It would not reflect the real status.
As noted below, "Complex" is past beta,
Gr
On Thu, May 10, 2018 at 5:10 PM, Gilles
wrote:
> On Thu, 10 May 2018 08:22:40 -0600, Gary Gregory wrote:
>
>> How about releasing as "beta" i.e. 1.0-beta1?
>>
>
> It would not reflect the real status.
> As noted below, "Complex" is past beta,
Great.
> while some of the
> other codes need revi
On Thu, 10 May 2018 08:22:40 -0600, Gary Gregory wrote:
How about releasing as "beta" i.e. 1.0-beta1?
It would not reflect the real status.
As noted below, "Complex" is past beta, while some of the
other codes need review and/or a little work to settle
known issues.
Furthermore, I recall that
How about releasing as "beta" i.e. 1.0-beta1?
Gary
On Thu, May 10, 2018 at 7:39 AM, Gilles
wrote:
> Hi.
>
> The modules in [Numbers] are not all in a releasable state;
> even if a lot of work has been put in all of them, some
> need even more to be on a par with e.g. the "Complex" class.
>
> It
Hi.
The modules in [Numbers] are not all in a releasable state;
even if a lot of work has been put in all of them, some
need even more to be on a par with e.g. the "Complex" class.
It doesn't seem to serve any purpose to further delay the
release as there isn't any activity towards resolving the
