On Fri, Jul 12, 2013 at 2:53 AM, Branko Čibej <[email protected]> wrote:
> On 12.07.2013 01:48, Ryan Ollos wrote: > > Adding the issue to the release notes will require creating a new > release, > > If that's the case, then we're doing something wrong. Release notes > should not be part of the release tarball -- that should contain a > /link/ to the release notes, so that any errata can be applied to the > "live" release notes. > > Subversion keeps release notes in the project site repository. BH could > have wiki pages with release notes -- only editable by committers, of > course. > > -- Brane > Keeping release notes on the wiki sounds good to me. On a related note, at some point we should do something about our diverging installation instructions on the wiki (1) and in the repository (2). I vote for using the wiki in this case as well. This was recently brought to our attention again by a user (3). (1) https://issues.apache.org/bloodhound/wiki/BloodhoundInstall (2) http://svn.apache.org/repos/asf/bloodhound/trunk/installer/README.rst (3) http://markmail.org/message/pa6go7siozxtouje
