release it!

[Anatole Tresch <at...@gmail.com>]

Hi Guys

is there anything that speaks against building a new release? If no, we
should build one.

J Anatole

Re: release it!

[Werner Keil <we...@gmail.com>]

It would be a good idea to deprecate the JSR support and remove it in a
future release.

Werner



On Wed, Jul 17, 2019 at 8:24 AM Anatole Tresch <at...@gmail.com> wrote:

> OK, let's check how the release documentation looks like (AFAIK Oli did one
> the last time). If this works, things should be relatively easy. Since we
> do not build a binary release, main tasks are pre-releasing (building,
> testing, tagging) and go for the release votes ones things are in place.
> The homepage can be updated in a second step.
>
> Am Mi., 17. Juli 2019 um 00:21 Uhr schrieb William Lieurance <
> william.lieurance@namikoda.com>:
>
> > I'll certainly +1 a release now and also am in favor of more frequent
> > releases in the future.
> >
> > Sent from a tiny keyboard
> >
> > ________________________________
> > From: P. Ottlinger <po...@apache.org>
> > Sent: Tuesday, July 16, 2019 5:17:48 PM
> > To: dev@tamaya.incubator.apache.org
> > Subject: Re: release it!
> >
> > Am 17.07.19 um 00:16 schrieb Werner Keil:
> > > The JSR will never be out, it was withdrawn in favor of either
> > MicroProfile
> > > Config, a future Jakarta spec or both.
> > > the Jakarta spec is not there but keeping the old JSR in there would
> > cause
> > > more confusion, in a sandbox module I guess it is at people's own risk.
> >
> >
> > thanks for the explanation - why don't we release it with 0.4 and remove
> > it with 0.5?
> >
> > This would mean a higher release frequency which could help us graduate
> > as a TLP ;)
> >
> > Cheers,
> > Phil
> >
>
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
> *Twitter:  @atsticks, @tamayaconf*
>

Re: release it!

[Anatole Tresch <at...@gmail.com>]

OK, let's check how the release documentation looks like (AFAIK Oli did one
the last time). If this works, things should be relatively easy. Since we
do not build a binary release, main tasks are pre-releasing (building,
testing, tagging) and go for the release votes ones things are in place.
The homepage can be updated in a second step.

Am Mi., 17. Juli 2019 um 00:21 Uhr schrieb William Lieurance <
william.lieurance@namikoda.com>:

> I'll certainly +1 a release now and also am in favor of more frequent
> releases in the future.
>
> Sent from a tiny keyboard
>
> ________________________________
> From: P. Ottlinger <po...@apache.org>
> Sent: Tuesday, July 16, 2019 5:17:48 PM
> To: dev@tamaya.incubator.apache.org
> Subject: Re: release it!
>
> Am 17.07.19 um 00:16 schrieb Werner Keil:
> > The JSR will never be out, it was withdrawn in favor of either
> MicroProfile
> > Config, a future Jakarta spec or both.
> > the Jakarta spec is not there but keeping the old JSR in there would
> cause
> > more confusion, in a sandbox module I guess it is at people's own risk.
>
>
> thanks for the explanation - why don't we release it with 0.4 and remove
> it with 0.5?
>
> This would mean a higher release frequency which could help us graduate
> as a TLP ;)
>
> Cheers,
> Phil
>


-- 
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
*Twitter:  @atsticks, @tamayaconf*

Re: release it!

[William Lieurance <wi...@namikoda.com>]

I'll certainly +1 a release now and also am in favor of more frequent releases in the future.

Sent from a tiny keyboard

________________________________
From: P. Ottlinger <po...@apache.org>
Sent: Tuesday, July 16, 2019 5:17:48 PM
To: dev@tamaya.incubator.apache.org
Subject: Re: release it!

Am 17.07.19 um 00:16 schrieb Werner Keil:
> The JSR will never be out, it was withdrawn in favor of either MicroProfile
> Config, a future Jakarta spec or both.
> the Jakarta spec is not there but keeping the old JSR in there would cause
> more confusion, in a sandbox module I guess it is at people's own risk.


thanks for the explanation - why don't we release it with 0.4 and remove
it with 0.5?

This would mean a higher release frequency which could help us graduate
as a TLP ;)

Cheers,
Phil

Re: release it!

["P. Ottlinger" <po...@apache.org>]

