Stable release roadmap

I repurposed this issue as a stable release roadmap, which will include multiple releases.

I also support it.
I can help you providing and reviewing patches.

Just cleared out the RTBCs and cut beta5.

Note #2724939: Change cloned entity's created-date to the date it was cloned is ready for review.

Requesting review, as stable release blocker issue are fixed. Once we get approval on this will cut the 2.0.0 stable release.

Just my 2 cents, but anyone who manages a site using Layout Builder would likely consider #3050027: Inline Blocks on Layout Builder Fail to Clone Correctly a stable release blocker. The fix had to be reverted, so the issue is open again.

Certainly! Addressing the concern at hand, we can indeed consider making an exception for Layout Builder as part of our current development strategy. We understand that it holds a unique place in our ecosystem and requires special attention.

Additionally, your suggestion of creating a dedicated submodule to support entity cloning in conjunction with Layout Builder is a prudent measure. This approach allows us to safeguard against potential disruptions for other functionalities. By isolating this support into a separate module, we can ensure that if there are any specific compatibility issues or bugs, they can be managed without affecting the stability of the core system. This separation of concerns will facilitate smoother integration and provide a clearer path for maintenance and updates in the future.

Are there any other details or specific workflows you believe we should consider in this context?

Regarding the concerns about the Layout Builder's issue(#3050027: Inline Blocks on Layout Builder Fail to Clone Correctly) with the Entity Clone module, I believe we can address this issue independently rather than allowing it to delay the stable release. We will continue to monitor the issue closely while proceeding with the release.

@colan, @joevagyok, @vpeltot, @Upchuk, @NickDickinsonWilde I would appreciate hearing your opinion on this matter.
I have created the 2.0.0 tag, but it has not yet been released.

I appreciate your willingness to have the discussion @Rajeshreeputra, and I don't want to overstate or belabor the point. That said, I think a stable release implies that all known critical/major issues around Drupal core functionality have been resolved. If there were incompatibilities with other contrib projects, I'd get it. But Layout Builder and translated entity references are both core-provided functionality with outstanding issues (#3050027 and #3258535 respectively) that can and do lead to data loss.

If you do proceed with a "stable" release, please consider adding a warning to the release notes (and, ideally, the project page) that Entity Clone should not be used in those cases. Thank you!

My thoughts: Let's make it a beta release until core support is resolved.

Sure, will cute the beta, along with #3363333: Cloneable entities functionality does not restrict content type entity and #3359414: Option to clone content nodes including all comments.

Adding blockers to the IS.

For issues #3103935: Provide aliases to cloned content. and #3258535: Translatable entity reference fields are not cloned correctly, we have requested a review from the community. Upon receiving the 'Reviewed & Tested by the Community' (RTBC) status, we will proceed with the merge and release.

This will leave us with only issue #3050027: Inline Blocks on Layout Builder Fail to Clone Correctly to resolve before we can proceed with a stable release.

Is this roadmap still accurate?

https://www.drupal.org/project/entity_clone/issues/3050027
and
https://www.drupal.org/project/entity_clone/issues/3258535

are blockers?? Or can a D11 release be made with these bugs? And maybe the bugs can be mentioned in the release notes?