Roll a new UUID stable release

I'm taking a long weekend off with the family. I think it is worth reviewing some patches and doing some QA next week before considering a new release.

Any time would be great for a release to address this known issue. I just burned the last three hours hunting it down, and I'd be delighted if I were the last one to have to do so.

We discussed a new release in Munich. There are a couple of bugs we want to fix before cutting the new release. Expect something soon.

Excellent. Thanks!

Is there a listing somewhere for issues/bugs on the roadmap so that we can contribute/follow? I've just been trawling through all D7 UUID issues and couldn't really get an idea of which ones are pending (apart from some recent updates).

Please please please, any updates on this HUGE issue? UUID has broken Rules for my client's site, which is Not Okay.

I would also love to see a new UUID release!

I went through the issue queue and found some bug fixes that I think should be rolled into a new release. They will need a maintainer to review, but seem to have some inertia in the queue and address bugs with current version:

#1605284: The following token types are not defined but have tokens
#1764468: Variable $entity_ids got renamed and needs to be updated.
#1795152: tnid is localised too early when deploying a new node that is the source for a translation
#1565082: FIx documented hook names for features rebuild & revert
#1777980: Tests fail if optional deploy module is not present.
#1764516: Repeated functions / Syntax error.
#1666220: Wrong target_type get from entity reference field.
#1596990: Remove hook_features_enable_feature

Any news?

The latest stable release (alpha3) gives many notices due to #1810226: Error message when deploying a site: Undefined variable: $replacements, but the latest dev release is working fine for me.

Any news?

Not sure if this might product an alpha4 or a beta1 or maybe even an RC?

bump

This got me too.

A new release should be put out as soon as possible. I've had fatal PHP errors with both Commerce and other modules that utilize UUID, which updating to dev fixes.

I would be willing to bet that the alpha release from January 2012 breaks a lot of modules, and it has been a year.

If the maintainers feel like granting me commit access I would be more than willing to shuffle this along.

The deploy-revisions branch will need to be reviewed and merged before a new release is cut. Our test coverage is slipping too. There is nothing stopping people from using git snapshots.

Fixing priority.

I concur that a new release should be rolled as soon as possible, even without the pending stuff. (it's been since June 2012 since users have been asking for this).

Also the Rules module is breaking because of this module (which has been fixed in dev by the way). Please refer to this thread for more information: #1792524: code error which causes adding new condition to not do anything when user clicks on "Continue" green button

Putting back priority to critical as this is causing other modules to break, also affecting lots of developers and development time consequently.

There's nothing stopping devs from using the dev branch, no, but for others who update modules from Drupal admin (trust me, they're out there)- they get punched in the gut. Handled three external cases this month revolving around UUID.

This is a problem with an alpha release, the priority is major not critical. Please stop playing with the priority.

If you want to change the priority to "major" and not "critical", at least put a message on the module's page (in bold at the top and in red) telling users to not use this module because it breaks a lot of stuff, it wastes developer's time trying to hunt the issue down and affects a lot of people.

Modules that rely on UUID have been broken since alpha3 and wound up finding ways to not depend on UUID due to the fatal errors.

skwashd what is needed to move forward with this issue?

I would like to see a stable release; we have a site where we wanted to use uuid for node_export, but we couldn't because of a conflict with rules. Dev branch is not an option for us because of company policy.

This is a pretty fatal bug - I can't see why a quick release can be generated to correct it. It is misleading to have alpha3 marked stable when it will break your site if certain other modules are present (Rules, Commerce, etc).

@populist made a good list in #8, many of the issues there are now RTBC. How do we get them fixed. Any others missing?

Seems the alpha is less than stable and that everyone's recommending using the dev version of the module.

Maybe the alpha should be removed for now.

I am in agreement with #27. alpha3 is 15 months old, and the current dev is much better. If there are too many open issues to make a final release, then an alpha4 or beta1 release should be pushed out, and the remaining open issues could be addressed as time permits.

Wow, we are 52 commits ahead of the current release. Spent 4 hours to figure out that tokens for field collections aren't available because of wrong logic in hook_entity_property_info_alter (#1427462: Variable overwrite in uuid_entity_property_info_alter()).

Just sent an email to dixon_ (maintainer) and asked him when he will release a new version.

A new release is rolled. Sorry to have kept you all waiting.

Finally! <3

Thanks!