I worry sometimes when announcing something completely new (we’re working on a few things!) that people will misinterpret my priorities… Yes, I love adding new features, but I’m also fixing bugs. We deploy Micro.blog multiple times a week with little tweaks.
@manton I think there are ways to solve this -- mostly with better and more obvious messaging -- but obviously the priority should be fixing the bugs rather than talking about them. It's also probably just one of those points of tension that all smaller products have whilst growing.
@manton From my perspective, your releases are impressive. There’s a lotof new functionality for a service run by a small team. Plenty! 🙂 We get that you need to prioritize.
@manton A changelog.micro.blog could be a nice reference. Simple bulleted list of New additions, Bug Fixes, Tweaks, Deprecated.
@Burk Good idea. It would be nice if I could take our GitHub check-in history (for all repos, private and public) and make it available. Maybe just as a page on news.micro.blog.
@manton I think it's a matter of getting the word out on the tweaks. Personally, I like reading change log when apps have an update instead of the generic "bug fixes and improvements". Also, not sure if you want to be that open like David Merfield who maintains this News page for Blot.
