Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdi-dev] CDI 4.0 project release plan

The  https://projects.eclipse.org/projects/ee4j.cdi/releases/4.0 is the precursor to creating that type of PR. Each of those PRs references a project creation review plan at the ee4j project level.

On Tue, Apr 27, 2021 at 11:09 AM Emily Jiang via cdi-dev <cdi-dev@xxxxxxxxxxx> wrote:
Thank you Scott for starting this release plan! I think we need to create a plan review for CDI 3.0, similar to some of these Plan Review.

Thanks
Emily


On Wed, Apr 21, 2021 at 8:54 PM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,

Thanks a lot Scott. I'll be on the next call then to provide any input for these issues where needed.

Kind regards,
Arjan Tijms


On Wed, Apr 21, 2021 at 7:18 PM Scott Stark <starksm64@xxxxxxxxx> wrote:
I have added a number of issues to discuss. We should start triaging these on the weekly calls.

On Wed, Apr 21, 2021 at 11:56 AM Scott Stark <starksm64@xxxxxxxxx> wrote:
Thanks, I'll add a point that says to consider addressing open issues and list the relevant ones starting with 460.

On Wed, Apr 21, 2021 at 11:46 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,

If it's not too late, could you add an item that says to address small changes to help alignment with/support for specs building on CDI?

This was a topic mentioned in the CDI.Next document, and would included issues to support Jakarta REST's transition to CDI such as https://github.com/eclipse-ee4j/cdi/issues/460

Kind regards,
Arjan Tijms



On Wed, Apr 21, 2021 at 6:40 PM Scott Stark <starksm64@xxxxxxxxx> wrote:
I have started a release plan for the 4.0 release that will target the EE 10 core profile;


At this point it is somewhat vague in line with other specification release plans. As we flesh out the core and lite specification changes we can update the plan. As the core platform evolves any requirements on CDI can be added as well.

Create an issue in the CDI project to discuss changes that should be reflected in the release plan.

_______________________________________________
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev
_______________________________________________
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev
_______________________________________________
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev
_______________________________________________
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev


--
Thanks
Emily

_______________________________________________
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev

Back to the top