Create stable release of 8.x-2.0

Seems likely that these two can be RTBC and committed soon so I'd like to definitely wait for them.

* #2393873: Use current account rather than global $user in user_profile_form
* #2297471: Verify that passwords are matching on the frontend

While not required I'd also like to try and get in #2298875: Fix styling issues for password strength text

Beta1 has been made https://www.drupal.org/node/178881/release

For 6.x I'm going to have to create a new branch 6.x-2.x to avoid any confusion with the old project functionality.

@ben/@greggles, have you thought of also aligning 7.x, and switching to 7.x-2.x as well? in a sense, we're giving this namespace a second life, so I think this would make sense (and keep in sync with D6 too).

I don't think there's a lot of confusion by having a 6.x-2.x and a 7.x-1.x so long as the documentation states that they're compatible and now that there is already a 7.x-1.x-beta1 I think moving it to a 2.x would create more confusion. @scor have you seen/heard of difficulties in projects having different minor branch identifiers cross major branch? I recall that confusion with Views but I think Password Strength is small enough to not have that.

if we were to make that change/alignment, now would be the time with only a dozen install of password_strength beta1. I don't have any example to backup my claim, only common sense. What does greggles think?

cool, let's continue with 7.x-1.x and 6.x-2.x then...

Looks good. Just wish I had more time to contribute :( will do my best...

updating summary

Apologies if this would be better as a new issue.

At the moment, the 7.x and 8.x recommended releases are both a long way behind:

$ drush rl password_strength
 Project            Release         Date         Status                 
 password_strength  8.x-2.x-dev     2016-Dec-05  Development            
 password_strength  8.x-2.0-alpha1  2015-Oct-20  Supported, Recommended

$ drush rl password_strength-7.x
 Project            Release        Date         Status                 
 password_strength  7.x-1.x-dev    2016-Oct-28  Development            
 password_strength  7.x-1.0-beta1  2014-Dec-20  Supported, Recommended

In particular, 8.x-2.0-alpha1 pre-dates #2633090: Remove dependency on Composer Manager, so projects which don't want to include the (deprecated) composer_manager module are forced to patch or use the dev version.

For a security-oriented module, it would ideal to have stable releases so that password_strength was covered by the security advisory policy.

Is there anything in particular holding back stable releases for the 7.x and 8.x branches (not sure if the original issue summary here is a little out-of-date)?

It would be good to tag new releases even if they're still alpha/beta/rc.

Thanks @greggles, that's great.

I'll try to have a comb through the issue queue for 8.x

What is the status of this module, is anyone at the helm currently? I agree with previous comments about the importance of security coverage.

This module's latest release is over a year old and still a beta. Is there an ETA on when the full release can be cut?

#3320918: password_policy bumped to 4.x cross posting because I think it's a quick fix and likely needs to get in (or some variant of that MR) before a stable release.