This META issue will be used to reference those issues that need to be fixed before a 8.x-1.0-beta can be released.

The criterion for beta blockers:

  • API changes
  • Automated testing

Comments

mpotter created an issue. See original summary.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Status: Active » Needs review

We've made a lot of progress in the 2 and a half months since we opened this issue. Is it time for a beta release?

The major refactoring that introduced data model changes is now behind us:

Up to now, we've made data model changes without supporting upgrades, meaning that Features has been so unstable as to be practically unusable.

We've also made a lot of progress on the test coverage front.

We don't yet meet all the beta targets we set. There's a lot more test coverage to go, and a ticket for config schema, #2392561: Add configuration schema. Neither of these seems likely, though, to change the data model.

I'm wondering whether, In the interests of allowing people to start really using the module, it's time to start supporting an upgrade path and issue a beta release.

@mpotter, @dawehner: thoughts?

dawehner’s picture

dawehner
Primary language German
commented

I agree with a beta, given that we have at least some form of general test coverage. 

              |    |    |
             )_)  )_)  )_)
            )___))___))___)\
           )____)____)_____)\\
         _____|____|____|____\\\__
---------\                   /---------
  ^^^^^ ^^^^^^^^^^^^^^^^^^^^^
    ^^^^      ^^^^     ^^^    ^^
         ^^^^      ^^^
nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Status: Needs review » Active

Setting back to active pending work on the next alpha release, #2651708: Issue Features 8.x-3.x-alpha6 release.

mpotter’s picture

mpotter commented

So we are close here. I'd like to see the remaining "Major" issues resolved:

That would leave these related "Major" issues which are probably beyond a Beta schedule unless somebody has more time:

In that first list, we have patches and most are looking good but they are marked as "Needs work" because our automated tests are not passing. If we can figure out which test is failing and get that fixed then I'd be willing to roll out a Beta with just the current test coverage.

mpotter’s picture

mpotter commented

Updating this list. The remaining Major items are:

The configuration schema issue depends on the work in the "New assignment plugins not registered" issue where the plugin annotations are being used for default settings which might remove some config settings from Features itself.

The last issue regarding FeaturesBundle might require more work than we can do for beta, so need to decide if it's really "Major" and API-changing or not.

mpotter’s picture

mpotter commented

Moving #2392561: Add configuration schema and #2621658: FeaturesBundle should implement EntityWithPluginCollectionInterface to Normal non-beta status.

Adding #2697867: Installed Package in a bundle is shown as not-exported. Once that passes tests then I'll roll the beta.

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented

According to https://www.drupal.org/project/issues/search/features?text=&assigned=&su... there is one old issue

Checking for majors there are 2 open https://www.drupal.org/project/issues/search/features?text=&assigned=&su...

Checking the child issues I count 4

/me puzzled

mpotter’s picture

mpotter commented
Status: Active » Fixed

As you said, the first was an old issue and just pointed to the related Testing issue. The Testing issue is a Meta issue to collect other testing issues and we decided there was enough test coverage to warrant a beta release.

All of these issues were discussed during the weekly Features 8 IRC meeting and we decided the remaining issues were no longer major and not blocking a beta release, so the beta was released last Friday.

Now this issue is also closed and we can just continue to work on bug fixes as needed to get to a stable release.

clemens.tolboom’s picture

clemens.tolboom
Primary language Dutch
Location Groningen, 🇳🇱/🇪🇺
commented

We have a beta1 :-) ... tnx

Status: Fixed » Closed (fixed)

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