I’m almost ready to release a new version of swaks which includes a few new features and some bug fixes. The last change I made involved a change in the code which reads text from the server. All of my testing indicates that the code is right, but my available testing platforms aren’t as varied as they used to be. If you are able, please download and test. Feel free to share the link as much as you want, but please don’t package it yet. If no one reports anything serious I’ll release the “real” version in a week or so.
Here are links to the script and the Changelog for this version:
LINK REMOVED – this was a development release and the changes have been incorporated in official releases. Please see the project home page at http://jetmore.org/john/code/swaks/ for the latest release.
I don’t have a pretty version of new features or bug fixes yet but the Changelog can be trawled for a decent overview.
Any testing notes or last minute requests can be dropped as a comment here if you want, but they are most useful as an email to email@example.com.
I’ve never been especially proactive in evangelizing swaks, but its usage number have grown to the point in the last 10 years that I think I probably am probably hurting users by not having more communication channels to receive and provide updates. So, here’s a quick breakdown of what channels exist right now, and where I want to go in the future
- Website – http://jetmore.org/john/code/swaks
- Update list – There’s no UI for this, but emailing firstname.lastname@example.org and asking to be notified of new releases will get you on the notify list.
- I don’t really have any desire to run a mailing list myself but there have been some requests for one (which I assume would be very, very low traffic).
- swaks.net – I own this domain, at some point in the future I think it makes sense for the swaks distribution to move to it.
- Trac – swaks’ “todo” list is not huge, and not especially hard to hold in my head, but I like the idea of Trac or something similar because of its ticket/commit cross reference and the timeline to help remember the history of the development. Not sold on this being worth the effort of maintaining yet.
If there’s some specific thing you’d like to see from swaks, whether it’s a communication channel or a feature/bug, please let me know in the comments or via email (email@example.com).