I apologize in advance if this isn't the proper forum for this question...

What issues are holding back the 7.x-2.x branch from a full release? Is there any plan to close that gap? Are there reasons that the maintainers have chosen not to take that step?

Thank you!

Comments

rickward created an issue. See original summary.

snufkin’s picture

snufkin CreditAttribution: snufkin at Acquia commented

No, this is the right place for it.

The main reason I think is lack of time from the maintainers side to coordinate and review everything. Here are the steps I would take to plan for the full release:

1. Review existing bugs for 2.x and check if any of them could be a release blocker
2. Review existing issues for 2.x and decide which ones we want to include in the 2.x release
3. If there are any issues found in 1. or 2. I'd open a meta-issue so we can track the progress of merging those into 2.x-dev
4. Make the changes and roll the release

It would be incredibly helpful, if you could help with reviewing the issue queue with respect to 2.x bugs and features and see if there are any release blockers, or features that are easy to commit and would be good in a 2.x stable.

rickward’s picture

rickward CreditAttribution: rickward commented

I can absolutely help with triaging the issue queue. I will follow up shortly.

rickward’s picture

rickward CreditAttribution: rickward commented

snufkin:

I reviewed the 7.x-2.x-alpha2 issue queue, and only two issues jump out at me:

https://www.drupal.org/node/2377727
This looks important, but I haven't had a chance to test locally. If the Drupal session is being killed, this shouldn't really be an issue. Killing the entire SSO session shouldn't be the job of this module, correct? We redirect to a global logout.

https://www.drupal.org/node/2681159
I haven't experienced this issue with simplesamlphp 1.14.2. Perhaps the issue is with simplesamlphp. So this may just be a "need to update" or configuration issue.

All other issues look to be poorly defined or configuration issues (or just old...).

Stevel’s picture

Stevel CreditAttribution: Stevel commented
Status: Active » Needs review

https://www.drupal.org/node/2377727
This looks important, but I haven't had a chance to test locally. If the Drupal session is being killed, this shouldn't really be an issue. Killing the entire SSO session shouldn't be the job of this module, correct? We redirect to a global logout.

The user is properly logged out. The 'problem' is that a session cookie still exists, causing external caches to 'miss', so it's a performance issue only.

https://www.drupal.org/node/2681159
I haven't experienced this issue with simplesamlphp 1.14.2. Perhaps the issue is with simplesamlphp. So this may just be a "need to update" or configuration issue.

I can confirm it works with 1.14, so this looks like a configuration error as well.

Setting this to 'Needs review'.

DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna at Mediacurrent commented
Title: Final release for 7.x-2.x » Plan for simpleSAMLphp Authentication 7.x-2.0 release
Version: 7.x-2.0-alpha2 » 7.x-2.x-dev

Standardized the title.