subject:"Re\: release it\!"

Re: release it!

2019-07-17 Thread Werner Keil

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  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.lieura...@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 
> > 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!

2019-07-16 Thread Anatole Tresch

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.lieura...@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 
> 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!

2019-07-16 Thread William Lieurance

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 
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!

2019-07-16 Thread P. Ottlinger

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!

2019-07-16 Thread Werner Keil

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  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!

2019-07-16 Thread P. Ottlinger

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!

2019-07-16 Thread 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...


Werner Keil  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  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  wrote:
> >
> > > Hi Guys
> > >
> > > is there anything that speaks against building a new release? If no, we
> > > should build one.
> > >
> > > J Anatole
> > >
> >
>

Re: release it!

2019-07-16 Thread Werner Keil

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  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  wrote:
>
> > Hi Guys
> >
> > is there anything that speaks against building a new release? If no, we
> > should build one.
> >
> > J Anatole
> >
>

Re: release it!

2019-07-16 Thread Aaron Coburn

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

Cheers,
Aaron



On Tue, 16 Jul 2019 at 05:16, Anatole Tresch  wrote:

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

Re: Release of Extensions

2017-07-08 Thread Oliver B. Fischer

I hope I we will be able to start the vote on the extensions tomorrow. I 
am also overhauling the relase guide for Tamaya but I am not so fast as 
I would like to be (daugther weekend).


Oliver


Am 01.07.17 um 10:54 schrieb Anatole Tresch:

would be good

Am 01.07.2017 08:49 schrieb "Oliver B. Fischer" :


Hi Anatole,

my plan was to update the release guide first, but I could to both in
parallel.

Oliver


Am 30.06.17 um 09:41 schrieb Anatole Tresch:

--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf




--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf

Re: Release of Extensions

2017-07-01 Thread Anatole Tresch

would be good

Am 01.07.2017 08:49 schrieb "Oliver B. Fischer" :

> Hi Anatole,
>
> my plan was to update the release guide first, but I could to both in
> parallel.
>
> Oliver
>
>
> Am 30.06.17 um 09:41 schrieb Anatole Tresch:
>
>> Hi Oliver/all
>>
>> what is the state regarding release of the extensions. Announcing API/Core
>> only doesnt make much sense, since the most useful functionality
>> (especially the new features) are residing in the extensions part...
>>
>> J Anatole
>>
>>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251
> M +49 178 7903538
> E o.b.fisc...@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fisc...@jabber.org
> X http://xing.to/obf
>
>

Re: Release Guide, Resolved or Closed Issues

2017-04-06 Thread P. Ottlinger

Am 07.04.2017 um 00:08 schrieb Oliver B. Fischer:
> one question about handling issues. Should we close or only resolve
> issues before releasing the target version of the issues? According to
> our release guide it is needed to resolve them before the release. But
> when should be close them?

I'd either close them once the release is out OR
after someone reviewed the stuff OR
we talked about it in the hangout.

Just my 2ct -
due to the fact that we do not have many contributors yet we could
resolve them after all of the work is done and close it after the
release is out.

n8
Phil

Re: Release Planning

2016-03-14 Thread Oliver B. Fischer


+1

Am 14.03.16 um 06:32 schrieb Anatole Tresch:

Basically all is ready. I have fixed many docs and minor things and finally
redesigned the mutable module (current discussion thread). Current last
todo is updating the mutable module docs. That I can do today during
travelling. If we dont get further disagrees on my discussion thread it
should be possible to build the release today or tomorrow and start the
release vote here.

Anatole
Am 14.03.2016 01:43 schrieb "John D. Ament" :


Any update?

On Mon, Mar 7, 2016 at 7:58 PM Anatole Tresch  wrote:


I started but ended up with some oome in maven. Tbc tomorrow...

Anatole
Am 07.03.2016 7:50 PM schrieb "P. Ottlinger" :


Hi guys,

Am 26.02.2016 um 16:56 schrieb Anatole Tresch:

I also prepared corresponding changes (and also fixes) on the site
repository. So once the release is ready I would manually update docs

and

javadocs as I did for the last release and check in the new version).

This

way we can get out with the release quickly. And the release would

not

be

delayed because of the new generated site is not yet ready).

Any suggestions or objections progressing that way?

Thanks for adding yet another feature - but I think that 0.2 can and
should be released to stay within the release schedule.

@Anatole: can you start the release?

Javadoc seems ok.

Cheers,
Phil




--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf

Re: Release Planning

2016-03-14 Thread John D. Ament

Great news! Thanks for the update.

John

On Mon, Mar 14, 2016 at 1:32 AM Anatole Tresch  wrote:

> Basically all is ready. I have fixed many docs and minor things and finally
> redesigned the mutable module (current discussion thread). Current last
> todo is updating the mutable module docs. That I can do today during
> travelling. If we dont get further disagrees on my discussion thread it
> should be possible to build the release today or tomorrow and start the
> release vote here.
>
> Anatole
> Am 14.03.2016 01:43 schrieb "John D. Ament" :
>
> > Any update?
> >
> > On Mon, Mar 7, 2016 at 7:58 PM Anatole Tresch 
> wrote:
> >
> > > I started but ended up with some oome in maven. Tbc tomorrow...
> > >
> > > Anatole
> > > Am 07.03.2016 7:50 PM schrieb "P. Ottlinger" :
> > >
> > > > Hi guys,
> > > >
> > > > Am 26.02.2016 um 16:56 schrieb Anatole Tresch:
> > > > > I also prepared corresponding changes (and also fixes) on the site
> > > > > repository. So once the release is ready I would manually update
> docs
> > > and
> > > > > javadocs as I did for the last release and check in the new
> version).
> > > > This
> > > > > way we can get out with the release quickly. And the release would
> > not
> > > be
> > > > > delayed because of the new generated site is not yet ready).
> > > > >
> > > > > Any suggestions or objections progressing that way?
> > > >
> > > > Thanks for adding yet another feature - but I think that 0.2 can and
> > > > should be released to stay within the release schedule.
> > > >
> > > > @Anatole: can you start the release?
> > > >
> > > > Javadoc seems ok.
> > > >
> > > > Cheers,
> > > > Phil
> > > >
> > > >
> > >
> >
>

Re: Release Planning

2016-03-14 Thread Romain Manni-Bucau

+1
Le 14 mars 2016 06:32, "Anatole Tresch"  a écrit :

> Basically all is ready. I have fixed many docs and minor things and finally
> redesigned the mutable module (current discussion thread). Current last
> todo is updating the mutable module docs. That I can do today during
> travelling. If we dont get further disagrees on my discussion thread it
> should be possible to build the release today or tomorrow and start the
> release vote here.
>
> Anatole
> Am 14.03.2016 01:43 schrieb "John D. Ament" :
>
> > Any update?
> >
> > On Mon, Mar 7, 2016 at 7:58 PM Anatole Tresch 
> wrote:
> >
> > > I started but ended up with some oome in maven. Tbc tomorrow...
> > >
> > > Anatole
> > > Am 07.03.2016 7:50 PM schrieb "P. Ottlinger" :
> > >
> > > > Hi guys,
> > > >
> > > > Am 26.02.2016 um 16:56 schrieb Anatole Tresch:
> > > > > I also prepared corresponding changes (and also fixes) on the site
> > > > > repository. So once the release is ready I would manually update
> docs
> > > and
> > > > > javadocs as I did for the last release and check in the new
> version).
> > > > This
> > > > > way we can get out with the release quickly. And the release would
> > not
> > > be
> > > > > delayed because of the new generated site is not yet ready).
> > > > >
> > > > > Any suggestions or objections progressing that way?
> > > >
> > > > Thanks for adding yet another feature - but I think that 0.2 can and
> > > > should be released to stay within the release schedule.
> > > >
> > > > @Anatole: can you start the release?
> > > >
> > > > Javadoc seems ok.
> > > >
> > > > Cheers,
> > > > Phil
> > > >
> > > >
> > >
> >
>

Re: Release Planning

2016-03-13 Thread Anatole Tresch

Basically all is ready. I have fixed many docs and minor things and finally
redesigned the mutable module (current discussion thread). Current last
todo is updating the mutable module docs. That I can do today during
travelling. If we dont get further disagrees on my discussion thread it
should be possible to build the release today or tomorrow and start the
release vote here.

Anatole
Am 14.03.2016 01:43 schrieb "John D. Ament" :

> Any update?
>
> On Mon, Mar 7, 2016 at 7:58 PM Anatole Tresch  wrote:
>
> > I started but ended up with some oome in maven. Tbc tomorrow...
> >
> > Anatole
> > Am 07.03.2016 7:50 PM schrieb "P. Ottlinger" :
> >
> > > Hi guys,
> > >
> > > Am 26.02.2016 um 16:56 schrieb Anatole Tresch:
> > > > I also prepared corresponding changes (and also fixes) on the site
> > > > repository. So once the release is ready I would manually update docs
> > and
> > > > javadocs as I did for the last release and check in the new version).
> > > This
> > > > way we can get out with the release quickly. And the release would
> not
> > be
> > > > delayed because of the new generated site is not yet ready).
> > > >
> > > > Any suggestions or objections progressing that way?
> > >
> > > Thanks for adding yet another feature - but I think that 0.2 can and
> > > should be released to stay within the release schedule.
> > >
> > > @Anatole: can you start the release?
> > >
> > > Javadoc seems ok.
> > >
> > > Cheers,
> > > Phil
> > >
> > >
> >
>

