Reading up through this, all sound good to me!
Cheers,
Woonsan
On Thu, Feb 21, 2019 at 6:45 AM Davide Giannella wrote:
>
> So much for having said... ;)
> > Please let's focus on the process here and ignore the version number.
>
> In-line as usual
>
> On 20/02/2019 14:54, Marcel Reutegger wrote
So much for having said... ;)
> Please let's focus on the process here and ignore the version number.
In-line as usual
On 20/02/2019 14:54, Marcel Reutegger wrote:
> Hi,
>
> On 20.02.19, 13:21, "Robert Munteanu" wrote:
>> On Wed, 2019-02-20 at 10:45 +, Davide Giannella wrote:
>>> - Any previ
On Wed, 2019-02-20 at 14:54 +, Marcel Reutegger wrote:
> Hi,
>
> On 20.02.19, 13:21, "Robert Munteanu" wrote:
> > On Wed, 2019-02-20 at 10:45 +, Davide Giannella wrote:
> > > - Any previous oak release will be automatically deprecated. What
> > > has
> > > been already branched and releas
Hi,
On 20.02.19, 13:21, "Robert Munteanu" wrote:
> On Wed, 2019-02-20 at 10:45 +, Davide Giannella wrote:
> > - Any previous oak release will be automatically deprecated. What has
> > been already branched and released still stays there. This applies
> > only
> > to future releases.
>
> So s
Hi,
On Wed, 2019-02-20 at 10:45 +, Davide Giannella wrote:
> - Any previous oak release will be automatically deprecated. What has
> been already branched and released still stays there. This applies
> only
> to future releases.
So say we release 1.12 from trunk and then 1.12.1 from trunk. Do
Good morning team,
there were some discussions face to face between some of the Oak team
members about the many branches we currently have to support and how we
could better support the changing world around releases of "tools" we
use. Most notably is the JVM support and release model from Oracle.
