This has been a really tough release.
Support for Atom 1.0 is now complete. Converting the Atom 0.3 parser to support 1.0 only took about two days and I was quite pleased with myself that the code was so well-designed that this work could be done so quickly :-). But upgrading the rest of Awasu to handle the implications of this took quite a bit longer... 🙁
See folks, we now have a syndication format that lets publishers unambiguously state whether content is plain-text or HTML. With RSS feeds, you have no idea what anything is and so when it comes time to look at that content, Awasu has no way of knowing how to present it. Most of the time you can get away with it (which is why this state of affairs has lasted as long as it has) but there are common situations where it just doesn't work.
With Atom 1.0, Awasu now has the information it needs to do the job properly. The template processor, in particular, is now much smarter about how it does things. It looks at the type of each piece of content it's inserting and intelligently encodes it according to the type of output it's generating (HTML, XML, plain-text, etc.).
For the non-techies amongst you, the executive summary is this: things now Just Work™ (assuming you're using Atom 1.0).
Another major change is exposing some of the key design concepts we built into Awasu when we implemented the content archiving system. I hinted earlier about how Awasu manages metadata and this is now all available via some new template parameters. This lays the foundations for some powerful new features in the next release (note to Earl: remember asking me ages ago about being able to extract Furl-specific information out of Furl feeds? This is it :cool:).
Like I said, this has been a really tough release and I'm so looking forward to getting back onto some fun stuff... 🙂