Re: Release Planning

2016-03-13 Thread John D. Ament

Any update?

On Mon, Mar 7, 2016 at 7:58 PM Anatole Tresch  wrote:

> I started but ended up with some oome in maven. Tbc tomorrow...
>
> Anatole
> Am 07.03.2016 7:50 PM schrieb "P. Ottlinger" :
>
> > Hi guys,
> >
> > Am 26.02.2016 um 16:56 schrieb Anatole Tresch:
> > > I also prepared corresponding changes (and also fixes) on the site
> > > repository. So once the release is ready I would manually update docs
> and
> > > javadocs as I did for the last release and check in the new version).
> > This
> > > way we can get out with the release quickly. And the release would not
> be
> > > delayed because of the new generated site is not yet ready).
> > >
> > > Any suggestions or objections progressing that way?
> >
> > Thanks for adding yet another feature - but I think that 0.2 can and
> > should be released to stay within the release schedule.
> >
> > @Anatole: can you start the release?
> >
> > Javadoc seems ok.
> >
> > Cheers,
> > Phil
> >
> >
>

Re: Release Planning

2016-03-07 Thread Anatole Tresch

I started but ended up with some oome in maven. Tbc tomorrow...

Anatole
Am 07.03.2016 7:50 PM schrieb "P. Ottlinger" :

> Hi guys,
>
> Am 26.02.2016 um 16:56 schrieb Anatole Tresch:
> > I also prepared corresponding changes (and also fixes) on the site
> > repository. So once the release is ready I would manually update docs and
> > javadocs as I did for the last release and check in the new version).
> This
> > way we can get out with the release quickly. And the release would not be
> > delayed because of the new generated site is not yet ready).
> >
> > Any suggestions or objections progressing that way?
>
> Thanks for adding yet another feature - but I think that 0.2 can and
> should be released to stay within the release schedule.
>
> @Anatole: can you start the release?
>
> Javadoc seems ok.
>
> Cheers,
> Phil
>
>

Re: Release Planning

2016-03-07 Thread P. Ottlinger

Hi guys,

Am 26.02.2016 um 16:56 schrieb Anatole Tresch:
> I also prepared corresponding changes (and also fixes) on the site
> repository. So once the release is ready I would manually update docs and
> javadocs as I did for the last release and check in the new version). This
> way we can get out with the release quickly. And the release would not be
> delayed because of the new generated site is not yet ready).
> 
> Any suggestions or objections progressing that way?

Thanks for adding yet another feature - but I think that 0.2 can and
should be released to stay within the release schedule.

@Anatole: can you start the release?

Javadoc seems ok.

Cheers,
Phil



signature.asc
Description: OpenPGP digital signature

Re: Release Staging

2015-08-04 Thread Romain Manni-Bucau

You should stage on apache then it will get sync-ed on central no?
Le 4 août 2015 12:34, Anatole Tresch atsti...@gmail.com a écrit :

 Hi John/all

 I was successful in uploading the release to sonatype for staging.
 Unfortunately I (UID: anatole) was not able to access Nexus. I commented on
 the INFRA ticket on this.
 Can you check, if you have access to https://oss.sonatype.org ?

 Or I am doing something wrong here? The process of staging basically is
 nothing new, since I did similar things with the money JSR already, so once
 I would be able to login we could continue with the release/voting
 process...

 Anatole



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

Re: Release Staging

2015-08-04 Thread John D. Ament

Sorry, Close the Repo not Promote

On Tue, Aug 4, 2015 at 6:47 AM John D. Ament johndam...@apache.org wrote:

 Hi Anatole,

 So you're not going to push to oss.sonatype.org at this point (we need to
 vote on the artifacts before the release goes out the door)

 If you login here https://repository.apache.org/#stagingRepositories
 using your regulard apache username/password, you should see the staging
 repo you created.  If you click on promote you should get a URL generated
 that is accessible to other and have the release artifacts we're voting on.

 The URL should end up being
 https://repository.apache.org/content/repositories/orgapachetamaya-1001/

 The -src.zip/-src.tar.gz are what we vote on.

 John


 On Tue, Aug 4, 2015 at 6:34 AM Anatole Tresch atsti...@gmail.com wrote:

 Hi John/all

 I was successful in uploading the release to sonatype for staging.
 Unfortunately I (UID: anatole) was not able to access Nexus. I commented
 on
 the INFRA ticket on this.
 Can you check, if you have access to https://oss.sonatype.org ?

 Or I am doing something wrong here? The process of staging basically is
 nothing new, since I did similar things with the money JSR already, so
 once
 I would be able to login we could continue with the release/voting
 process...

 Anatole



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

Re: Release Staging

2015-08-04 Thread John D. Ament

BTW, since we're using maven for the release, all of the steps from
deltaspike apply to us.

http://deltaspike.apache.org/steps_for_a_release.html

So we can reuse that info here.



On Tue, Aug 4, 2015 at 6:55 AM John D. Ament johndam...@apache.org wrote:

 Sorry, Close the Repo not Promote


 On Tue, Aug 4, 2015 at 6:47 AM John D. Ament johndam...@apache.org
 wrote:

 Hi Anatole,

 So you're not going to push to oss.sonatype.org at this point (we need
 to vote on the artifacts before the release goes out the door)

 If you login here https://repository.apache.org/#stagingRepositories
 using your regulard apache username/password, you should see the staging
 repo you created.  If you click on promote you should get a URL generated
 that is accessible to other and have the release artifacts we're voting on.

 The URL should end up being
 https://repository.apache.org/content/repositories/orgapachetamaya-1001/

 The -src.zip/-src.tar.gz are what we vote on.

 John


 On Tue, Aug 4, 2015 at 6:34 AM Anatole Tresch atsti...@gmail.com wrote:

 Hi John/all

 I was successful in uploading the release to sonatype for staging.
 Unfortunately I (UID: anatole) was not able to access Nexus. I commented
 on
 the INFRA ticket on this.
 Can you check, if you have access to https://oss.sonatype.org ?

 Or I am doing something wrong here? The process of staging basically is
 nothing new, since I did similar things with the money JSR already, so
 once
 I would be able to login we could continue with the release/voting
 process...

 Anatole



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

Re: Release Staging

2015-08-04 Thread John D. Ament

Agreed, it can be confusing.  Looks like the only step left is closing the
repo.

John

On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch atsti...@gmail.com wrote:

 I just did what is described here:
 http://www.apache.org/dev/publishing-maven-artifacts.html
 http://www.apache.org/dev/publishing-maven-artifacts.html

 or, more especially here:

 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

 Then:
 http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

 And finally:

 http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository

 So *section 4* here is completely misleading IMO:
 4 - STAGE THE RELEASE FOR A VOTE¶
 
 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
 

 mvn release:perform

 The release will automatically be inserted into a temporary staging
 repository for you. See the Nexus staging documentation
 http://www.sonatype.com/books/nexus-book/reference/staging.html for full
 details.

 Now you must close the staging repository to indicate to Nexus that the
 build is done and to make the artifacts available. Follow the steps
 inClosing
 the Staged Repository
 http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage to
 close your new repository, *this will allow your community to VOTE on the
 staged atrifacts*.

 But fair enough, now things look clearer again ;)

 Thanks
 Anatole


 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

  You should stage on apache then it will get sync-ed on central no?
  Le 4 août 2015 12:34, Anatole Tresch atsti...@gmail.com a écrit :
 
   Hi John/all
  
   I was successful in uploading the release to sonatype for staging.
   Unfortunately I (UID: anatole) was not able to access Nexus. I
 commented
  on
   the INFRA ticket on this.
   Can you check, if you have access to https://oss.sonatype.org ?
  
   Or I am doing something wrong here? The process of staging basically is
   nothing new, since I did similar things with the money JSR already, so
  once
   I would be able to login we could continue with the release/voting
   process...
  
   Anatole
  
  
  
   --
   *Anatole Tresch*
   Java Engineer  Architect, JSR Spec Lead
   Glärnischweg 10
   CH - 8620 Wetzikon
  
   *Switzerland, Europe Zurich, GMT+1*
   *Twitter:  @atsticks*
   *Blogs: **http://javaremarkables.blogspot.ch/
   http://javaremarkables.blogspot.ch/*
  
   *Google: atsticksMobile  +41-76 344 62 79*
  
 



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

Re: Release Staging

2015-08-04 Thread John D. Ament

Yes, go pick your children. :-)

push is set to false in our release plugin config, as a result the created
release is not in master yet (a good thing!). We should only push it to
master once its been voted on by both PPMC and IPMC. But we can push a
release branch to do the voting on. As a result, the release is only on
your computer.

John

On Tue, Aug 4, 2015 at 8:10 AM Anatole Tresch atsti...@gmail.com wrote:

Yep, but as of now I have to take up my children, so it has to wait for a
couple of hours, unless somebody else jumps in ;) the 0.1-incubating tag
should be there on master (created by the release plugin)...

Anatole

2015-08-04 14:05 GMT+02:00 John D. Ament johndam...@apache.org:

Also, can you push the release branch up to the repo (not as master, but
something like v0.1-incubating or equivalent) ?
This way we have a tag and git commit to vote on.

John

On Tue, Aug 4, 2015 at 8:04 AM John D. Ament johndam...@apache.org
wrote:

I noticed that as well.

I don't think that'll block the release. We can work w/ infra in
parallel
to figure out the toolchain setup (probably should have done that
before
we
introduced toolchain requirements, but lesson learned).

