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 9+. There are many benefits to publishing a stable release for a module.
Release-blocker issues
Finish #3151618: $webform_data is null- we need more information on how to reproduce this issue.Review and consider #3145769: Changes will not save if draft did not exist when page loadedReview and consider #3192372: Optimistic locking errors in multistep formReview and consider #3191482: Support webform-multiple itemsReview and consider #3262559: Update code-base using PHPStan- Review and consider #3274705: Doesn't work when user is Limited to single submission
Good-to-fix issues
Above and beyond tasks
Remaining tasks
- Establish a list of release-blockers and 'good-to-fix' issues for a stable release.
- Resolve the above issues blocking the release of a stable release.
- Craft changelog for the new release.
- Create a new release.
Issue fork webformautosave-3211488
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
rymcveighI think it would be good to add some code style cleanup before we release the module as well. I feel like that could be added to this issue so I'll create an MR.
Comment #4
rymcveighComment #7
rymcveighAdjusting the title to reflect the new versioning system.
Comment #9
gregglesIf we want to switch to a 1.0 style numbering I think we'd have to create that as a new branch in git and new series of releases on drupal.org. We could definitely consider doing that.
Comment #10
rymcveighChanging to be version 2.x because composer may interpret the current release as 1.x in some folk's composer.json files.
Comment #11
rymcveighComment #12
WebbehComment #13
rymcveighUpdated the description using this template: #3239062: 'Stable Release Request' Issue Template
Comment #14
rymcveighComment #15
rymcveighComment #16
rymcveighI tested this with the following webform setup:
Comment #18
rymcveighComment #19
rymcveighComment #20
rymcveighComment #21
rymcveighComment #22
rymcveighComment #24
rymcveighThe most recent MR is ready for review. I created a new one. The "PHP 8.1 & MySQL 5.7, D9.4 2" test is the valid test for the MR.
Comment #25
gregglesMR LGTM.
Comment #27
rymcveighThanks for the review @greggles. The MR has been merged in and a stable release has been created.