Problem/Motivation

We finally have a stable version of Drupal 8! Even after two years of development, however, we still don't have a stable version of Flag. While the dev version is "stable enough" for use, we still do not support upgrades within the 4.x version. Not even having an alpha is a barrier for many users.

Proposed resolution

Create an alpha release ASAP, even if it has outstanding criticals, kluges, or regressions. It's an alpha, after all, and this is more about saying "Yes, please use Flag!" than making it perfect.

Remaining tasks

  • Identify which issues are preventing an alpha release.
  • Create a Flag alpha release as soon as possible, and begin to support upgrades within the 4.x version.
  • Work to resolve criticals, major regressions, and missing features during the alpha process.
  • Release betas when Flag hits zero criticals and zero missing features.
  • Identify which issues, criteria, load testing, or waiting period need to be resolved before releasing 4.0.
  • Have some Irish Coffee or something.

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Comments

socketwench created an issue. See original summary.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented

+1 to releasing an alpha version yesterday ;)

socketwench’s picture

socketwench CreditAttribution: socketwench as a volunteer commented

Me too. I can't think of anything that'd prevent us from doing an alpha today, but I've been absent for months due to events and burnout.

emclaughlin’s picture

emclaughlin CreditAttribution: emclaughlin at Genuine commented

I'm fairly new to the project, but in my testing and poking around I haven't found anything that would prevent an alpha version from being released, heavy emphasis on the "alpha" part.

Nope, I take it back, Field Entry flags are weirdly janky in ways that result in errors when you try to delete them. They delete! But you get weird errors all the same.

joachim’s picture

joachim CreditAttribution: joachim commented

> While the dev version is "stable enough" for use

It really isn't! Look at the criticals list!

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented

Not stable stable but it really is working well enough ;)

The critical list isn't that bad, not bad enough to not release an alpha version and core actually mode some improvements that should allow us to fix at least one. Rerolled the patch.

joachim’s picture

joachim CreditAttribution: joachim commented

Field entry UI is totally broken, our access system is broken, and link output doesn't work in some places...

If you guys feel an alpha in this state is ok, and that it would help get more people helping, then fair enough.

socketwench’s picture

socketwench CreditAttribution: socketwench as a volunteer commented

I want to side with Berdir, but now that I've looked at the criticals I think we need to at least fix #2409673: impossible to uninstall Flag before releasing Alpha 1. I consider this a "site breaking" bug. We don't want that in an alpha.

As a compromise, I also suggest including a warning on the Field Entry Link Type marking it as "Experimental" until we fix #2607766: flags using field entry link type can't be unflagged.

Furthermore, disable the options to attach Flags on the Entity Edit Form, with the hope we'll fix it in the alphas. #2497187: [regression] "Display checkbox on entity edit form" not implemented - hook_field_attach_form removed in D8

The other criticals I'm much less concerned about for an alpha. They must be fixed before the betas though.

joachim’s picture

joachim CreditAttribution: joachim commented

I don't really want to disable things in the UI or mark them as experimental, especially when they're core functionality. It's an alpha, and alpha is Latin for 'doesn't work', and people can read the release notes for that sort of thing.

socketwench’s picture

socketwench CreditAttribution: socketwench as a volunteer commented
Title: [Plan] Release Flag 8.0-4.0 » [Plan] Release Flag 8.1-4.0

At this point it might as well be 8.1.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented

Note that there's no such thing as 8.1-4.0. It's 8.x-4.0.

If you do depend on a specific minor version because you e.g. use a new interface or so, then you need to add a version dependency on the system module: - system (>=8.1.0).

But I don't think that's the case right now.

socketwench’s picture

socketwench CreditAttribution: socketwench at FFW commented
Title: [Plan] Release Flag 8.1-4.0 » [Plan] Release Flag 8.x-4.0

Good point!

ksenzee’s picture

ksenzee
she/her
Location Seattle area
CreditAttribution: ksenzee at Smartsheet commented

Looks like there's only one open critical left, which is #2475893: Support for Flagging by anonymous users. Maybe an alpha would be okay now?

martin107’s picture

martin107 CreditAttribution: martin107 commented
Issue summary: View changes

Marking alpha related tasks as done.

mmjvb’s picture

mmjvb CreditAttribution: mmjvb as a volunteer commented
Issue summary: View changes

As there are beta's released assume it can be marked as done. Don't know about criticals or missing features.

zenimagine’s picture

zenimagine CreditAttribution: zenimagine commented

It will be necessary to think of changing the version by deleting 8.x-

neclimdul’s picture

neclimdul
He/Him
CreditAttribution: neclimdul at APQC commented

Critical issues seem to be long dealt with. The major related to this seems important to some use cases so not sure if that's blocking the final release.

Would be nice to get another beta though with D10 support to help with upgrade testing.