Create Panopoly 7.x-1.x release

This could also be related to these issues:

• #2159285: Commits and -dev release for Panopoly not updating
• #2125405: Not all commits showing up

Did you try the workaround posted in #2132327-25: Can't create release: git repository tag appears in repo browser, but not vcs tables?

@barraponto: We have tried it many, many times - like once a week for several weeks. :-) It worked for us once, but not on any subsequent try. This was all explained in this issue: #2159285: Commits and -dev release for Panopoly not updating and they say there are still bugs to be squashed. :-/

FYI, I beleive it's this bug that's preventing proper releases for us right now

#2169079: Fix escaping in VersioncontrolGitRepositoryHistorySynchronizerDefault

Another random FYI: We've already accumulated enough changes for a 1.1 release, which will probably be made at the same time as 1.0 once Drupal.org will let us. :-)

Are we going to have 1.1 release for the panopoly modules? I'm using the 1.0 set right now for my panopoly-based distros (https://github.com/barraponto/kw-skeletons/blob/panopoly-l10n/SKELETON.make)

Yes, we will make 1.1 versions of all the Panopoly modules when we do the Panopoly 1.1 release.

Made the title explicit, as this issue is now referenced from other module queues.

The Drupal.org bugs appear to be fixed! We should be good to finally roll the 1.0 release and jump straight to 1.1 as well. :-) I'll ping @populist and @mrfelton to see what the game plan is.

YEEEEEEEEAAAH.