Comment 2 for bug 963739

> The announcements should stay short and focus and the latest changes.

I don't quite get this, the release announcement gets circulated wide and far, especially for a major non beta version.

Why don't you want to give people a starting point from there to easily find out about the hard work you put into the release?

To me that would be the main point in making a release announcement at all.

> Yo get more details:
>
> http://bazaar.canonical.com/en/ select 'Documentation'
>
> http://doc.bazaar.canonical.com/en/ select 'HTML Online' for 2.5
> http://doc.bazaar.canonical.com/bzr.2.5/en/ select 'Release Notes'
> http://doc.bazaar.canonical.com/bzr.2.5/en/release-notes/index.html from there you can get the details for each release.

Highly appreciated, but still, it means I have to know where it is in the project (I always forget that after not visiting the project website for several months), requires quite a bit of navigation (not least of which is that I first have to go back from the release announcement to the home page to get at the documentation).

I mean, it's your project, but why don't you want to entice people with the hard work you did in the release announcement?

For all it's worth, you seem to be saying: no we don't put a link to those nice release notes because people who don't want to really dig and search for them shall not read them.

Over the top on purpose (apologies for that), as I want to illustrate how silly it sounds to me.

Best Regards!