This is a release co-ordination issue for CiviCRM Entity 7.x-2.0
7.x-2.0 will be released when the following issues are addressed:
* #2203921: Error after enabling module (does this affect 7.x-2.x?)
* #2271487: Provide option to select username format when creating linked users
* #2351509: Support Image (and other) Fields
* #2413425: Inconsistent Date Format
* #2476231: GH-43: WSoD on upgrade from 7.x-1.x to 7.x-2.x
* #2476759: Expose Contribution Pages as an Entity
* #2476763: Move CiviCRM Entities from Structure -> Content Types menu
* #2476777: Coding standards for 7.x-2.x
* #2477089: Remove unused, insecure password setting when creating a user
* #2804987: Remove need to clear caches twice
| Comment | File | Size | Author |
|---|
Comments
Comment #1
xurizaemonComment #2
xurizaemonComment #3
xurizaemonWhoops wrong issue :D
Comment #4
jkingsnorth commentedI think #2477089: Remove unused, insecure password setting when creating a user should be on the list, so I've added it, hope that's OK.
Comment #5
xurizaemonComment #6
markusa commented#2351509: Support Image (and other) Fields
This is a feature request IMO. accepting patches or merge requests on github. If it doesn't get in then its not an issue for me. Not a deal breaker for a 2.0 stable release. there is a way around it with the imagecache_external module...
#2413425: Inconsistent Date Format
CiviCRM Entity eats what CiviCRM feeds it. We need to handle it "correctly", even if its not consistent. As to making it consistent, take it up with the folks at CiviCRM. Not a deal breaker for a 2.0 stable release.
Comment #7
markusa commentedBeta3 has been released, with new features and the bug fixes here.
I've posted several new fixes, and some minor new features int he -dev release, that will be beta4 by the end of the month (November) (may even call it a release candidate).
Time to start thinking hard about an offical 2.0 release...
Most new features from here on out will be going into the sub-modules, because the main CiviCRM Entity module has had many bug fixes, and improvements over the past year, its battle tested now, and feels really solid to me.
Comment #8
markusa commentedunless anyone has any objections, its about time to release 2.0 official.
Today I released beta5 with a few bug fixes, and then if no new issues appear, its time to release it.
Comment #9
xurizaemonLooks good to me! Do it :)
Are all the issues fixed in this upcoming release the ones listed in this ticket? (I see all those issues are fixed or closed, but wonder if there are others not mentioned?)
Comment #10
markusa commentedFixed:
https://www.drupal.org/node/2452157
https://www.drupal.org/node/2831998
https://www.drupal.org/node/2452157
In the last several betas there's been not too much changed in the main module. I think there were a few bug squashed and a few improvements that got done without issues.
The major development as been in the new submodules in the beta3 and beta4 releases.
I seriously need to get about 20 pages of documentation written.
Comment #11
markusa commented