Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [krazo-dev] Our next steps...
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.

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?

Ivar

On Wed, Oct 23, 2019 at 6:01 PM Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote:
@Ivar Do you perhaps know if something like 1.0.0.Beta1 is possible at all? The Eclipse Handbook contains this:

Milestone builds and release candidates are not themselves official releases. Per the Eclipse Development Process, milestone and release candidate builds are intended to be consumed by a limited audience to solicit, gather, and incorporate feedback from leading edge consumers. 

The "limited audience" doesn't sound like we are allowed to push to Maven Central!?! Not sure how strict these rules are. And maybe this is even a PMC decision? I don't think that there was any Beta-like release in EE4J yet!?

Christian

Am Mi., 23. Okt. 2019 um 13:40 Uhr schrieb Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>:
I am good with any versioning as long as it is 1.0.0<something>. 

Ivar

On Wed, Oct 23, 2019 at 1:00 PM Gregor Tudan <gregor@xxxxxxxx> wrote:
+1 for beta1. I think that a beta better reflects our current status than another milestone release.

I‘m really looking forward to that final! 😃

> Am 23.10.2019 um 11:38 schrieb Tobias Erdle <tobias.erdle@xxxxxxxxx>:
>
> Hi all,
>
> IMO the plan sounds good.
>
>> I'm not quite sure which version this should be. If we keep the
>> versioning scheme of Ozark, the next release would be 1.0.0-m05 as
>> originally planned. Releasing something like 0.9.0 would be weird,
>> because it looks like the Ozark version was more recent.
>> Maybe 1.0.0.Beta1?
>
> I think a version 1.0.0Beta1 is better than some milestone version, because it shows progress and that we move straight towards our target of a final release.
>
> Best regards,
>
> Tobias
>
>>> Am 23.10.19 um 10:55 schrieb Christian Kaltepoth:
>> Hi all,
>> as the Krazo CQ <https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18559> is
>> finally approved, we should talk about our next steps.
>> Back then our plan was to release 1.0.0-m05 as soon possible after the
>> transfer to Eclipse is completed and after that work on passing the TCK on
>> at least one container and release it as 1.0.0-m06.
>> As the transfer and IP check took so long, we need to adjust the plan. So
>> my proposal is to proceed like this:
>> We should start the release procedure for our first release in the next
>> days. I'm not quite sure which version this should be. If we keep the
>> versioning scheme of Ozark, the next release would be 1.0.0-m05 as
>> originally planned. Releasing something like 0.9.0 would be weird, because
>> it looks like the Ozark version was more recent. Maybe 1.0.0.Beta1? I'm
>> currently checking what we need to do for the release. It looks like there
>> is quite some paperwork to do, but I can take care of this.
>> After the first Eclipse Krazo release is out, I would immediately like to
>> start the procedure of going final with the spec. I still need to write a
>> bit of documentation for the TCK, but this won't be very much work. Then we
>> need to stage release for the specification and the TCK. At this point we
>> can also prepare the release for Eclipse Krazo 1.0.0. All of this will
>> require some timing, because there will be JCP ballots and EE4J ballots
>> involved.
>> So for Krazo this would mean:
>>   - Release 1.0.0-m05 (or however we call it) ASAP
>>   - Release 1.0.0 together with the spec after that
>> Thoughts?
>> 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
>
> _______________________________________________
> 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


--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation, Inc.

Eclipse Foundation: The Platform for Open Innovation and Collaboration

Back to the top