8.x-1.0 release plan

Created on 12 October 2021, over 2 years ago
Updated 2 February 2023, over 1 year ago

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 8+, just a -rc2. There are many benefits to publishing a stable release for a module.

Release-blocker issues

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 above issues blocking the release of a stable release.
  • Craft changelog for new release.
  • Create new release.
🌱 Plan
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States Webbeh Georgia, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States richgerdes New Jersey, USA

    I did just release 1.0-rc3 β†’ today, which should address the biggest concerns, adding a few of the RTBC and bugs with patches along with Drupal 10 support. If there are no major issues, I think that should be the last RC and we should make a full release soon. I would like to see at least #2928938: Prevent editing/deletion of inuse composites. β†’ solved before we have a full 1.0.

    @joseph.olstad, the main goal of this module is to provide a complex web ui configurable element, which can be reused across multiple forms. The base module does provide the idea of a composite, and lets the user build one with code, but this isn't ideal for non developers, which is why the module was born. I had hoped it might also be the home to other webform related tooling if anything helpful came up in the future.

    @svendecabooterm, thanks for interest in helping maintain the project. I would be open to adding someone if you are still interested. I haven't been using this module as heavily recently so haven't gotten back to it as much, so another set of hands who's actively using it would be a great addition. I'd still be open to help if you want to. I'm not always looking over issues or the emails for them, but feel free to ping me on slack if you are still interested and I don't get back to you right away.

  • πŸ‡ΊπŸ‡ΈUnited States richgerdes New Jersey, USA

    I'm also adding #3182180: No support for defining a default value for a field of a composite β†’ to the list of things to add. I think we should address that as well.

Production build 0.69.0 2024