Problem/Motivation

While working on #1973510: Support Field Collection field types noticed that the patch from that issue does work with the latest dev but not latest tagged release. I also received feedback from users who tried the patch and used latest tagged release which is beta11.

Proposed resolution

Roll out a new tagged release. Or are there other issues that need to be resolved before that?

Comments

Primsi created an issue. See original summary.

Primsi’s picture

Respectfully bumping this :)

Liam Morland’s picture

Title: New tagged release beta12 » New tagged release beta13

7.x-1.0-beta12 was released on 17 November 2016.

7.x-1.0-beta13 should be released.

Liam Morland’s picture

It has been a year since the last beta and there are several commits past that which are almost a year old. I would really appreciate if if the current development version were released as 7.x-1.0-beta13. Then there are several RTBC patches which should be committed leading to 7.x-1.0-beta14.

fubarhouse’s picture

Agreed Liam,

There is a lot of good work that isn't included in the latest beta.

As much as I would love an actual release, a new beta makes more sense given the quantity of features and fixes found in the dev version.

Also, I'll add my +1 here!

Liam Morland’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

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