"VERSION = X.Y.Z
X = major release number (MAJOR) – not backwards compatible
Y = minor release number (MINOR) – backwards compatible, additional
features
Z = patch/bug fix number (TINY) – small bug fixes"
That got me thinking about my own version numbering policy and I
quickly realised that I didn't really have a sensible one. So I've
decided to adopt Dr. Nic's suggestion and rename the release formerly
known as 0.5.4 to 0.6.0 because there are changes that are not
backwards compatible, namely -
1. Queue#subscribe passes a hash of message data
( { :header, :payload, :delivery_details } ) to its block instead of
passing the message payload by default. The method also handles
acknowledgements slightly differently.
2. Queue#pop and Client#returned_message both return a similar hash
the one used in Queue#subscribe.
If this is the first time that you are hearing about these changes
then I apologise for not being able to think of a better way to
announce them, but I have posted about them on this list before.
I hope that this renaming will not cause any problems, however I'm
sure that I'll be informed if it does. I'm working on a command line
interface for Bunny at the moment and will make that available in
v0.6.1. If you keep an eye on my next_release branch on GitHub (after
today) you can get a preview of it as it evolves and perhaps give me
some feedback :)
Thank you for your continued support,
Chris Duncan (a.k.a. celldee)
_______________________________________________
bunny-amqp-devel mailing list
bunny-am...@rubyforge.org
http://rubyforge.org/mailman/listinfo/bunny-amqp-devel