Because of #2230709: Using the new Susy 2, we're currently stuck on a git hash of Omega and cannot update until this is resolved.

But even if we update Pieces to support Susy2, other end user themes may not work correctly... So what should we do? Just backport patches? I'm not too thrilled that they made an API change right in the middle of a release but meh.

CommentFileSizeAuthor
#3 2398093-omega4-backports-3.patch10.65 KBjaperry
#1 2398093-omega4-backports-1.patch2.69 KBjaperry
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

japerry’s picture

japerry
Location KVUO
CreditAttribution: japerry at Drupal Association commented
FileSize
2398093-omega4-backports-1.patch2.69 KB

In the meantime, here is a patch that backports all changes post susy 2.

japerry’s picture

japerry
Location KVUO
CreditAttribution: japerry at Drupal Association commented
Assigned: Unassigned » DyanneNova

Sounds like we want to stick with singularity? Will updating omega past Susy2 affect anything?

japerry’s picture

japerry
Location KVUO
CreditAttribution: japerry commented
FileSize
2398093-omega4-backports-3.patch10.65 KB

This patch encapsulates all commits from 4.3 to hash: d08b9ccf0b1779557d87fa941f54b1a35cfa28a8