Replies: 1 comment 1 reply
-
|
You are right. This is mostly on me. I like moving fast and trust the documents will catch up. It's a huge effort on documentation and @Jutanium is working on it, along with the dozens of people working on translations but I don't usually wait on that stuff. I did for 1.0 which was a necessity, but it also pushed things off weeks. To be fair @Jutanium wanted to meet up this week to talk about the new stuff in 1.2.0 but I pushed it off since I have 2 conference talks and a stream I need to prepare for on top of being an incredibly busy time at work. In general, I think we need better information around patch releases. I always give minors a treatment but it would be valuable to generate changelogs for patches as well. I am not as familiar with tooling that automatically does that but I know it exists. I'd like to see docs keep up but I'm hesitant to push back releases for it. I imagine people have different opinions here so I'd love to hear your thoughts. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
While it's great to see Solid's new minor releases with exciting and significant(!) features, the official website contents (landing page, guide, docs, tutorial, etc.) seem to be lagging behind the changes.
I was originally going to create an issue on the
solidjs/solid-docsrepo, but then thought it might be worth raising the issue here as a discussion since it might be related to a broader topic of Solid's release process. I know this is much easier said than done, but I believe the release process requires more coordination between the core libraries and the official contents.Beta Was this translation helpful? Give feedback.
All reactions