I just tried deploying Drupal 7.11, and if I'm not mistaken, there's a major problem. It seems to contain Drupal 7.9 + security fixes, rather than Drupal 7.10 + security fixes.

Therefore, all the bug fixes that went into Drupal 7.10 will be gone for anyone who upgrades to Drupal 7.11.

I am not quite sure what to do about this... Do we create a Drupal 7.13 that contains the code that should have been released as Drupal 7.11?


xjm’s picture

Yeah, NO idea what to do here. Releasing a 7.13 that is 7.10 + security fixes would be even worse--it would downgrade all the sites that just upgraded to 7.12.

catch’s picture

What about moving the tag and forcing a rebuild of the release tarballs? That's not very good either though.

grendzy’s picture

It's hard to think of a solution that wouldn't make it worse. The obvious answer to me is publishing 7.13 (7.10 +fixes), and 7.14 (same as 7.12), but as xjm says you're almost back to the same problem.

How about we do nothing? There are only 348 users of 7.11 at last count. We could make a public service announcement alerting users to the error, and suggest users begin planning an upgrade to 7.12.

scor’s picture

PSA as I know them are for security related matters. 7.11 did include the latest security patches and does not introduce any security regression, the only regressions are mostly bug fixes.

David_Rothstein’s picture

@webchick already updated the announcements at http://drupal.org/node/1425092 and http://drupal.org/drupal-7.12 with this information (even used a <marquee> tag on the first one!). I'm not sure if there is anywhere else to announce it.

Neil Adair’s picture

I updated to core 7.11 because the site used i18n 7.1.3 and the site broke (unexpected error) when I updated to i18n 7.1.4, subsequently updating to core 7.12 fixed the problem.

If you updated to core 7.11 due to i18n, update to core 7.12 before updating i18n to 7.1.4

klausi’s picture

I would suggest to release Drupal 7.11.1 (=Drupal 7.10 + security fixes, really this time), unpublish Drupal 7.11 and replace references to Drupal 7.11 everywhere with Drupal 7.11.1

Steven Jones’s picture

What about moving the tag and forcing a rebuild of the release tarballs? That's not very good either though.

Maybe not ideal, but that's what we want to do here surely?

catch’s picture

Yeah I still think that's the best option.

Gábor Hojtsy’s picture

The best option is to have two different Drupal 7.11s out there?

catch’s picture

Yeah I think that's better than releasing a 7.12 that doesn't contain bugfixes from 7.11, or a 7.13 that's exactly the same as 7.11.

It's several days since the release now though, so we could just mark this won't fix I guess.

Gábor Hojtsy’s picture

Yes, I would say not doing anything beyond documenting the problem (which was already done in a ver visual way) is the best option for us now.

klausi’s picture

What are the arguments against 7.11.1?

xjm’s picture

We should probably update http://drupal.org/drupal-7.12 in addition to the release notes and then mark this won't fix, I think, since we're now two weeks after the fact.

grendzy’s picture

Status:Active» Needs review

klausi, 7.11.1 isn't an option as far as I know, because a new version format (according to http://groups.drupal.org/node/152484) would require "changes to various dependencies like Update Status/Update Manager, project packaging scripts, Drush, etc".

I agree with "won't fix", after updating the announcement page:

Discussion is ongoing at Administrators are encouraged to update to 7.12 as soon as possible. See #1430404: Drupal 7.11 is missing all the bug fixes from Drupal 7.10 for details.

xjm’s picture

Status:Needs review» Fixed

The text has been updated at:

So, let's call it fixed?

webchick’s picture

Hey, thanks so much for taking care of this, folks. I'm really sorry I dropped the ball here. :( I literally have had _zero_ time last week and this between various travel and things going on with work.

I agree that in this case, when we're literally talking about less than 1% of sites that are affected, simply amending the release notes/announcement is a much better approach than a new version which would confuse the crap out of people.

sandiec’s picture

Is it possible to upgrade from drupal 7.0 to drupal 12 without re installing. My hosting people changed me to a server that has a newer version of PHP that comes with 7.0 only. I am new at this drupal cms and I find the task quite daunting to re install drupal. My hosting company does however use fantastico

If the answer is no please indicate step by step the process.
Thank you

grendzy’s picture

Hi sandiec, Updating from 7.0 to 7.12 is possible, yes. However this queue is for issues in the Drupal core code itself. Please visit http://drupal.org/support to see what your support options are if you need more assistance. http://drupal.stackexchange.com/ is another good option.

Status:Fixed» Closed (fixed)

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