Comments

greggles created an issue. See original summary.

greggles’s picture

Issue summary: View changes

Thinking more on this and I'm not sure we should hold it back until 2935622 is fixed. That change is potentially valuable and worthwhile and also disruptive (making it a good candidate before 1.0). However...I'm not likely to work on it and we've lived a long time without it, so...seems OK to push.

greggles’s picture

Issue summary: View changes
greggles’s picture

Issue summary: View changes
andypost’s picture

Issue summary: View changes

I'd like to get in
- #2856542: [2.x] Allow authentication via mail and password over RPC as it has tests bet needs more eyes
- #2987060: Commerce 2 Completion Registration checkout pane looks ready but have no preference on implmentation

greggles’s picture

Thanks for your thoughts, andypost!

Both of those feel like they'd be fine to wait for after 8.x-1.0.

I feel like I should create a 8.x-1.0-rc7 very soon (like right now), commit #3034828 just after, and then plan on the 8.x-1.0 in 2 weeks if there are no new criticals. What do you think of that plan?

andypost’s picture

rc7++ right now and 2 weeks should be enough

andypost’s picture

Issue summary: View changes
greggles’s picture

OK, I created https://www.drupal.org/project/email_registration/releases/8.x-1.0-rc7

@andypost I'd love your review of 3034848 if you can.

andypost’s picture

greggles’s picture

Issue summary: View changes
greggles’s picture

Issue summary: View changes

Adding a commerce related fix that seems like a critical bug to me. Luckily it has a good patch.

andypost’s picture

I think it ready to be commited with composer fix only #3084055: Email Registration breaks commerce panes on old versions of commerce

the remaining deprecations could be split to fix obvious ones and the remains after release which we could target to 8.7.7 and declare d9 support

greggles’s picture

I'm open to that plan laid out in #13. Do you think we need one more stable release or just another ~week for any feedback/bugs to surface and then create the 8.x-1.0 final?

andypost’s picture

andypost’s picture

greggles’s picture

I think it could be good to make a 1.0 release with the current state of the code.

The changes in 3037323 and 423920 seem good, but we should ship a 1.0 for folks to use and those don't seem to be 100% ready just yet.

It's been 2 weeks since the last commits and no new issues are opened. I plan to do a 1.0 if there are no objections in the next few days.

andypost’s picture

Status: Active » Reviewed & tested by the community

Yes, that's perfect time!

greggles’s picture

Status: Reviewed & tested by the community » Fixed
Chris Matthews’s picture

Thanks so much!

Status: Fixed » Closed (fixed)

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