Before creating the beta1 release, these issues must be fixed.

Feature:

Comments

vpeltot created an issue. See original summary.

colan’s picture

So, should we release the first beta now that #2706639: Support for sub-entity cloning is in, or should it be another alpha? I don't have a good sense of how stable the API is.

colan’s picture

Some issues raised here. We should fix before release. https://www.drupal.org/project/entity_clone/issues/2706639#comment-12677475

acbramley’s picture

chris matthews’s picture

Issue summary: View changes

8.x-1.0-alpha2 was released in December 2017. Since then, patches from the two issues referenced below have been committed to 8.x-1.x-dev. Would it be possible to commit the patches from the current issues with RTBC status and tag the -beta1 release? Are there any other issues that Needs work or Needs review that should be included in the -beta1 release? If so, the issue summary needs to be updated accordingly.

Issue #2706639: Support for sub-entity cloning
Issue #3008195: Move update hook to post update hook

chris matthews’s picture

Issue summary: View changes
colan’s picture

I contacted the maintainer about this issue on December 26th. We should consider following Dealing with unsupported (abandoned) projects after January 9th, after which I'm happy to become a maintainer.

vpeltot’s picture

Maintainer is back here !

Issue #3008195: Move update hook to post update hook is fixed.
I'm going to create the beta 1 release tag.

vpeltot’s picture

Status: Active » Fixed
colan’s picture

Thanks! Can we get the other RTBCs committed now (assuming they're good patches)? Let me know if you'd like some help.

https://www.drupal.org/project/issues/entity_clone?status=14&version=8.x

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.