| Re: [krazo-dev] Our next steps... |
Thanks, Ed. I wasn't aware of that. So maybe graduation shouldn't be top priority for us as well.Am Do., 24. Okt. 2019 um 23:08 Uhr schrieb Ed Bratt <ed.bratt@xxxxxxxxxx>:_______________________________________________If it matters, just about everything in the EE4J sub-project collection is still shown as Incubating. We haven't taken the time to pull the materials together and actually graduate most projects (maybe none of them?).
On 10/24/2019 4:11 AM, Ivar Grimstad wrote:
That's a good question... Graduation review can be combined with the release review though...I see that the incubating logo is on the project page, so I guess we are...
Ivar
On Thu, Oct 24, 2019 at 12:47 PM Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote:
Do we also need a Graduation Review? Are we still in incubation status?
Am Do., 24. Okt. 2019 um 11:29 Uhr schrieb Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>:
We would have to engage in a release review, which is typically up to 14 days.For patches, bugfixes (or service releases as they are referred to in EF), this is not necessary.
Ivar
On Thu, Oct 24, 2019 at 10:39 AM Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote:
_______________________________________________Hi Ivar,
No, we haven't had any beta releases yet.According to the EDP (https://www.eclipse.org/projects/dev_process/#6_4_Releases), we can do a milestone or release candidate build. I would suggest 1.0.0-RC1 for example.
But could we also push them to Maven Central? The text I quoted above mentions that these releases are targeted at a "limited audience", whatever that means.
Another question is whether we need to do that at all? Couldn't we just release a final release when we have released the spec? What do we gain from releasing a version before that? The only thing I can come up with is that we would like to test the release process, and that may maybe be a good enough reason?
I would love to give the release process a try before going final with the spec and Krazo. Just to learn what has to be done, how it is done and in which problem we may run. I would also like to learn about the review process and all the things that need to be done for it. This will also help to understand how long such a process will take. This is important because I would really like to push out releases often. Especially because I'm quite sure that after we are final more people will start to use Krazo and will most likely run into issues and bugs that we need to fix.
Christian
--
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/krazo-dev
--
_______________________________________________Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation, Inc.
Eclipse Foundation: The Platform for Open Innovation and Collaboration
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/krazo-dev
--
_______________________________________________
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/krazo-dev
--
Ivar Grimstad
Jakarta EE Developer Advocate | Eclipse Foundation, Inc.
Eclipse Foundation: The Platform for Open Innovation and Collaboration
_______________________________________________ krazo-dev mailing list krazo-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/krazo-dev
krazo-dev mailing list
krazo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/krazo-dev
--