John

On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch atsti...@gmail.com
wrote:

What I also see is that we still have that toolchain issue with the
1.7
toolchain on Jenkins... so the current build breaks on Jenkins ;(

2015-08-04 13:59 GMT+02:00 John D. Ament johndam...@apache.org:

Agreed, it can be confusing. Looks like the only step left is
closing
the
repo.

John

On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch atsti...@gmail.com
wrote:

I just did what is described here:
http://www.apache.org/dev/publishing-maven-artifacts.html
http://www.apache.org/dev/publishing-maven-artifacts.html

or, more especially here:

http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

Then:

http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

And finally:

http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository

So *section 4* here is completely misleading IMO:
4 - STAGE THE RELEASE FOR A VOTE¶

http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

mvn release:perform

The release will automatically be inserted into a temporary
staging
repository for you. See the Nexus staging documentation
http://www.sonatype.com/books/nexus-book/reference/staging.html
for
full
details.

Now you must close the staging repository to indicate to Nexus
that
the
build is done and to make the artifacts available. Follow the
steps
inClosing
the Staged Repository

http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

to
close your new repository, *this will allow your community to VOTE
on
the
staged atrifacts*.

But fair enough, now things look clearer again ;)

Thanks
Anatole

2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau
rmannibu...@gmail.com
:

You should stage on apache then it will get sync-ed on central
no?
Le 4 août 2015 12:34, Anatole Tresch atsti...@gmail.com a
écrit :

Hi John/all

I was successful in uploading the release to sonatype for
staging.
Unfortunately I (UID: anatole) was not able to access Nexus. I
commented
on
the INFRA ticket on this.
Can you check, if you have access to https://oss.sonatype.org
?

Or I am doing something wrong here? The process of staging
basically
is
nothing new, since I did similar things with the money JSR
already,
so
once
I would be able to login we could continue with the
release/voting
process...

Anatole

--
*Anatole Tresch*
Java Engineer Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon

