Hi.
[Sorry for not replying earlier; I've been quite diverted
by what happened around the RNG-37 issue[1].]
On Mon, 11 Dec 2017 16:16:34 +, Stephen Colebourne wrote:
This all seems reasonable. One things I'd suggest is getting at least
one new component to a full release as soon as possible
On Dec 11, 2017 09:17, "Stephen Colebourne" wrote:
This all seems reasonable. One things I'd suggest is getting at least
one new component to a full release as soon as possible to demonstrate
that the plan can work. This suggests that step 1 involves a full
release for [numbers]
Right, get the
This all seems reasonable. One things I'd suggest is getting at least
one new component to a full release as soon as possible to demonstrate
that the plan can work. This suggests that step 1 involves a full
release for [numbers]
Stephen
On 9 December 2017 at 01:59, Gilles wrote:
> Hi all.
>
> S
I think I have some issues WRT "supported" and "unsupported" code that I
have mentioned on this list in the past but I do not want to stand in the
way of work getting done. So go for it. Our community will voice, hack and
vote I hope, with as much energy, diligence, and perseverance as you have
sho
This sounds like an approach analogous to the incubator modules in OpenJDK
itself.
Hopefully this will suit both worlds. Those who want the complete bundle
can do so, those who want discrete modules can do so.
Cheers,
Martijn
On 9 December 2017 at 01:59, Gilles wrote:
> Hi all.
>
> Stephen Co
Hi all.
Stephen Colebourne correctly summarized the situation[1]:
Project management must be based on life-cycle, not the
other way around.
Here below, a concrete plan is proposed in answer to the
suggestion (of a fork) made by Martijn Verburg[2].
1. Initial (beta?) release of "Commons Numbers"
