As we're getting really close to a release I thought it'd be good to make a list of remaining tasks to be done. Sort of like a release checklist like we had back in the ceviche repo before we went public. I think it helped us a lot in the final weeks.
I compiled a list of PRs that I think are a _must_ have for the final release. We should be careful here not to fail victim of feature creep. It's not like will stop publishing releases after that. Instead we'll continue cutting new ones in our usual 2-3 weeks cycle.
Releasing X will ease our maintenance burden quiet a bit as we can finally deprecate preact-compat (it has moved to core at preact/compat) and allow the ecosystem to adapt.
PRs:
hydration #1697Suspense for SSR https://github.com/preactjs/preact-render-to-string/pull/92~~Docs:
Release:
preact-router@next as latestpreact-render-to-string@next as latestpreact-jsx-chai for X https://github.com/developit/preact-jsx-chai/pull/70cc @andrewiggins @JoviDeCroock @developit @ForsakenHarmony @cristianbote
Forgot to add: PRs like the new devtools adapter can easily land in a point/patch release. My thinking here is that even the extension itself is still marked as experimental so we could release it under the "preview" umbrella. I still need to write more tests for it though.
I'd say this is a good issue to point to for our docs: https://github.com/developit/preact-www/issues/286
I'd propose splitting it up, when our crucial PR's are done we can publish RC.0 and when we feel the docs are on point the final release.
@pmkroeker Anything on the TS side you'd want to add?
Not that I can think of off hand. The biggest thing is to remind library authors that JSX will now need to be imported if it is used in their typings.
Closing, Preact X was released a while back :tada:
Most helpful comment
Not that I can think of off hand. The biggest thing is to remind library authors that JSX will now need to be imported if it is used in their typings.