[META] - First alpha release [#2701623]

Before the first release, all Drupal entities must works correctly.
And #2701225: Add test coverage for all already managed entities must be closed

Compatibility with Content Entities

Entity name	Machine name	Compatibility status
Custom block	block_content	OK
Comment	comment	OK
Content	node	OK
File	file	OK	#2701229: [File] - Entity clone does not work properly
User	user	OK	#2701237: [User] - Entity clone does not work properly
~~Custom menu link~~	~~menu_link_content~~	NOK	#2701231: [Custom menu link] - Entity clone does not work properly
~~Shortcut link~~	~~shortcut~~	NOK	#2701233: [Shortcut link] - Entity clone does not work properly
~~Taxonomy term~~	~~taxonomy_term~~	NOK	#2701235: [Taxonomy term] - Entity clone does not work properly
Aggregator feed	aggregator_feed	Unknown
Aggregator feed item	aggregator_item	Unknown
Contact message	contact_message	Unknown

Compatibility with Config Entities

Entity name	Machine name	Compatibility status
Action	action	OK
Block	block	OK
Content type	node_type	OK	#2701739: [Content type] - No attached field
Custom block type	block_content_type	OK	#2701731: [Custom block type] - No attached field
Comment type	comment_type	OK	#2701733: [Comment type] - No attached field
Contact form	contact_form	OK	#2701737: [Contact form] - No attached field
Language	language	OK
Date format	date_format	OK	But all basic entities are locked after clone #2701715: [Date Format] - Basic entities stay locked after clone
Field	field_config	OK
Form mode	entity_form_mode	OK
View mode	entity_view_mode	OK
Text format	filter_format	OK
Image style	image_style	OK
Menu	menu	OK	But menu link must be cloned too ?
Responsive image style	responsive_image_style	OK
Role	role	OK
Search page	search_page	OK
Shortcut set	shortcut_set	OK	But shortcut link must be cloned too ?
View	view	OK
Text Editor	editor	NOK	Error with toUrl()
Tour	tour	NOK
Content Language Settings	language_content_settings	Unknown
RDF mapping	rdf_mapping	Unknown
Migration	migration	Unknown

Exception or entity cannot be cloned alone :

Base field override (base_field_override) : This entity is cloned only if the entity who used this base field override is cloned
Field storage (field_storage_config) : This entity is cloned when a Field is cloned
Entity view display (entity_view_display) : This entity is cloned only if the entity who used this display is cloned
Entity form display (entity_form_display) : This entity is cloned only if the entity who used this display is cloned

Comments

Comment #1

7 April 2016 at 05:45

vpeltot created an issue. See original summary.

Comment #2

vpeltot CreditAttribution: vpeltot commented 7 April 2016 at 05:58

Title:

[META] - Before release

» [META] - Entities compatibility

Comment #3

vpeltot CreditAttribution: vpeltot commented 7 April 2016 at 08:21

Issue summary:

View changes

Comment #4

vpeltot CreditAttribution: vpeltot commented 7 April 2016 at 08:35

Issue summary:

View changes

Comment #5

vpeltot CreditAttribution: vpeltot commented 7 April 2016 at 08:38

Issue summary:

View changes

Comment #6

vpeltot CreditAttribution: vpeltot commented 11 April 2016 at 06:58

Version:		» 8.x-1.x-dev
Issue summary:	View changes

Comment #7

vpeltot CreditAttribution: vpeltot commented 11 April 2016 at 06:58

Issue summary:

View changes

Comment #8

vpeltot CreditAttribution: vpeltot commented 11 April 2016 at 06:59

Title:

[META] - Entities compatibility

» [META] - First release

Comment #9

vpeltot CreditAttribution: vpeltot commented 12 April 2016 at 10:13

Issue summary:

View changes

Comment #10

vpeltot CreditAttribution: vpeltot commented 12 April 2016 at 10:13

Issue summary:

View changes

Comment #11

vpeltot CreditAttribution: vpeltot commented 12 April 2016 at 10:14

Status:

Active

» Needs work

Comment #12

vpeltot CreditAttribution: vpeltot commented 12 April 2016 at 10:17

Issue summary:

View changes

Comment #13

vpeltot CreditAttribution: vpeltot commented 14 April 2016 at 07:32

Issue summary:

View changes

Comment #14

vpeltot CreditAttribution: vpeltot commented 14 April 2016 at 07:32

Issue summary:

View changes

Comment #15

vpeltot CreditAttribution: vpeltot commented 14 April 2016 at 07:38

Issue summary:

View changes

Comment #16

vpeltot CreditAttribution: vpeltot commented 14 April 2016 at 07:57

Issue summary:

View changes

Comment #17

vpeltot CreditAttribution: vpeltot commented 14 April 2016 at 07:57

Issue summary:

View changes

Comment #18

colan

he/him

English

Toronto 🇨🇦

CreditAttribution: colan at Colan Schwartz Consulting commented 20 September 2017 at 15:34

I think it would be fine to start cutting alpha releases though. The module is now being used by 1407 sites so there is definitely some functionality that's usable.

Comment #19

vpeltot CreditAttribution: vpeltot commented 22 September 2017 at 09:56

Issue summary:

View changes

Let's go to release this module!

Release cycle plan:

Release	Target date	Details
1.0-alpha1	September 22	All tests must be OK
1.0-alpha2	September 29	With minor bug fixes that are already in status RTBC & Needs review (to be passed in RTBC)
1.0-beta...	every weeks	With Bug fixes and the big change about the recursive clone
1.0-rc1	before the first 8.4.x monthly bugfix release (November 1)
1.0-rc...		With bug fixes (if necessary)
1.0		When no new bug are created since 2 weeks