Bzr 0.10 release candidate 1

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gustavo Niemeyer wrote:
>>don't think anyone expected that we could.  Martin said:
> 
> 
> Well, I expected.  

Okay, so clearly we need to manage expectations better.  I'd like to
find a balance between keeping people informed and getting buried in
administrivia.

Already, adding a feature entails
1. implementing tests
2. implementing the feature
3. updating the NEWS
4. updating doc/ documentation
5. submitting for review
6. updating from reviews
7. maybe goto 5
8. submitting the merge
9. updating the spec, if appropriate.

So you can see why I'd rather not add any more steps.

>>Given that we'll be doing releases every month, I wonder whether this
>>is really needed.  The actual release notes will let people know about
>>our progress.
> 
> 
> Release notes usually talk about what was released, as opposed to
> what's being worked on and how far the development is with these
> features.  Of course, there could be a section named
> "Unreleased notes".  ;-)

Sure, but our actual release notes will only lag development by 2 weeks
on average.  So I was proposing not saying anything about whether a
feature will be in a release until it's actually in a release candidate.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFE8xt40F+nu1YWqI0RAna9AJ0bYka4e6gqlbgWHznLrJFgWuaeTQCfSKaP
KKrpUfez/jkffFajKuX6jTU=
=RWup
-----END PGP SIGNATURE-----