Release v2.0.0

[armanbilge]

We're right at the finish line! The outstanding PRs are:

• The great migration to dom #588: reviewed by @japgolly, needs a final review
• Use opaque types for Scala 3 #592: reviewed by @sjrd, based on The great migration to dom #588
• Improve HTMLCollection, add HTMLOptionsCollection and HTMLFormControlsCollection #593: basically ready, let's get this one in as well

The only other issues in the 2.0.0 milestone are internal and don't have binary or source compatibility implications, so I don't think we should block on those.

Is there anything else?

I don't mean to be impatient or pushy, there's no real rush of course. But speaking personally I'll be very happy to have this weight off my shoulders and see all of our efforts come to fruition. And importantly start the process of propagating this change through the ecosystem.

[armanbilge]

I've set a (tentative) due date on the milestone for next week.

[sjrd]

FYI, I will be on vacation the week of October 25. I don't think you'll need me for the release at all, but just in case. ;)

[armanbilge]

Well I did goof it up once before 😳 thanks for letting me know. In theory we can release anytime this week (all the aforementioned PRs are ready), I am hopeful David will chime in with his blessings/objections :)

[japgolly]

Hello. Sounds great, let's get this release out. My only contribution to the plan is that I think it'd be a good idea to do an RC first. One reason is that the new release process is still new, another reason is that I'd love to try it in a big app, make sure everything works as expected and all tests pass, so that if there are any mistakes we've made, hopefully we catch them in time before locking ourselves into bincompat for the entire 2.x series. Actually it might be a good idea to let the community do the same.

[armanbilge]

Thanks for chiming in! Hope all is well ❤️

Yes, I think doing an RC is not a bad idea. Actually we've been publishing snapshots all along so I was planning to try PRing laminar against one of those snapshots. But an RC works too :)

I'd be shocked if there aren't any mistakes, but I would be surprised if there is a mistake with bincompat implications.

[armanbilge]

FWIW, what I'm most concerned about re binary compatibility, is making sure we loudly communicate that downstreams should remove the for3use213 from their build configs. Because it is far too easy to merge a Scala Steward update to SJS-dom v2 without paying attention to this. And this would have as bad binary compatibility implications just as if we just published SJS-dom v1 for Scala 3.

[japgolly]

Yeah very good point! Maybe a big bold instruction at the top of the release notes?

Thanks for chiming in! Hope all is well

Thank you! Unfortunately it's just bad news after bad news. Funny thing is that I have unrelated appt next month that about something that could be cancer which, I think at this point I'd just laugh and say ggs. I'll probably be fine eventually though. Unfortunately for my OSS contributions I might be a bit randomly flakey for a while. I am sorry about that but not much I can do. Looks like you've been doing awesome work so as both a co-contributor and as an end-user, thank you!!

[armanbilge]

I am so sorry to hear that 😢 I certainly don't want to pile on, and hope that I haven't by pushing for this release. Just let me know.

[japgolly]

Oh my bad, no, no, not at all. Nothing like that :) When I have a bit of capacity I like to pop in and do what I can. No pressure :)

[armanbilge]

Anything else? Should we cut an RC?

[armanbilge]

I just tried building raquo/scala-dom-types against 8a2d8f6. It was ... extremely easy. Didn't have to make any changes or even get any deprecation warnings, because it was already using the dom.* aliases defined in v1.

[japgolly]

Should we cut an RC?

Yeah let's do it! In fact, I'll do it now...

[armanbilge]

Nice! I am currently looking through SJS-dom's downstream dependencies to try and figure out what important projects to help along with a PR.

https://mvnrepository.com/artifact/org.scala-js/scalajs-dom/usages

[armanbilge]

Downstreams to test with RC:

• Update to sjs-dom 2.0.0 final raquo/scala-dom-types#72
• Update to sjs-dom 2.0.0 final raquo/Airstream#91
• Update to scalajs-dom 2.0.0 com-lihaoyi/scalatags#225
• Update to sjs-dom 2.0.0 final softwaremill/sttp-model#126
• Update to sjs-dom 2.0.0 final shadaj/slinky#511
• Update to sjs-dom 2.0.0 final lemonlabsuk/scala-uri#369
• Update to sjs-dom 2.0.0 http4s/http4s-dom#23
• Upgrade scalajs-dom to 2.0.0-RC1 japgolly/scalajs-react#995
• Build/test against sjs-dom 2.0.0-RC1 ScalablyTyped/Converter#373
• what else?