Inline Entity Form stable release plan

If anyone is interested our nonprofit would be happy to sponsor the time to help get 🐛 Field permissions access override Fixed across the finish line so that Inline Entity Form can move to a stable 8.x-1.0 (or 2.0.0) release.

Nice to see 🐛 Field permissions access override Fixed get in 🎉

With no stable release for 8.x-1.x available there's already work on a 2.0.x? Can someone please explain what's going on with the module? Sites that use Commerce can't (easily; I know it's possible via some hackery, but it shouldn't be necessary) use v2. Thank you.

Maybe the switch to 2.0.x was purely to switch to semantic versioning 🤷‍♂️, but it would be good to have clarification on the difference between 8.x-1.x and 2.0.x.

I'd also appreciate notes on the differences between the major versions.

We're looking at this because we have a project where the client requires that all contributed modules have Drupal security team coverage, or we have ourselves audited the module. We haven't participated in or applied any patches from the "must-have" issues. I don't know if this is a shared experience, but given there's already a 2.x branch that could host compatibility-breaking code, I would encourage the module maintainers to tag a stable release of the 1.x branch so it can get security team coverage.

I too would very much appreciate a stable release and notes on the differences between the major versions. The current situation makes it very hard to decide which version to use for new extensive and critical functionality.

From @podarok via Slack:

2.0 was created by me in order to introduce menu reference module
I didn't want to confuse long run with 1.x branch in order to keep your pace
We fixed a bunch of issues in 2.0, but mostly related to menu reference, which is part of the YMCA Website Services distribution ( formerly Open Y ) now
It is safe to merge 1.x into 2.0, because basic functionality is not changed in 2.0
Sorry for the confusion

2.0 version created in order to add new major functionality ( Inline Entity Menu Form ) while 1.0 work in progress. 2.0 team is doing code pull from 1.0 version from time to time in order to be aligned.
1.0 still has own roadmap which will be merged in 2.0 after getting stable

Unfortunately i have been afk for quite some weeks and did not notice what is going on with that 2.x branch. According to the last comment, that branch was created as sort of personal playground or feature branch. This was contrary to the strategy agreed here, and ignoring basic semver and drupal.org maintainership rules, created that branch, and added numerous unreviewed commits, some of which added regressions, or did not contain automated tests, contrary to needs-tests tags. Which causes substantial harm to the ecosystem. I do not assume bat faith, but Dunning-Kruger is worse than bad faith. After thinking quite a while about what action is adequate, and speaking to some fellows, i marked that 2.x branch unsupported, added an explanation on the project page, revoked said person's privileges and notified them, opened 📌 Clean up problematic 2.x branch Active to coordinate further actions on this, and notified all other mainteiners and co-maintainers. Any help with the cleanup appreciated. No hard feelings.

Now to the thing i really wanted put my enegy into: I updated the IS with a ultra-minimal roadmap to a stable release (which may or may not need to be 3.0.0 now), and will stick to that until done. Any help is appreciated a lot.
Feel free to PM me if if can unblock any needed steps, but also bear with me if my reaction time is more like a week than a day, because i have s super tight schedule these days.

Habemus 3.0.0-rc18.

Note, I think we should open a 3.0.x branch ASAP so that the 3.x branch can be used as the "main" branch for new features (towards a future 3.1.x release), while we cherry-pick / backport any bug fixes or non-disruptive tasks to 3.0.x as we move towards the 3.0.0 stable release.

Thanks!
-Derek

Very good point!

I love the updated (and clearly stated) IS updates. Is there any specific timelines for the first 3.0.0 stable release?

To expand on #66, I've got a client who is looking at this project and their security posture is to use code/modules that have security support. Since this project is still a non-stable release, they feel a little uncomfortable to use it. From reviewing the must-haves, this looks really close to a stable release. It would be nice to see 📌 Get PHPStan level 1 passing and enable automated test job Active land (it is rtbc) and 📌 Drop PHP7 support to help with code cleanup Needs work as well (only NR, but easy to get to RTBC). That only leaves ✨ Allow select widget for "Add existing items" Needs work from what I can tell as blocking release. Am I reading that correctly?

@geek-merlin @heddn @volkerk Should 🐛 Changes are lost when collapsing a paragraphs subform including an inline_entity_form Needs work maybe also added to 3.x stable release plan because it seems not be fixed in 8.x-1.x yet.