It seems that the 4.x has been released and 8.x-3.x support is dropped. Thanks for your effort to keep the module maintained!

The Password Strength module extends the Password Policy module, so we need to update our requirement (see issue #3320918: password_policy bumped to 4.x).

I wanted to know: why was 8.x-3.x support removed? It seems that 8.x-3.x could be supported for a bit longer while folks migrate to 4.x?

What is the purpose of the 4.x branch? Will the Password Strength and other similar modules need to change their code to support 4.x?

Thanks in advance for your help.

Comments

greggles created an issue. See original summary.

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented

@greggles, there is not much besides some bug fixes and D10 support from what I can see.
https://git.drupalcode.org/project/password_policy/-/compare/8.x-3.2...4...

Nothing that looks like it needs an upgrade path.

daften’s picture

daften commented

But, if I may ask, why was a new major version released then? Based on semver, that should only be done for backwards incompatible changes. Adding D10 support does not fall in that category.

eelkeblok’s picture

eelkeblok
he/him
Primary language Dutch
Location Netherlands 🇳🇱
commented

One (fairly good, IMHO) reason might be to actually be able to use semver, because the old versioning scheme is not (semver, that is; unfortunately it is not possible - AFAIK - to move to semver within a major version, i.e. move from 8.x-3.2 to 3.3.0). However, some guidance about this would be very helpful, especially because a major jump is not usually picked up by a composer update and requires extra action on the part of a person applying maintenance to a site.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

I agree with #4 that a move to semver can be a worthwhile reason and that would also be part of why it makes sense to drop support for the old 8.x-3.x relatively quickly. It would just be good to state that explicitly so folks know that an upgrade is a low-risk operation.

As it stands, the project page and release node don't explain the philosophy of the 4.x branch.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Status: Active » Fixed

I've updated the project page to capture this information:

https://www.drupal.org/project/password_policy

Feel free to reopen this if it's not sufficient.

Status: Fixed » Closed (fixed)

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

eelkeblok’s picture

eelkeblok
he/him
Primary language Dutch
Location Netherlands 🇳🇱
commented

Looks great. If I can just chime in here again, I think it would be a good idea to add the same information to the 4.0.0 release notes. When running into major updates, this is usually my first stop to see if there is anything I should be aware of. Granted, my next stop would probably be the project page, but by then I am already in "investigation mode" :) Probably a good idea to repeat that info for any subsequent patch releases as well.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Version: 4.0.0 » 4.0.x-dev

Thanks @eelkeblok. Please open a new issue with what you'd like included. Thanks.