Problem/Motivation

The intent of this issue is to help the maintainer(s) coordinate community efforts in the creation of a stable release. Community involvement is only intended as a suggestion; it is up to maintainers to ultimately decide the creation of, and what goes into, a stable release. If you are not interested in using this issue, please mark the issue as Fixed or Closed (works as designed).

As of the creation of this issue, this project presently does not have a stable release compatible with Drupal 10+. There are many benefits to publishing a stable release for a module. Project Browser uses stable releases as a recommended criteria for module discovery (#3240314-16: Decide on algorithm for "recommended" modules).

Maintainers should enter tickets as #123456: Drupal website oupedia.com with imported joomla template to take advantage of drupal.org issue linking and status highlighting.

Release-blocker issues

Good-to-fix issues

Above and beyond tasks

  • Create an issues-fixed list for stable release using the drupalorg-cli tool.

Dropped issues

Remaining tasks

  • Establish a list of release-blockers and 'good-to-fix' issues for a stable release.
  • Resolve above issues blocking the release of a stable release.
  • Create a release tag.
  • Craft changelog for new release using https://drupal-mrn.dev.
  • Create new release.
  • Update the project page, and documentation.

Do you have resources you'd like to contribute to this template? Have feedback on the stable release request issue template? We want your feedback: #3239062: 'Stable Release Request' Issue Template

Original issue summary

Problem/Motivation

We've bumped the development branch from 8.x-1.x to 2.0.x-dev. We have adopted several tickets recently to get this project up to par. Now, we need to consider whether to publish a release.

Proposed resolution

Consider whether to publish a release.

Remaining tasks

  • Review the release candidate for Drupal 9 and Drupal 10 compatibility.
  • Review the release candidate for production viability.
CommentFileSizeAuthor
#4 Screencast 2022-08-09 20:35:18.mp42.81 MBomkar-pd

Comments

jcandan created an issue. See original summary.

jcandan’s picture

jcandan commented

I know several in the community are using 8.x-1.x-dev in production.

Please make the upgrade to the latest release candidate and report back here with your feedback.

omkar-pd’s picture

omkar-pd commented
StatusFileSize
new Screencast 2022-08-09 20:35:18.mp42.81 MB

Tested the latest version on 9.4.1. Found a couple of issues.
1. The invalid number/too long/too short number is getting saved.
2. Cannot get the selected country when editing the node.

Check attachment.

omkar-pd’s picture

omkar-pd commented
StatusFileSize
new Screencast 2022-08-09 20:35:18.mp42.81 MB

Tested the latest version on 9.4.1. Found a couple of issues.
1. The invalid number/too long/too short number is getting saved.
2. Cannot get the selected country when editing the node.

Check attachment.

jcandan’s picture

jcandan commented

With this release, it will include README changes that will need to be published to the project page.

See #3524990: Update the composer process.

jcandan’s picture

jcandan commented

@omkar-pd, #3143446: Flag not selected on node editing form forces user to re-select and #3525118: Prevent save on invalid phone number value capture the concerns noted.

jcandan’s picture

jcandan commented
Title: Release 2.0.0 » Telephone International Widget 2.0.0 stable release plan
Assigned: Unassigned » jcandan
Category: Task » Plan
Issue summary: View changes
Status: Needs review » Active
jcandan’s picture

jcandan commented
Issue summary: View changes
jcandan’s picture

jcandan commented
Issue summary: View changes
jcandan’s picture

jcandan commented
Issue summary: View changes
jcandan’s picture

jcandan commented
Issue summary: View changes
jcandan’s picture

jcandan commented
Issue summary: View changes
jcandan’s picture

jcandan commented
Issue summary: View changes
jcandan’s picture

jcandan commented
Issue summary: View changes
jcandan’s picture

jcandan commented
Issue summary: View changes

Removed #3525118: Prevent save on invalid phone number value as a release blocker. Willing to consider putting it back in. Awaiting community feedback.

jcandan’s picture

jcandan commented
Issue summary: View changes

Added #3525670: Bump supported intl-tel-input version. Seems appropriate to get the front-end package dependency a good solid update before a major release.

When 2.0.0-rc2 gets released, it will introduce breaking changes (changes that require consuming applications to make code modifications to continue working correctly with the new version). While release candidates may be considered close to stable, this update is long overdue, and introducing breaking changes on a release candidate isn't strictly forbidden. We'll be sure to communicate this in the release documentation for RC2.

jcandan’s picture

jcandan commented
Issue summary: View changes
plopesc’s picture

plopesc
he/him
Primary language Spanish
commented

Create an issues-fixed list for stable release using the drupalorg-cli tool.

https://drupal-mrn.dev/ is a simple alternative that will make your life easier :)

jcandan’s picture

jcandan commented
Issue summary: View changes

We're close. Adding a CI code standards error fix.

jcandan’s picture

jcandan commented
Issue summary: View changes
jcandan’s picture

jcandan commented

Will follow #16 and proceed with an rc2 release when #3568806: [CI] Fix formElement references an invalid method is complete.

jcandan’s picture

jcandan commented

@omkar-pd, can you comment on #3525118: Prevent save on invalid phone number value and let me know if the concern there is addressed by Telephone Validation?

jcandan’s picture

jcandan commented

Released 2.0.0-rc2. Placing in Needs Review to get community feedback. Unless a bug is reported, I hope to publish a 2.0.0 release in the next 2 weeks.

jcandan’s picture

jcandan commented
Status: Active » Needs review