Re: release it!

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

Re: release it!

om 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

Re: release it!

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

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

Re: release it!

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,

Re: release it!

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

Re: release it!

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

Re: release it!

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

Re: release it!

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

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.

Re: Release of Extensions

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

Re: Release Guide, Resolved or Closed Issues

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?

Re: Release Planning

+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

Re: Release Planning

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

Re: Release Planning

+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

Re: Release Planning

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

Re: Release Planning

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

Re: Release Planning

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

Re: Release Planning

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

Re: Release Staging

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

Re: Release Staging

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

Re: Release Staging

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

Re: Release Staging

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

Re: Release Staging

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

Re: Release Staging

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

Re: Release Staging

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

Re: Release Staging

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:

Re: Release Staging

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

Re: Release Staging

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

Re: Release Staging

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 -

Re: Release Staging

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

Re: Release Staging

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

Re: Release Preparation

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

Re: Release Preparation

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

Re: Release Preparation

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

Re: Release Preparation

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

Re: Release Preparation

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.

Re: Release Preparation

+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

RE: Release Preparation

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

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

Re: Release Preparation

;) -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

Re: Release

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

RE: Release

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

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

Re: Release

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

Re: Release

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.

Re: Release of 0.1

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

Re: Release of 0.1

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

Re: Release of 0.1

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

Re: Release of 0.1

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