I’ve created 1.0 tags and releases of all of the modules. I’m unable to do complete the process for the profile itself as #2132327: Can't create release: git repository tag appears in repo browser, but not vcs tables is preventing me from creating the release node. Here is a checklist of the remaining things to do to cut a 1.0 release.

Comments

mrfelton’s picture

mrfelton CreditAttribution: mrfelton commented
Issue summary: View changes
mrfelton’s picture

mrfelton CreditAttribution: mrfelton commented
Issue summary: View changes
dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
CreditAttribution: dsnopek commented

This could also be related to these issues:

mrfelton’s picture

mrfelton CreditAttribution: mrfelton commented
Parent issue: » #2132327: Can't create release: git repository tag appears in repo browser, but not vcs tables
Related issues: +#2159285: Commits and -dev release for Panopoly not updating, +#2125405: Not all commits showing up
barraponto’s picture

barraponto CreditAttribution: barraponto commented

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

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
CreditAttribution: dsnopek commented

@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. :-/

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
CreditAttribution: dsnopek commented
Related issues: +#2169079: Fix escaping in VersioncontrolGitRepositoryHistorySynchronizerDefault

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

#2169079: Fix escaping in VersioncontrolGitRepositoryHistorySynchronizerDefault

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
CreditAttribution: dsnopek commented

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. :-)

barraponto’s picture

barraponto CreditAttribution: barraponto commented

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)

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
CreditAttribution: dsnopek commented

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

jonathan1055’s picture

jonathan1055 CreditAttribution: jonathan1055 commented
Title: Create 7.x-1.x release » Create Panopoly 7.x-1.x release

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

dsnopek’s picture

dsnopek
he/him
Primary language English
Location USA
CreditAttribution: dsnopek commented

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.

barraponto’s picture

barraponto CreditAttribution: barraponto commented

YEEEEEEEEAAAH.

mrfelton’s picture

mrfelton CreditAttribution: mrfelton commented
Status: Active » Fixed

Aaannnnddd.... http://www.systemseed.com/blog/panopoly-1-1-released ;)

https://drupal.org/node/2184971

Status: Fixed » Closed (fixed)

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