The re-motion team has worked on this for quite some time: Michael Ketting gathered the requirements, Patrick Größ wrote a JIRA integration tool based on Michael’s instructions, I integrated that tool into our build system. And now we’re finally “done” – we finally have release notes for our weekly re-motion builds.
Here is a partial screenshot of the ones for version 1.13.43:
The re-linq build packages also have dedicated release notes which only include re-linq issues:
The release notes are automatically generated from our JIRA issues; we try to create descriptive issues for each change we are making. This involves new features and bugfixes as well as breaking changes, performance improvements, and so on. We started doing so some time ago, in anticipation of having auto-generated release notes, and so we’ve been able to generated release notes for older builds as well. This means if you’re currently using 1.13.23 and want to know what has changed since then, you can simply look up all the release notes starting from 1.13.24 (be aware, though, that older release notes might not be as complete as the new ones). The downloadable ZIP packages contain the release notes of all the builds created for the respective minor version (1.13, currently).
Here’s what the download package for build 1.13.43 contains:
All in all, I hope this will make it easier for you to determine when to upgrade your re-motion versions; and it might also give some meaning to the “COMMONS-1234” keys we’re always referring to in our SVN commit messages :)
I’ve already alluded to it on our mailing list, and now it’s official: starting with build 1.13.41, the re-linq assembly Remotion.Data.Linq.dll is now a stand-alone DLL. Over Christmas, Matthias Görtler spent quite a few hours rewriting those parts of re-linq that used to depend on the rest of re-motion. Here’s the result:
 |  |
| 1.13.40: What a difference a reference makes… | 1.13.41: Only standard libs, please |
As you can see, the reference to Remotion.dll also added indirect dependencies on Remotion.Interfaces.dll, log4net, and Castle DynamicProxy 2. By removing that reference, re-linq now only depends on .NET framework assemblies. That should facilitate interoperability for projects that already use a specific version of log4net or DynamicProxy.
If you have any questions, just post them to our discussion group.
- Fabian