Closed (fixed)
Project:
HEAD to HEAD
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
7 Oct 2010 at 04:59 UTC
Updated:
20 Mar 2015 at 15:31 UTC
Jump to comment: Most recent
Now that the beta1 is out is it true that upgrades from here on out will be supported in core? (e.g., no more need for head2head from here on out for Drupal 7)
My source for this information is from this Acquia article)...hoping someone can confirm either way.
Comments
Comment #1
catchThere needs to be a head2head update for #895014: All fields of a node type are lost on module disable. I believe that's the last schema change prior to beta that doesn't have a patch yet.
I'm pretty sure any beta-beta schema changes will need to support existing Drupal 7 sites, that means we can retire this project more or less apart from any bugs that come up, or alternatively mothball it until Drupal 8 opens up.
Comment #2
int commentedI think that now after the beta1, the DB updates must be only in drupal core.
To ensure that all drupal7 sites work fine.
Comment #3
rfay/me is *really* hoping we can do something more sophisticated and robust in the D8 cycle. Oh so much.
Reference: #876764: Handle intra-alpha updates with a more convenient strategy (perhaps special hook_update_alpha_N()?)
Comment #4
rfayHoping for an alpha-to-alpha final that will do the job?
Comment #5
Jackinloadup commentedwith #4 rfay
waiting for a go
Comment #6
David_Rothstein commentedSafe to say this support request is as fixed as it's ever going to be for Drupal 7 :) For Drupal 8, see #2455949: [policy, no patch] Re-activate the head2head project and use it for beta2beta upgrades in the short-term.