*Switzerland, Europe Zurich, GMT+1*
*Twitter: @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/*

*Google: atsticksMobile +41-76 344 62 79*

--
*Anatole Tresch*
Java Engineer Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon

*Switzerland, Europe Zurich, GMT+1*
*Twitter: @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/*

*Google: atsticksMobile +41-76 344 62 79*

--
*Anatole Tresch*
Java Engineer Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon

*Switzerland,

Re: Release Staging

2015-08-04 Thread John D. Ament

Also, can you push the release branch up to the repo (not as master, but
something like v0.1-incubating or equivalent) ?
This way we have a tag and git commit to vote on.

John

On Tue, Aug 4, 2015 at 8:04 AM John D. Ament johndam...@apache.org wrote:

 I noticed that as well.

 I don't think that'll block the release.  We can work w/ infra in parallel
 to figure out the toolchain setup (probably should have done that before we
 introduced toolchain requirements, but lesson learned).

 John

 On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch atsti...@gmail.com wrote:

 What I also see is that we still have that toolchain issue with the 1.7
 toolchain on Jenkins... so the current build breaks on Jenkins ;(


 2015-08-04 13:59 GMT+02:00 John D. Ament johndam...@apache.org:

  Agreed, it can be confusing.  Looks like the only step left is closing
 the
  repo.
 
  John
 
  On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch atsti...@gmail.com
 wrote:
 
   I just did what is described here:
   http://www.apache.org/dev/publishing-maven-artifacts.html
   http://www.apache.org/dev/publishing-maven-artifacts.html
  
   or, more especially here:
  
  
 
 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
  
   Then:
   http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
  
   And finally:
  
  
 
 http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
  
   So *section 4* here is completely misleading IMO:
   4 - STAGE THE RELEASE FOR A VOTE¶
   
  
 
 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
   
  
   mvn release:perform
  
   The release will automatically be inserted into a temporary staging
   repository for you. See the Nexus staging documentation
   http://www.sonatype.com/books/nexus-book/reference/staging.html for
  full
   details.
  
   Now you must close the staging repository to indicate to Nexus that
 the
   build is done and to make the artifacts available. Follow the steps
   inClosing
   the Staged Repository
   
 http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
  to
   close your new repository, *this will allow your community to VOTE on
 the
   staged atrifacts*.
  
   But fair enough, now things look clearer again ;)
  
   Thanks
   Anatole
  
  
   2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com
 :
  
You should stage on apache then it will get sync-ed on central no?
Le 4 août 2015 12:34, Anatole Tresch atsti...@gmail.com a
 écrit :
   
 Hi John/all

 I was successful in uploading the release to sonatype for staging.
 Unfortunately I (UID: anatole) was not able to access Nexus. I
   commented
on
 the INFRA ticket on this.
 Can you check, if you have access to https://oss.sonatype.org ?

 Or I am doing something wrong here? The process of staging
 basically
  is
 nothing new, since I did similar things with the money JSR
 already,
  so
once
 I would be able to login we could continue with the release/voting
 process...

 Anatole



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

   
  
  
  
   --
   *Anatole Tresch*
   Java Engineer  Architect, JSR Spec Lead
   Glärnischweg 10
   CH - 8620 Wetzikon
  
   *Switzerland, Europe Zurich, GMT+1*
   *Twitter:  @atsticks*
   *Blogs: **http://javaremarkables.blogspot.ch/
   http://javaremarkables.blogspot.ch/*
  
   *Google: atsticksMobile  +41-76 344 62 79*
  
 



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

Re: Release Staging

2015-08-04 Thread Anatole Tresch

Yep, but as of now I have to take up my children, so it has to wait for a
couple of hours, unless somebody else jumps in ;) the 0.1-incubating tag
should be there on master (created by the release plugin)...

Anatole

2015-08-04 14:05 GMT+02:00 John D. Ament johndam...@apache.org:

 Also, can you push the release branch up to the repo (not as master, but
 something like v0.1-incubating or equivalent) ?
 This way we have a tag and git commit to vote on.

 John

 On Tue, Aug 4, 2015 at 8:04 AM John D. Ament johndam...@apache.org
 wrote:

  I noticed that as well.
 
  I don't think that'll block the release.  We can work w/ infra in
 parallel
  to figure out the toolchain setup (probably should have done that before
 we
  introduced toolchain requirements, but lesson learned).
 
  John
 
  On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch atsti...@gmail.com
 wrote:
 
  What I also see is that we still have that toolchain issue with the 1.7
  toolchain on Jenkins... so the current build breaks on Jenkins ;(
 
 
  2015-08-04 13:59 GMT+02:00 John D. Ament johndam...@apache.org:
 
   Agreed, it can be confusing.  Looks like the only step left is closing
  the
   repo.
  
   John
  
   On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch atsti...@gmail.com
  wrote:
  
I just did what is described here:
http://www.apache.org/dev/publishing-maven-artifacts.html
http://www.apache.org/dev/publishing-maven-artifacts.html
   
or, more especially here:
   
   
  
 
 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
   
Then:
   
 http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
   
And finally:
   
   
  
 
 http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
   
So *section 4* here is completely misleading IMO:
4 - STAGE THE RELEASE FOR A VOTE¶

   
  
 
 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

   
mvn release:perform
   
The release will automatically be inserted into a temporary staging
repository for you. See the Nexus staging documentation
http://www.sonatype.com/books/nexus-book/reference/staging.html
 for
   full
details.
   
Now you must close the staging repository to indicate to Nexus that
  the
build is done and to make the artifacts available. Follow the steps
inClosing
the Staged Repository

  http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
   to
close your new repository, *this will allow your community to VOTE
 on
  the
staged atrifacts*.
   
But fair enough, now things look clearer again ;)
   
Thanks
Anatole
   
   
2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau 
 rmannibu...@gmail.com
  :
   
 You should stage on apache then it will get sync-ed on central no?
 Le 4 août 2015 12:34, Anatole Tresch atsti...@gmail.com a
  écrit :

  Hi John/all
 
  I was successful in uploading the release to sonatype for
 staging.
  Unfortunately I (UID: anatole) was not able to access Nexus. I
commented
 on
  the INFRA ticket on this.
  Can you check, if you have access to https://oss.sonatype.org ?
 
  Or I am doing something wrong here? The process of staging
  basically
   is
  nothing new, since I did similar things with the money JSR
  already,
   so
 once
  I would be able to login we could continue with the
 release/voting
  process...
 
  Anatole
 
 
 
  --
  *Anatole Tresch*
  Java Engineer  Architect, JSR Spec Lead
  Glärnischweg 10
  CH - 8620 Wetzikon
 
  *Switzerland, Europe Zurich, GMT+1*
  *Twitter:  @atsticks*
  *Blogs: **http://javaremarkables.blogspot.ch/
  http://javaremarkables.blogspot.ch/*
 
  *Google: atsticksMobile  +41-76 344 62 79*
 

   
   
   
--
*Anatole Tresch*
Java Engineer  Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon
   
*Switzerland, Europe Zurich, GMT+1*
*Twitter:  @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/*
   
*Google: atsticksMobile  +41-76 344 62 79*
   
  
 
 
 
  --
  *Anatole Tresch*
  Java Engineer  Architect, JSR Spec Lead
  Glärnischweg 10
  CH - 8620 Wetzikon
 
  *Switzerland, Europe Zurich, GMT+1*
  *Twitter:  @atsticks*
  *Blogs: **http://javaremarkables.blogspot.ch/
  http://javaremarkables.blogspot.ch/*
 
  *Google: atsticksMobile  +41-76 344 62 79*
 
 




-- 
*Anatole Tresch*
Java Engineer  Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon

*Switzerland, Europe Zurich, GMT+1*
*Twitter:  @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/*

*Google: atsticksMobile  +41-76 344 62 79*

Re: Release Staging

2015-08-04 Thread Anatole Tresch

I just did what is described here:
http://www.apache.org/dev/publishing-maven-artifacts.html
http://www.apache.org/dev/publishing-maven-artifacts.html

or, more especially here:
http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

Then: http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

And finally:
http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository

So *section 4* here is completely misleading IMO:
4 - STAGE THE RELEASE FOR A VOTE¶
http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

mvn release:perform

The release will automatically be inserted into a temporary staging
repository for you. See the Nexus staging documentation
http://www.sonatype.com/books/nexus-book/reference/staging.html for full
details.

Now you must close the staging repository to indicate to Nexus that the
build is done and to make the artifacts available. Follow the steps inClosing
the Staged Repository
http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage to
close your new repository, *this will allow your community to VOTE on the
staged atrifacts*.

But fair enough, now things look clearer again ;)

Thanks
Anatole


2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

 You should stage on apache then it will get sync-ed on central no?
 Le 4 août 2015 12:34, Anatole Tresch atsti...@gmail.com a écrit :

  Hi John/all
 
  I was successful in uploading the release to sonatype for staging.
  Unfortunately I (UID: anatole) was not able to access Nexus. I commented
 on
  the INFRA ticket on this.
  Can you check, if you have access to https://oss.sonatype.org ?
 
  Or I am doing something wrong here? The process of staging basically is
  nothing new, since I did similar things with the money JSR already, so
 once
  I would be able to login we could continue with the release/voting
  process...
 
  Anatole
 
 
 
  --
  *Anatole Tresch*
  Java Engineer  Architect, JSR Spec Lead
  Glärnischweg 10
  CH - 8620 Wetzikon
 
  *Switzerland, Europe Zurich, GMT+1*
  *Twitter:  @atsticks*
  *Blogs: **http://javaremarkables.blogspot.ch/
  http://javaremarkables.blogspot.ch/*
 
  *Google: atsticksMobile  +41-76 344 62 79*
 




-- 
*Anatole Tresch*
Java Engineer  Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon

*Switzerland, Europe Zurich, GMT+1*
*Twitter:  @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/*

*Google: atsticksMobile  +41-76 344 62 79*

Re: Release Staging

2015-08-04 Thread John D. Ament

Yay! It closed!

https://repository.apache.org/content/repositories/orgapachetamaya-1001/

We now have a staged release that can be voted upon.

John

On Tue, Aug 4, 2015 at 7:59 AM John D. Ament johndam...@apache.org wrote:

 Agreed, it can be confusing.  Looks like the only step left is closing the
 repo.

 John


 On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch atsti...@gmail.com wrote:

 I just did what is described here:
 http://www.apache.org/dev/publishing-maven-artifacts.html
 http://www.apache.org/dev/publishing-maven-artifacts.html

 or, more especially here:

 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

 Then:
 http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

 And finally:

 http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository

 So *section 4* here is completely misleading IMO:
 4 - STAGE THE RELEASE FOR A VOTE¶
 
 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
 

 mvn release:perform

 The release will automatically be inserted into a temporary staging
 repository for you. See the Nexus staging documentation
 http://www.sonatype.com/books/nexus-book/reference/staging.html for
 full
 details.

 Now you must close the staging repository to indicate to Nexus that the
 build is done and to make the artifacts available. Follow the steps
 inClosing
 the Staged Repository
 http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
 to
 close your new repository, *this will allow your community to VOTE on the
 staged atrifacts*.

 But fair enough, now things look clearer again ;)

 Thanks
 Anatole


 2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

  You should stage on apache then it will get sync-ed on central no?
  Le 4 août 2015 12:34, Anatole Tresch atsti...@gmail.com a écrit :
 
   Hi John/all
  
   I was successful in uploading the release to sonatype for staging.
   Unfortunately I (UID: anatole) was not able to access Nexus. I
 commented
  on
   the INFRA ticket on this.
   Can you check, if you have access to https://oss.sonatype.org ?
  
   Or I am doing something wrong here? The process of staging basically
 is
   nothing new, since I did similar things with the money JSR already, so
  once
   I would be able to login we could continue with the release/voting
   process...
  
   Anatole
  
  
  
   --
   *Anatole Tresch*
   Java Engineer  Architect, JSR Spec Lead
   Glärnischweg 10
   CH - 8620 Wetzikon
  
   *Switzerland, Europe Zurich, GMT+1*
   *Twitter:  @atsticks*
   *Blogs: **http://javaremarkables.blogspot.ch/
   http://javaremarkables.blogspot.ch/*
  
   *Google: atsticksMobile  +41-76 344 62 79*
  
 



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

Re: Release Staging

2015-08-04 Thread Anatole Tresch

What I also see is that we still have that toolchain issue with the 1.7
toolchain on Jenkins... so the current build breaks on Jenkins ;(


2015-08-04 13:59 GMT+02:00 John D. Ament johndam...@apache.org:

 Agreed, it can be confusing.  Looks like the only step left is closing the
 repo.

 John

 On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch atsti...@gmail.com wrote:

  I just did what is described here:
  http://www.apache.org/dev/publishing-maven-artifacts.html
  http://www.apache.org/dev/publishing-maven-artifacts.html
 
  or, more especially here:
 
 
 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
 
  Then:
  http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
 
  And finally:
 
 
 http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository
 
  So *section 4* here is completely misleading IMO:
  4 - STAGE THE RELEASE FOR A VOTE¶
  
 
 http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote
  
 
  mvn release:perform
 
  The release will automatically be inserted into a temporary staging
  repository for you. See the Nexus staging documentation
  http://www.sonatype.com/books/nexus-book/reference/staging.html for
 full
  details.
 
  Now you must close the staging repository to indicate to Nexus that the
  build is done and to make the artifacts available. Follow the steps
  inClosing
  the Staged Repository
  http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage
 to
  close your new repository, *this will allow your community to VOTE on the
  staged atrifacts*.
 
  But fair enough, now things look clearer again ;)
 
  Thanks
  Anatole
 
 
  2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:
 
   You should stage on apache then it will get sync-ed on central no?
   Le 4 août 2015 12:34, Anatole Tresch atsti...@gmail.com a écrit :
  
Hi John/all
   
I was successful in uploading the release to sonatype for staging.
Unfortunately I (UID: anatole) was not able to access Nexus. I
  commented
   on
the INFRA ticket on this.
Can you check, if you have access to https://oss.sonatype.org ?
   
Or I am doing something wrong here? The process of staging basically
 is
nothing new, since I did similar things with the money JSR already,
 so
   once
I would be able to login we could continue with the release/voting
process...
   
Anatole
   
   
   
--
*Anatole Tresch*
Java Engineer  Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon
   
*Switzerland, Europe Zurich, GMT+1*
*Twitter:  @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/*
   
*Google: atsticksMobile  +41-76 344 62 79*
   
  
 
 
 
  --
  *Anatole Tresch*
  Java Engineer  Architect, JSR Spec Lead
  Glärnischweg 10
  CH - 8620 Wetzikon
 
  *Switzerland, Europe Zurich, GMT+1*
  *Twitter:  @atsticks*
  *Blogs: **http://javaremarkables.blogspot.ch/
  http://javaremarkables.blogspot.ch/*
 
  *Google: atsticksMobile  +41-76 344 62 79*
 




-- 
*Anatole Tresch*
Java Engineer  Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon

*Switzerland, Europe Zurich, GMT+1*
*Twitter:  @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/*

*Google: atsticksMobile  +41-76 344 62 79*

Re: Release Staging

2015-08-04 Thread Anatole Tresch

Now the HEAD/master is back to 0.1-incubating-SNAPSHOT again.

2015-08-04 23:04 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:

From my experience release-plugin is fine if all steps are successful
otherwise you get issues like the one you speak about. jgitflow plugin is
nicer in general - speaking from experience - but impose so branches
structures which doesnt fit apache so I guess we dont have the choice yet
but we can get in touch with maven developpers - somes are not that far
AFAIK ;) - to enhance it.

Using a 3rd party repo - ie a github repo of a *committer* - is ok since
then the branch is pushed upstream in the workflow.

2015-08-04 22:57 GMT+02:00 Anatole Tresch atsti...@gmail.com:

Hi John

not sure, if I got all correctly... The Deltaspike manual describes
pushing
the branch to some thrid party repo, which I think is not a good
solution,
it should be manageable within Apache entirely IMO. Currently the release
branch, after having some troubles with my tooling here, is here:

https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;a=tree;h=refs/heads/0.1-incubating;hb=refs/heads/0.1-incubating

Nevertheless the master also shows already 0.2-SNAPSHOT now ;(
I tried to fix that but currently git server seems to be hanging... ;(

Unfortunately I have now again to leave. IMO using the release plugin did
not really made things easier. It does too many things in parallel,
where I
am used to have more detailed control on it. But others may have other
opinions.

Best,
Anatole

2015-08-04 14:19 GMT+02:00 John D. Ament john.d.am...@gmail.com:

Yes, go pick your children. :-)

push is set to false in our release plugin config, as a result the
created
release is not in master yet (a good thing!). We should only push it
to
master once its been voted on by both PPMC and IPMC. But we can push a
release branch to do the voting on. As a result, the release is only
on
your computer.

John

On Tue, Aug 4, 2015 at 8:10 AM Anatole Tresch atsti...@gmail.com
wrote:

Yep, but as of now I have to take up my children, so it has to wait
for a
couple of hours, unless somebody else jumps in ;) the 0.1-incubating
tag
should be there on master (created by the release plugin)...

Anatole

2015-08-04 14:05 GMT+02:00 John D. Ament johndam...@apache.org:

Also, can you push the release branch up to the repo (not as
master,
but
something like v0.1-incubating or equivalent) ?
This way we have a tag and git commit to vote on.

John

On Tue, Aug 4, 2015 at 8:04 AM John D. Ament
johndam...@apache.org
wrote:

I noticed that as well.

John

On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch
atsti...@gmail.com
wrote:

What I also see is that we still have that toolchain issue with
the
1.7
toolchain on Jenkins... so the current build breaks on Jenkins
;(

2015-08-04 13:59 GMT+02:00 John D. Ament johndam...@apache.org
:

Agreed, it can be confusing. Looks like the only step left is
closing
the
repo.

John

On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch
atsti...@gmail.com

wrote:

I just did what is described here:
http://www.apache.org/dev/publishing-maven-artifacts.html
http://www.apache.org/dev/publishing-maven-artifacts.html

or, more especially here:

http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

Then:

http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

And finally:

http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository

So *section 4* here is completely misleading IMO:
4 - STAGE THE RELEASE FOR A VOTE¶

http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

mvn release:perform

The release will automatically be inserted into a temporary
staging
repository for you. See the Nexus staging documentation

http://www.sonatype.com/books/nexus-book/reference/staging.html
for
full
details.

Now you must close the staging repository to indicate to
Nexus
that
the
build is done and to make the artifacts available. Follow
the
steps
inClosing
the Staged Repository

Re: Release Staging

2015-08-04 Thread Anatole Tresch

Hi John

not sure, if I got all correctly... The Deltaspike manual describes pushing
the branch to some thrid party repo, which I think is not a good solution,
it should be manageable within Apache entirely IMO. Currently the release
branch, after having some troubles with my tooling here, is here:

https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;a=tree;h=refs/heads/0.1-incubating;hb=refs/heads/0.1-incubating

Nevertheless the master also shows already 0.2-SNAPSHOT now ;(
I tried to fix that but currently git server seems to be hanging... ;(

Unfortunately I have now again to leave. IMO using the release plugin did
not really made things easier. It does too many things in parallel, where I
am used to have more detailed control on it. But others may have other
opinions.

Best,
Anatole

2015-08-04 14:19 GMT+02:00 John D. Ament john.d.am...@gmail.com:

Yes, go pick your children. :-)

John

On Tue, Aug 4, 2015 at 8:10 AM Anatole Tresch atsti...@gmail.com wrote:

Anatole

2015-08-04 14:05 GMT+02:00 John D. Ament johndam...@apache.org:

Also, can you push the release branch up to the repo (not as master,
but
something like v0.1-incubating or equivalent) ?
This way we have a tag and git commit to vote on.

John

On Tue, Aug 4, 2015 at 8:04 AM John D. Ament johndam...@apache.org
wrote:

I noticed that as well.

John

On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch atsti...@gmail.com
wrote:

What I also see is that we still have that toolchain issue with the
1.7
toolchain on Jenkins... so the current build breaks on Jenkins ;(

2015-08-04 13:59 GMT+02:00 John D. Ament johndam...@apache.org:

Agreed, it can be confusing. Looks like the only step left is
closing
the
repo.

John

On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch atsti...@gmail.com

wrote:

I just did what is described here:
http://www.apache.org/dev/publishing-maven-artifacts.html
http://www.apache.org/dev/publishing-maven-artifacts.html

or, more especially here:

http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

Then:

http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

And finally:

http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository

So *section 4* here is completely misleading IMO:
4 - STAGE THE RELEASE FOR A VOTE¶

http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

mvn release:perform

The release will automatically be inserted into a temporary
staging
repository for you. See the Nexus staging documentation

http://www.sonatype.com/books/nexus-book/reference/staging.html
for
full
details.

Now you must close the staging repository to indicate to Nexus
that
the
build is done and to make the artifacts available. Follow the
steps
inClosing
the Staged Repository

http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

to
close your new repository, *this will allow your community to
VOTE
on
the
staged atrifacts*.

But fair enough, now things look clearer again ;)

Thanks
Anatole

2015-08-04 12:35 GMT+02:00 Romain Manni-Bucau
rmannibu...@gmail.com
:

You should stage on apache then it will get sync-ed on central
no?
Le 4 août 2015 12:34, Anatole Tresch atsti...@gmail.com a
écrit :

Hi John/all

I was successful in uploading the release to sonatype for
staging.
Unfortunately I (UID: anatole) was not able to access
Nexus. I
commented
on
the INFRA ticket on this.
Can you check, if you have access to
https://oss.sonatype.org
?

Or I am doing something wrong here? The process of staging
basically
is
nothing new, since I did similar things with the money JSR

Re: Release Staging

2015-08-04 Thread Romain Manni-Bucau

Using a 3rd party repo - ie a github repo of a *committer* - is ok since
then the branch is pushed upstream in the workflow.

2015-08-04 22:57 GMT+02:00 Anatole Tresch atsti...@gmail.com:

Hi John

not sure, if I got all correctly... The Deltaspike manual describes pushing
the branch to some thrid party repo, which I think is not a good solution,
it should be manageable within Apache entirely IMO. Currently the release
branch, after having some troubles with my tooling here, is here:

https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya.git;a=tree;h=refs/heads/0.1-incubating;hb=refs/heads/0.1-incubating

Nevertheless the master also shows already 0.2-SNAPSHOT now ;(
I tried to fix that but currently git server seems to be hanging... ;(

Unfortunately I have now again to leave. IMO using the release plugin did
not really made things easier. It does too many things in parallel, where I
am used to have more detailed control on it. But others may have other
opinions.

Best,
Anatole

2015-08-04 14:19 GMT+02:00 John D. Ament john.d.am...@gmail.com:

Yes, go pick your children. :-)

push is set to false in our release plugin config, as a result the
created
release is not in master yet (a good thing!). We should only push it to
master once its been voted on by both PPMC and IPMC. But we can push a
release branch to do the voting on. As a result, the release is only on
your computer.

John

On Tue, Aug 4, 2015 at 8:10 AM Anatole Tresch atsti...@gmail.com
wrote:

Yep, but as of now I have to take up my children, so it has to wait
for a
couple of hours, unless somebody else jumps in ;) the 0.1-incubating
tag
should be there on master (created by the release plugin)...

Anatole

2015-08-04 14:05 GMT+02:00 John D. Ament johndam...@apache.org:

Also, can you push the release branch up to the repo (not as master,
but
something like v0.1-incubating or equivalent) ?
This way we have a tag and git commit to vote on.

John

On Tue, Aug 4, 2015 at 8:04 AM John D. Ament johndam...@apache.org
wrote:

I noticed that as well.

John

On Tue, Aug 4, 2015 at 8:02 AM Anatole Tresch atsti...@gmail.com
wrote:

What I also see is that we still have that toolchain issue with
the
1.7
toolchain on Jenkins... so the current build breaks on Jenkins ;(

2015-08-04 13:59 GMT+02:00 John D. Ament johndam...@apache.org:

Agreed, it can be confusing. Looks like the only step left is
closing
the
repo.

John

On Tue, Aug 4, 2015 at 7:45 AM Anatole Tresch
atsti...@gmail.com

wrote:

I just did what is described here:
http://www.apache.org/dev/publishing-maven-artifacts.html
http://www.apache.org/dev/publishing-maven-artifacts.html

or, more especially here:

http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

Then:

http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

And finally:

http://central.sonatype.org/pages/releasing-the-deployment.html#locate-and-examine-your-staging-repository

So *section 4* here is completely misleading IMO:
4 - STAGE THE RELEASE FOR A VOTE¶

http://www.apache.org/dev/publishing-maven-artifacts.html#stage-release-vote

mvn release:perform

The release will automatically be inserted into a temporary
staging
repository for you. See the Nexus staging documentation

http://www.sonatype.com/books/nexus-book/reference/staging.html
for
full
details.

Now you must close the staging repository to indicate to Nexus
that
the
build is done and to make the artifacts available. Follow the
steps
inClosing
the Staged Repository

http://www.apache.org/dev/publishing-maven-artifacts.html#close-stage

to
close your new repository, *this will allow your community to
VOTE
on
the
staged atrifacts*.

But fair enough, now things look clearer again ;)

Thanks
Anatole

Re: Release Preparation

2015-08-01 Thread John D. Ament

Sounds good to me.  If you do createa  dry run, let me know and I can run
through it as well, hopefully identify stuff that may need to get fixed.

I will say this month is our reporting cycle again.  I'm concerned with
community growth, e.g. its mostly you and Oliver.  Last report I think we
were talking about a release and 3 months later, no release.

John

On Sat, Aug 1, 2015 at 3:30 PM Anatole Tresch atsti...@gmail.com wrote:

 Dear All

 I continued working on the release preparation as started By Oliver. I
 tested successfully release:prepare and also opened the corresponding nexus
 group with Infrastructure. Before effectively preparing the release for the
 release vote, I will further check for missing documentation, todos and
 errors and also as of now the metamodels extension module is empty (I
 implemented it once, but something went wrong, so I am currently readding
 it as part of the experimental branch).

 Nevertheless I look forward that we will be able to vote for our
 0.1-incubating release soon, so being able to release it before JavaOne and
 ApacheCon Europe ;)

 Feel free to further have a look at the current code, especially the TODOs
 still present at some locations.

 Cheers,
 Anatole


 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

Re: Release Preparation

2015-08-01 Thread John D. Ament

Anatole,

Yes, getting the first release out will help with community interest, now
its something to play with.

To be honest, unless there's something critical that needs to be in 0.1
that's not there, I'd strongly like to push you to move on the release.  We
can always circle back with more releases to fix things and make it better
(once we have the release process in place, it becomes super easy).

From my point of view, the release contents look good.  I'm going to do a
deeper dive tonight to make sure nothing sticks out.  I do want to update
the website to include how to build, since its not 100% clear (I forgot
about the toolchains.xml requirement).  Let me know your thoughts on moving
forward with the current codebase as 0.1.

John

On Sat, Aug 1, 2015 at 7:40 PM Anatole Tresch atsti...@gmail.com wrote:

 Hi John/all

 I share your concerns. Therefore I think getting out a first release is
 very important. With that it's much easier to get people involved (at least
 that is my hope). Also I will present it at ApacheCon Europe and I as well
 as Werner Keil also are proposing it at several conferences. And I am sure
 the first release will get widely known quickly, once I will blog on it (I
 just look at the readers count on my EE config blog). In Germany I have
 also an series of articles about configuration, also well perceived on
 JAXenter. The next 2 articles are now focusing on Tamaya especially. If all
 that will not be enough to grow our community, honestly we must talk about
 plan B ...

 Cheers,
 Anatole

 BTW: I did the normal
 *mvn release:prepare -DdryRun=true \*
 *-DautoVersionSubmodules=true*
 starting on the project root level. Of course, I added a few things to
 settings.xml, but nothing special.

 2015-08-01 22:55 GMT+02:00 John D. Ament johndam...@apache.org:

  Sounds good to me.  If you do createa  dry run, let me know and I can run
  through it as well, hopefully identify stuff that may need to get fixed.
 
  I will say this month is our reporting cycle again.  I'm concerned with
  community growth, e.g. its mostly you and Oliver.  Last report I think we
  were talking about a release and 3 months later, no release.
 
  John
 
  On Sat, Aug 1, 2015 at 3:30 PM Anatole Tresch atsti...@gmail.com
 wrote:
 
   Dear All
  
   I continued working on the release preparation as started By Oliver. I
   tested successfully release:prepare and also opened the corresponding
  nexus
   group with Infrastructure. Before effectively preparing the release for
  the
   release vote, I will further check for missing documentation, todos and
   errors and also as of now the metamodels extension module is empty (I
   implemented it once, but something went wrong, so I am currently
 readding
   it as part of the experimental branch).
  
   Nevertheless I look forward that we will be able to vote for our
   0.1-incubating release soon, so being able to release it before JavaOne
  and
   ApacheCon Europe ;)
  
   Feel free to further have a look at the current code, especially the
  TODOs
   still present at some locations.
  
   Cheers,
   Anatole
  
  
   --
   *Anatole Tresch*
   Java Engineer  Architect, JSR Spec Lead
   Glärnischweg 10
   CH - 8620 Wetzikon
  
   *Switzerland, Europe Zurich, GMT+1*
   *Twitter:  @atsticks*
   *Blogs: **http://javaremarkables.blogspot.ch/
   http://javaremarkables.blogspot.ch/*
  
   *Google: atsticksMobile  +41-76 344 62 79*
  
 



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

Re: Release Preparation

2015-08-01 Thread John D. Ament

Ok, hope you don't mind, I committed a bunch of clean up to the poms.  The
release content looks on point, and I'd happily give my +1 to get this out
the door.

John

On Sat, Aug 1, 2015 at 8:57 PM John D. Ament johndam...@apache.org wrote:

 Anatole,

 Yes, getting the first release out will help with community interest, now
 its something to play with.

 To be honest, unless there's something critical that needs to be in 0.1
 that's not there, I'd strongly like to push you to move on the release.  We
 can always circle back with more releases to fix things and make it better
 (once we have the release process in place, it becomes super easy).

 From my point of view, the release contents look good.  I'm going to do a
 deeper dive tonight to make sure nothing sticks out.  I do want to update
 the website to include how to build, since its not 100% clear (I forgot
 about the toolchains.xml requirement).  Let me know your thoughts on moving
 forward with the current codebase as 0.1.

 John


 On Sat, Aug 1, 2015 at 7:40 PM Anatole Tresch atsti...@gmail.com wrote:

 Hi John/all

 I share your concerns. Therefore I think getting out a first release is
 very important. With that it's much easier to get people involved (at
 least
 that is my hope). Also I will present it at ApacheCon Europe and I as well
 as Werner Keil also are proposing it at several conferences. And I am sure
 the first release will get widely known quickly, once I will blog on it (I
 just look at the readers count on my EE config blog). In Germany I have
 also an series of articles about configuration, also well perceived on
 JAXenter. The next 2 articles are now focusing on Tamaya especially. If
 all
 that will not be enough to grow our community, honestly we must talk about
 plan B ...

 Cheers,
 Anatole

 BTW: I did the normal
 *mvn release:prepare -DdryRun=true \*
 *-DautoVersionSubmodules=true*
 starting on the project root level. Of course, I added a few things to
 settings.xml, but nothing special.

 2015-08-01 22:55 GMT+02:00 John D. Ament johndam...@apache.org:

  Sounds good to me.  If you do createa  dry run, let me know and I can
 run
  through it as well, hopefully identify stuff that may need to get fixed.
 
  I will say this month is our reporting cycle again.  I'm concerned with
  community growth, e.g. its mostly you and Oliver.  Last report I think
 we
  were talking about a release and 3 months later, no release.
 
  John
 
  On Sat, Aug 1, 2015 at 3:30 PM Anatole Tresch atsti...@gmail.com
 wrote:
 
   Dear All
  
   I continued working on the release preparation as started By Oliver. I
   tested successfully release:prepare and also opened the corresponding
  nexus
   group with Infrastructure. Before effectively preparing the release
 for
  the
   release vote, I will further check for missing documentation, todos
 and
   errors and also as of now the metamodels extension module is empty (I
   implemented it once, but something went wrong, so I am currently
 readding
   it as part of the experimental branch).
  
   Nevertheless I look forward that we will be able to vote for our
   0.1-incubating release soon, so being able to release it before
 JavaOne
  and
   ApacheCon Europe ;)
  
   Feel free to further have a look at the current code, especially the
  TODOs
   still present at some locations.
  
   Cheers,
   Anatole
  
  
   --
   *Anatole Tresch*
   Java Engineer  Architect, JSR Spec Lead
   Glärnischweg 10
   CH - 8620 Wetzikon
  
   *Switzerland, Europe Zurich, GMT+1*
   *Twitter:  @atsticks*
   *Blogs: **http://javaremarkables.blogspot.ch/
   http://javaremarkables.blogspot.ch/*
  
   *Google: atsticksMobile  +41-76 344 62 79*
  
 



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

Re: Release Preparation

2015-05-26 Thread linead

You could just include it as part of the generated documentation?

On Wed, May 27, 2015 at 9:57 AM, Oliver B. Fischer o.b.fisc...@swe-blog.net
 wrote:

 Hi,

 where should we put our release management guide? Any idea?

 Bye,

 Oliver


 Am 22.05.15 um 18:15 schrieb Mark Struberg:

 +1, think we have done a pretty good writeup in BVal back then

 http://bval.apache.org/release-management.html

 LieGrue,
 strub



  Am 22.05.2015 um 16:33 schrieb Oliver B. Fischer 
 o.b.fisc...@swe-blog.net:

 Should I create a release document with all need preparations?

 WDYT?

 Von meinem iPhone gesendet


 --
 N Oliver B. Fischer
 A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
 P +49 30 44793251
 M +49 178 7903538
 E o.b.fisc...@swe-blog.net
 S oliver.b.fischer
 J oliver.b.fisc...@jabber.org
 X http://xing.to/obf

Re: Release Preparation

2015-05-26 Thread Oliver B. Fischer


Hi,

where should we put our release management guide? Any idea?

Bye,

Oliver


Am 22.05.15 um 18:15 schrieb Mark Struberg:

+1, think we have done a pretty good writeup in BVal back then

http://bval.apache.org/release-management.html

LieGrue,
strub




Am 22.05.2015 um 16:33 schrieb Oliver B. Fischer o.b.fisc...@swe-blog.net:

Should I create a release document with all need preparations?

WDYT?

Von meinem iPhone gesendet



--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf

Re: Release Preparation

2015-05-26 Thread John D. Ament

+1, I've seen a number of other projects just maintain it with the rest of
their docs.  It's no secret.

On Tue, May 26, 2015 at 8:09 PM linead lin...@gmail.com wrote:

 You could just include it as part of the generated documentation?

 On Wed, May 27, 2015 at 9:57 AM, Oliver B. Fischer 
 o.b.fisc...@swe-blog.net
  wrote:

  Hi,
 
  where should we put our release management guide? Any idea?
 
  Bye,
 
  Oliver
 
 
  Am 22.05.15 um 18:15 schrieb Mark Struberg:
 
  +1, think we have done a pretty good writeup in BVal back then
 
  http://bval.apache.org/release-management.html
 
  LieGrue,
  strub
 
 
 
   Am 22.05.2015 um 16:33 schrieb Oliver B. Fischer 
  o.b.fisc...@swe-blog.net:
 
  Should I create a release document with all need preparations?
 
  WDYT?
 
  Von meinem iPhone gesendet
 
 
  --
  N Oliver B. Fischer
  A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
  P +49 30 44793251
  M +49 178 7903538
  E o.b.fisc...@swe-blog.net
  S oliver.b.fischer
  J oliver.b.fisc...@jabber.org
  X http://xing.to/obf

RE: Release Preparation

2015-05-22 Thread Tresch, Anatole

Would certainly help, then we can distribute the tasks to be done on whoever 
has time to help ;)

-Original Message-
From: Oliver B. Fischer [mailto:o.b.fisc...@swe-blog.net] 
Sent: Freitag, 22. Mai 2015 16:34
To: dev@tamaya.incubator.apache.org
Subject: Re: Release Preparation

Should I create a release document with all need preparations?

WDYT?

Von meinem iPhone gesendet

 Am 22.05.2015 um 16:26 schrieb Tresch, Anatole 
 anatole.tre...@credit-suisse.com:

 Hi all,

 does anyone have more hints (some kind of checklist ?), what must be in place 
 to do a first release...
 In the mean time we have 80% plus test coverage on all modules I think, so I 
 would say
 documentation, dist package are the most next steps. Beside we can still 
 discuss on further aspects as needed...

 Cheers,
 Anatole

 Anatole Tresch
 Platform Strategy  Strategic Projects, KGVX 42
 +41 44 334 03 89 (*414 0389)

Re: Release Preparation

2015-05-22 Thread Oliver B. Fischer

Should I create a release document with all need preparations?

WDYT?

Von meinem iPhone gesendet

 Am 22.05.2015 um 16:26 schrieb Tresch, Anatole 
 anatole.tre...@credit-suisse.com:
 
 Hi all,
 
 does anyone have more hints (some kind of checklist ?), what must be in place 
 to do a first release...
 In the mean time we have 80% plus test coverage on all modules I think, so I 
 would say
 documentation, dist package are the most next steps. Beside we can still 
 discuss on further aspects as needed...
 
 Cheers,
 Anatole
 
 
 Anatole Tresch
 Platform Strategy  Strategic Projects, KGVX 42
 +41 44 334 03 89 (*414 0389)

Re: Release Preparation

2015-05-22 Thread Oliver B. Fischer

I will create a dashboard in JIRA for all open issues for 0.1. Hope to 
be able it to do until tomorrow. Have to prepare a talk currently...




Am 22.05.15 um 16:47 schrieb Tresch, Anatole :

Would certainly help, then we can distribute the tasks to be done on whoever 
has time to help ;)

-Original Message-
From: Oliver B. Fischer [mailto:o.b.fisc...@swe-blog.net]
Sent: Freitag, 22. Mai 2015 16:34
To: dev@tamaya.incubator.apache.org
Subject: Re: Release Preparation

Should I create a release document with all need preparations?

WDYT?

Von meinem iPhone gesendet


Am 22.05.2015 um 16:26 schrieb Tresch, Anatole 
anatole.tre...@credit-suisse.com:

Hi all,

does anyone have more hints (some kind of checklist ?), what must be in place 
to do a first release...
In the mean time we have 80% plus test coverage on all modules I think, so I 
would say
documentation, dist package are the most next steps. Beside we can still 
discuss on further aspects as needed...

Cheers,
Anatole


Anatole Tresch
Platform Strategy  Strategic Projects, KGVX 42
+41 44 334 03 89 (*414 0389)



--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf

Re: Release

2015-05-15 Thread Oliver B. Fischer


Hi, I am back now and will resume with my contribution to Tamaya.

Bye,

Oliver


Am 10.05.15 um 22:05 schrieb Anatole Tresch:

Hi all

we need to get out a first release soon. Therefore I would suggest, that
each and every one here on the list, will open a JIRA ticket, for each task
he or she thinks must be done before the first release. I assume we will
discuss each task and then assign a responsible to care about it.
Depending on the tasks created, we might do a rough planning for the
release date.

 From a release packaging I assume, beside the normal artifacts deployed to
mvn central, we also will provide an assembly including all sources, jars
and documentation, so we might use the documentation project to add the
assembly build there...

There are different reasons, why I think we should not wait any longer for
the release:
- we need more adoption, so we need other people trying out our code
- we need more committers, so we need as well a release, so intesting
people can have a look at the code and docs easily and also offline.
- the ladder especially is interesting, since it might be (it is under
discussion) that Credit Suisse might use our project as a show case for
starting wider OSS engagement of the bank. This would bring us manpower as
well as bullet proof use cases ;)

WDYT?

Anatole



--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf

RE: Release

2015-05-11 Thread Tresch, Anatole

No, can you perhaps help me with some links/infos what to do?

-Original Message-
From: John D. Ament [mailto:johndam...@apache.org] 
Sent: Sonntag, 10. Mai 2015 23:12
To: dev@tamaya.incubator.apache.org
Subject: Re: Release

+1 from me.  I think I already got nexus setup for you.  Did anyone make
the dist area under incubator?
On May 10, 2015 16:06, Anatole Tresch anat...@apache.org wrote:

 Hi all

 we need to get out a first release soon. Therefore I would suggest, that
 each and every one here on the list, will open a JIRA ticket, for each task
 he or she thinks must be done before the first release. I assume we will
 discuss each task and then assign a responsible to care about it.
 Depending on the tasks created, we might do a rough planning for the
 release date.

 From a release packaging I assume, beside the normal artifacts deployed to
 mvn central, we also will provide an assembly including all sources, jars
 and documentation, so we might use the documentation project to add the
 assembly build there...

 There are different reasons, why I think we should not wait any longer for
 the release:
 - we need more adoption, so we need other people trying out our code
 - we need more committers, so we need as well a release, so intesting
 people can have a look at the code and docs easily and also offline.
 - the ladder especially is interesting, since it might be (it is under
 discussion) that Credit Suisse might use our project as a show case for
 starting wider OSS engagement of the bank. This would bring us manpower as
 well as bullet proof use cases ;)

 WDYT?

 Anatole

Re: Release

2015-05-10 Thread John D. Ament

+1 from me.  I think I already got nexus setup for you.  Did anyone make
the dist area under incubator?
On May 10, 2015 16:06, Anatole Tresch anat...@apache.org wrote:

 Hi all

 we need to get out a first release soon. Therefore I would suggest, that
 each and every one here on the list, will open a JIRA ticket, for each task
 he or she thinks must be done before the first release. I assume we will
 discuss each task and then assign a responsible to care about it.
 Depending on the tasks created, we might do a rough planning for the
 release date.

 From a release packaging I assume, beside the normal artifacts deployed to
 mvn central, we also will provide an assembly including all sources, jars
 and documentation, so we might use the documentation project to add the
 assembly build there...

 There are different reasons, why I think we should not wait any longer for
 the release:
 - we need more adoption, so we need other people trying out our code
 - we need more committers, so we need as well a release, so intesting
 people can have a look at the code and docs easily and also offline.
 - the ladder especially is interesting, since it might be (it is under
 discussion) that Credit Suisse might use our project as a show case for
 starting wider OSS engagement of the bank. This would bring us manpower as
 well as bullet proof use cases ;)

 WDYT?

 Anatole

Re: Release

2015-05-10 Thread Anatole Tresch

There will be much more: e.g. multi-classloader support, EE support, CDI
integration, JMX support to name some...
Completing, advancing with the experimental modules...

Building up some complex samples for config (metamodel) and a config-server
with remote capabilities, partially distributed config, e.g. using
ZooKeeper...

So I think there is still much work ;)

Cheers,
Anatole


2015-05-10 23:12 GMT+02:00 Oliver B. Fischer o.b.fisc...@swe-blog.net:

 Hi Anatole,

 it is good that you bring up this topic. I will go through my stuff and
 create issues if needed.

 BTW, I think more than new committers we need a plan which features to add
 to tamaya in the future. I miss this a little bit. The only big feature I
 see is to have a set of values.

 Bye,

 Oliver

 Am 10.05.15 um 22:05 schrieb Anatole Tresch:

  Hi all

 we need to get out a first release soon. Therefore I would suggest, that
 each and every one here on the list, will open a JIRA ticket, for each
 task
 he or she thinks must be done before the first release. I assume we will
 discuss each task and then assign a responsible to care about it.
 Depending on the tasks created, we might do a rough planning for the
 release date.

  From a release packaging I assume, beside the normal artifacts deployed
 to
 mvn central, we also will provide an assembly including all sources, jars
 and documentation, so we might use the documentation project to add the
 assembly build there...

 There are different reasons, why I think we should not wait any longer for
 the release:
 - we need more adoption, so we need other people trying out our code
 - we need more committers, so we need as well a release, so intesting
 people can have a look at the code and docs easily and also offline.
 - the ladder especially is interesting, since it might be (it is under
 discussion) that Credit Suisse might use our project as a show case for
 starting wider OSS engagement of the bank. This would bring us manpower as
 well as bullet proof use cases ;)

 WDYT?

 Anatole


 --
 N Oliver B. Fischer
 A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
 P +49 30 44793251
 M +49 178 7903538
 E o.b.fisc...@swe-blog.net
 S oliver.b.fischer
 J oliver.b.fisc...@jabber.org
 X http://xing.to/obf




-- 
*Anatole Tresch*
Java Engineer  Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon

*Switzerland, Europe Zurich, GMT+1*
*Twitter:  @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/*

*Google: atsticksMobile  +41-76 344 62 79*

Re: Release

2015-05-10 Thread Oliver B. Fischer


Hi Anatole,

it is good that you bring up this topic. I will go through my stuff and 
create issues if needed.


BTW, I think more than new committers we need a plan which features to 
add to tamaya in the future. I miss this a little bit. The only big 
feature I see is to have a set of values.


Bye,

Oliver

Am 10.05.15 um 22:05 schrieb Anatole Tresch:

Hi all

we need to get out a first release soon. Therefore I would suggest, that
each and every one here on the list, will open a JIRA ticket, for each task
he or she thinks must be done before the first release. I assume we will
discuss each task and then assign a responsible to care about it.
Depending on the tasks created, we might do a rough planning for the
release date.

 From a release packaging I assume, beside the normal artifacts deployed to
mvn central, we also will provide an assembly including all sources, jars
and documentation, so we might use the documentation project to add the
assembly build there...

There are different reasons, why I think we should not wait any longer for
the release:
- we need more adoption, so we need other people trying out our code
- we need more committers, so we need as well a release, so intesting
people can have a look at the code and docs easily and also offline.
- the ladder especially is interesting, since it might be (it is under
discussion) that Credit Suisse might use our project as a show case for
starting wider OSS engagement of the bank. This would bring us manpower as
well as bullet proof use cases ;)

WDYT?

Anatole



--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fisc...@swe-blog.net
S oliver.b.fischer
J oliver.b.fisc...@jabber.org
X http://xing.to/obf

Re: Release of 0.1

2015-02-13 Thread Anatole Tresch

Why gh? It would be awsome other colluegues can join your ideas and help on 
them once they have reached the required level of maturity...

-
Anatole Tresch
Glärnischweg 10
8620 Wetzikon
Tel +41 (43) 317 05 30
-
Send from Mobile

 Am 13.02.2015 um 08:06 schrieb Oliver B. Fischer o.b.fisc...@swe-blog.net:
 
 I would like to go on and to develop my extensions on GitHub as separate 
 project. Later, if they is an existing user community, I can contribute them. 
 So for me it would be fine if the builder and JSON module would be removed 
 from the tree.
 
 Oliver
 
 Am 12.02.15 um 18:21 schrieb Anatole Tresch:
 I also wanted to raise that question (I was some days sick, so you were
 faster ;-D )...
 
 If extensions must be moved out to a separate tree. I think some extensions
 already work qute well (resolver( and just need some tests and docs,
 whereas many others definitively require more time.
 So if we can separate extensions somehow (even perhaps manage in a seperate
 source tree), I would agree that API and core are rather stable.
 Things to be done:
 - Checking for accurate Javadocs
 - Checking improving API/Core Documentation
 - Ensure we have a release build, which also updates our web page on
 successful build with Javadocs, asciidocs (may be coping the generated
 html...? )
  Ensuring the delivery tool chain works ;)
 
 Best
 Anatole
 
 
 
 2015-02-12 18:06 GMT+01:00 Romain Manni-Bucau rmannibu...@gmail.com:
 
 IMO for core we can release (I'd like to release a 0.1-alpha but with
 our incubating it makes too long ;))
 
 for extensions I think it is too early so maybe we should remove them
 from main tree and release them separately when someone need it in
 alpha or experimental until we manage to discuss them and integrate
 them back in main tree
 
 wdyt?
 
 
 
 Romain Manni-Bucau
 @rmannibucau
 http://www.tomitribe.com
 http://rmannibucau.wordpress.com
 https://github.com/rmannibucau
 
 
 2015-02-12 18:03 GMT+01:00 Oliver B. Fischer o.b.fisc...@swe-blog.net:
 
 -- 
 N Oliver B. Fischer
 A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
 P +49 30 44793251
 M +49 178 7903538
 E o.b.fisc...@swe-blog.net
 S oliver.b.fischer
 J oliver.b.fisc...@jabber.org
 X http://xing.to/obf

Re: Release of 0.1

2015-02-12 Thread Romain Manni-Bucau

IMO for core we can release (I'd like to release a 0.1-alpha but with
our incubating it makes too long ;))

for extensions I think it is too early so maybe we should remove them
from main tree and release them separately when someone need it in
alpha or experimental until we manage to discuss them and integrate
them back in main tree

wdyt?



Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau


2015-02-12 18:03 GMT+01:00 Oliver B. Fischer o.b.fisc...@swe-blog.net:
 Hi,

 what needs to be done for a 0.1 release of Tamaya?

 BYe,

 Oliver

 --
 N Oliver B. Fischer
 A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
 P +49 30 44793251
 M +49 178 7903538
 E o.b.fisc...@swe-blog.net
 S oliver.b.fischer
 J oliver.b.fisc...@jabber.org
 X http://xing.to/obf

Re: Release of 0.1

2015-02-12 Thread Anatole Tresch

I also wanted to raise that question (I was some days sick, so you were
faster ;-D )...

If extensions must be moved out to a separate tree. I think some extensions
already work qute well (resolver( and just need some tests and docs,
whereas many others definitively require more time.
So if we can separate extensions somehow (even perhaps manage in a seperate
source tree), I would agree that API and core are rather stable.
Things to be done:
- Checking for accurate Javadocs
- Checking improving API/Core Documentation
- Ensure we have a release build, which also updates our web page on
successful build with Javadocs, asciidocs (may be coping the generated
html...? )
 Ensuring the delivery tool chain works ;)

Best
Anatole



2015-02-12 18:06 GMT+01:00 Romain Manni-Bucau rmannibu...@gmail.com:

 IMO for core we can release (I'd like to release a 0.1-alpha but with
 our incubating it makes too long ;))

 for extensions I think it is too early so maybe we should remove them
 from main tree and release them separately when someone need it in
 alpha or experimental until we manage to discuss them and integrate
 them back in main tree

 wdyt?



 Romain Manni-Bucau
 @rmannibucau
 http://www.tomitribe.com
 http://rmannibucau.wordpress.com
 https://github.com/rmannibucau


 2015-02-12 18:03 GMT+01:00 Oliver B. Fischer o.b.fisc...@swe-blog.net:
  Hi,
 
  what needs to be done for a 0.1 release of Tamaya?
 
  BYe,
 
  Oliver
 
  --
  N Oliver B. Fischer
  A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
  P +49 30 44793251
  M +49 178 7903538
  E o.b.fisc...@swe-blog.net
  S oliver.b.fischer
  J oliver.b.fisc...@jabber.org
  X http://xing.to/obf
 




-- 
*Anatole Tresch*
Java Engineer  Architect, JSR Spec Lead
Glärnischweg 10
CH - 8620 Wetzikon

*Switzerland, Europe Zurich, GMT+1*
*Twitter:  @atsticks*
*Blogs: **http://javaremarkables.blogspot.ch/
http://javaremarkables.blogspot.ch/*

*Google: atsticksMobile  +41-76 344 62 79*

Re: Release of 0.1

2015-02-12 Thread Werner Keil

Yep, guess time for another vote;-)






On Thu, Feb 12, 2015 at 6:21 PM, Anatole Tresch atsti...@gmail.com wrote:

 I also wanted to raise that question (I was some days sick, so you were
 faster ;-D )...

 If extensions must be moved out to a separate tree. I think some extensions
 already work qute well (resolver( and just need some tests and docs,
 whereas many others definitively require more time.
 So if we can separate extensions somehow (even perhaps manage in a seperate
 source tree), I would agree that API and core are rather stable.
 Things to be done:
 - Checking for accurate Javadocs
 - Checking improving API/Core Documentation
 - Ensure we have a release build, which also updates our web page on
 successful build with Javadocs, asciidocs (may be coping the generated
 html...? )
  Ensuring the delivery tool chain works ;)

 Best
 Anatole



 2015-02-12 18:06 GMT+01:00 Romain Manni-Bucau rmannibu...@gmail.com:

  IMO for core we can release (I'd like to release a 0.1-alpha but with
  our incubating it makes too long ;))
 
  for extensions I think it is too early so maybe we should remove them
  from main tree and release them separately when someone need it in
  alpha or experimental until we manage to discuss them and integrate
  them back in main tree
 
  wdyt?
 
 
 
  Romain Manni-Bucau
  @rmannibucau
  http://www.tomitribe.com
  http://rmannibucau.wordpress.com
  https://github.com/rmannibucau
 
 
  2015-02-12 18:03 GMT+01:00 Oliver B. Fischer o.b.fisc...@swe-blog.net:
   Hi,
  
   what needs to be done for a 0.1 release of Tamaya?
  
   BYe,
  
   Oliver
  
   --
   N Oliver B. Fischer
   A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
   P +49 30 44793251
   M +49 178 7903538
   E o.b.fisc...@swe-blog.net
   S oliver.b.fischer
   J oliver.b.fisc...@jabber.org
   X http://xing.to/obf
  
 



 --
 *Anatole Tresch*
 Java Engineer  Architect, JSR Spec Lead
 Glärnischweg 10
 CH - 8620 Wetzikon

 *Switzerland, Europe Zurich, GMT+1*
 *Twitter:  @atsticks*
 *Blogs: **http://javaremarkables.blogspot.ch/
 http://javaremarkables.blogspot.ch/*

 *Google: atsticksMobile  +41-76 344 62 79*

50 matches

Mail list logo