Sorry about that Bruce, and excellent feedback. I apologize about the missed notifications. That was my fault. I'm nervous about inundating my customers with too many messages, so I've chosen not to send updates when I felt the changes were not critical. I have somewhat of a unique situation in that metaPost is really comprised of many different dlls that are all versioned separately. If I make an update to the Text/HTML provider, I don't rev the version of metaPost. Of course, I've also recompiled the core without reving the minor revision number when I felt the change was just a minor improvement. That was the case on 6/28, but I’ll make sure in the future to increase the minor revision number if any changes are made to metaPost. I’ll do the following to help address this issue:
- Create a version history page and link to it from the main metaPost page.
- Post the current version of metaPost and each provider on the main metaPost page.
- Configure RSS on the version history page for those that want to keep track of all updates.
In order to ensure that the messages from Snowcovered are meaningful, I'll continue my current approach of only sending notification for releases which contain actual bug fixes or enhancements I would like everyone to know about. This way, you know if you get an email from Snowcovered regarding metaPost, it’s an update we think is worth the time to download.
Will this work? If not, please let me know. I’m open to suggestions. My goal is to make metaPost as easy to use and maintain as possible and this kind of feedback is really helpful.
Thanks!
Don