Here's a preview of the 0.16 release notes:

  http://people.apache.org/~jross/release_notes_0.16.html

I'll regenerate this before GA. Until then, you can adjust jira titles and categories to spruce up the release notes.

Note to developers: jiras 3937, 3938, 3901, and 3919 don't appear in the preview notes because they are not marked fixed or don't have their fix version set. I'm repairing this now. Take care to update your jiras, please.

Thanks,
Justin

On Wed, 11 Apr 2012, [email protected] wrote:

RC2 from revision 1324655 is available here:

 http://people.apache.org/~jross/qpid-0.16-rc2/

This RC fixes the problem with embedded svn versions that Robbie raised. It also has the following bug fixes:

 jross@nicaea qpid-0.16$ svn log -r 1309391:HEAD | fgrep QPID
 QPID-3937 - Back-ported fix from trunk into 0.16.
 QPID-3938 - Back-ported fix from trunk into 0.16
 QPID-3901: merge fix to 0.16 branch
 QPID-3900: merge fix to 0.16 branch
 QPID-3919
 QPID-3905: NullPointerException is thrown on rejecting messages whilst
   closing the connection
 QPID-3911: Fix deadlock on concurrent invocation of
   MessageConsumer#close() and Session#rollback() from consumer
   MessageListener

A point in passing: It helps (helps scripting like the above and git mirrors) if merges to 0.16 include descriptive text on the same line as the QPID- reference. Rather than "merge fix to 0.16", it's better to copy the summary from the original trunk commit. In other words, follow Robbie's example in the last two commits, :).

Finally, there's stirring on the list about a python build issue, and there are two ruby build issues not yet on the release branch. These may call for another RC.

Thanks,
Justin

---
0.16 release page: https://cwiki.apache.org/qpid/016-release.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to