Need to get an RC staged by Dec 15.

[starksm64]

We need to put together a full release candidate that I can then stage for review by the specification project by Dec 15 for inclusion in EE10. Please link to whatever tasks are needed for that and feel free to assign any to me.

[manovotn]

Here is what I know we need to do.

CDI spec:

• Move BeanContainer method under BeanManager, see BeanContainer#getInjectableReference should probably be on BeanManager instead #568
• Allow OM to access declaring class via CDI API, see Portable Extension's ObserverMethod doesn't expose the declaring Bean #563
• Specify invalid treatment of @Enhancement and @Registration phases, see Specify treatment of invalid @Enhancement and @Registration #576
• Move @SessionScoped into CDI Full, see Move the session scope to CDI Full #577

TCKs:

• Some tests are not under appropriate package AmbiguousInjectableReferenceTest and UnsatisfiedInjectableReferenceTest are not in full package cdi-tck#320
• Adjust CustomStereotypeTest, see Adjust CustomStereotypeTest to also include annotated class which sho… cdi-tck#323
• Provide tests for negative scenarios when using Build compatible extensions, see Create negative tests for build compatible extensions cdi-tck#321
• Add tests for withSubtypes and withAnnotations, see Add test for "withSubtypes" and "withAnnotations" members of @Enhancement cdi-tck#322
• Provide test coverage for OM exposing declaring Bean, see Provide test coverage for OM exposing Bean cdi-tck#324
• Check whether tests with @SessionScope are under "Full" category, see Review if tests with @SessionScope are under Full category cdi-tck#325

These issues are already being worked on by either me or @Ladicek and I guess we'll be able to address them pretty fast.

[Ladicek]

@manovotn thanks, I wanted to put down a similar list myself :-) Can you make each item a TODO item? It's enough to put [ ] after the bullet point. For example, this:

- [ ] my TODO item
- [ ] my other TODO item

results in:

• my TODO item
• my other TODO item

[manovotn]

@Ladicek, I was going to do it once I had all the issues.
Updated with checkboxes and updated with additional issues.

[Ladicek]

Perfect, thanks!

[manovotn]

Correct me if I am wrong @Ladicek but I think we have everything done except for merge of jakartaee/cdi-tck#328 which requires new CDI API version anyway :-)

[Ladicek]

How about we do a 4.0.0.Beta3 so that we can get the PR done and merged? :-)

[Ladicek]

In other words, yea I agree, we should be ready for RC.

[manovotn]

How about we do a 4.0.0.Beta3 so that we can get the PR done and merged? :-)

Did you just volunteer? :D

[Ladicek]

How about we do a 4.0.0.Beta3 so that we can get the PR done and merged? :-)

Did you just volunteer? :D

I'm on it!

[Ladicek]

Aaaand done, Beta3 should be on its way to Central.

[Ladicek]

It's there: https://repo.maven.apache.org/maven2/jakarta/enterprise/jakarta.enterprise.cdi-api/4.0.0.Beta3/

Let's get that one last PR updated and merged.

[manovotn]

It's there: https://repo.maven.apache.org/maven2/jakarta/enterprise/jakarta.enterprise.cdi-api/4.0.0.Beta3/

Let's get that one last PR updated and merged.

Thanks, on it!

[manovotn]

@starksm64 all the tasks that I was aware of are now completed.

[starksm64]

Ok, I'll start on an RC. Is there an updated Weld release that should be used in the TCK distribution?