Am 17.07.19 um 00:16 schrieb Werner Keil:
> The JSR will never be out, it was withdrawn in favor of either MicroProfile
> Config, a future Jakarta spec or both.
> the Jakarta spec is not there but keeping the old JSR in there would cause
> more confusion, in a sandbox module I guess it is at people's own risk.


thanks for the explanation - why don't we release it with 0.4 and remove
it with 0.5?

This would mean a higher release frequency which could help us graduate
as a TLP ;)

Cheers,
Phil

Re: release it!

[Werner Keil <we...@gmail.com>]

Phil,

The JSR will never be out, it was withdrawn in favor of either MicroProfile
Config, a future Jakarta spec or both.
the Jakarta spec is not there but keeping the old JSR in there would cause
more confusion, in a sandbox module I guess it is at people's own risk.

Werner



On Wed, Jul 17, 2019 at 12:38 AM P. Ottlinger <po...@apache.org> wrote:

> Am 16.07.19 um 16:42 schrieb Anatole Tresch:
> > the jsr382 module is in the sandbox and can be deleted or just removed
> from
> > the build. Any new abstractions from the jsr have been moved to the
> > microprofile api, but were not yet released, so the code written there
> will
> > be of great use once the next mp release is ready...
>
> I'd release it as it is ..... in case the new JSR is out, we might
> remove it then.
>
> To my mind there's so much change in the current version to rectify a
> release.
>
> I'm still not really able to do the release .... any other volunteer: go
> ahead.
>
> I can help a bit if there are questions concerning the homepage and
> stuff like that ...
>
> Cheers,
> Phil
>

Re: release it!

["P. Ottlinger" <po...@apache.org>]

Am 16.07.19 um 16:42 schrieb Anatole Tresch:
> the jsr382 module is in the sandbox and can be deleted or just removed from
> the build. Any new abstractions from the jsr have been moved to the
> microprofile api, but were not yet released, so the code written there will
> be of great use once the next mp release is ready...

I'd release it as it is ..... in case the new JSR is out, we might
remove it then.

To my mind there's so much change in the current version to rectify a
release.

I'm still not really able to do the release .... any other volunteer: go
ahead.

I can help a bit if there are questions concerning the homepage and
stuff like that ...

Cheers,
Phil

Re: release it!

[Anatole Tresch <at...@gmail.com>]

the jsr382 module is in the sandbox and can be deleted or just removed from
the build. Any new abstractions from the jsr have been moved to the
microprofile api, but were not yet released, so the code written there will
be of great use once the next mp release is ready...


Werner Keil <we...@gmail.com> schrieb am Di., 16. Juli 2019, 15:11:

> I'm not sure about the part that implemented JSR 182. Was that official or
> in the sandbox modules?
>
> I would deprecate those in a new release because the JSR stopped.
>
> At the moment Microprofile Config is an alternative. A Jakarta spec is
> planned but not sure when it will start.
>
> Werner
>
> Aaron Coburn <ac...@apache.org> schrieb am Di., 16. Juli 2019, 15:03:
>
> > Yes, let's definitely cut a release. +1
> >
> > Cheers,
> > Aaron
> >
> >
> >
> > On Tue, 16 Jul 2019 at 05:16, Anatole Tresch <at...@gmail.com> wrote:
> >
> > > Hi Guys
> > >
> > > is there anything that speaks against building a new release? If no, we
> > > should build one.
> > >
> > > J Anatole
> > >
> >
>

Re: release it!

[Werner Keil <we...@gmail.com>]

I'm not sure about the part that implemented JSR 182. Was that official or
in the sandbox modules?

I would deprecate those in a new release because the JSR stopped.

At the moment Microprofile Config is an alternative. A Jakarta spec is
planned but not sure when it will start.

Werner

Aaron Coburn <ac...@apache.org> schrieb am Di., 16. Juli 2019, 15:03:

> Yes, let's definitely cut a release. +1
>
> Cheers,
> Aaron
>
>
>
> On Tue, 16 Jul 2019 at 05:16, Anatole Tresch <at...@gmail.com> wrote:
>
> > Hi Guys
> >
> > is there anything that speaks against building a new release? If no, we
> > should build one.
> >
> > J Anatole
> >
>

Re: release it!

[Aaron Coburn <ac...@apache.org>]

Yes, let's definitely cut a release. +1

Cheers,
Aaron



On Tue, 16 Jul 2019 at 05:16, Anatole Tresch <at...@gmail.com> wrote:

> Hi Guys
>
> is there anything that speaks against building a new release? If no, we
> should build one.
>
> J Anatole
>