Bzr 0.10 release candidate 1

[Aaron Bentley]

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

Gustavo Niemeyer wrote:
>>I think since we are changing to time-based releases, then we have to
>>give somewhere. We might *hope* to land things for certain releases,
>>but we can't guarantee they will get done in time. (Like tags, smart
>>server, etc).
> 
> 
>>From a user perspective, it might be nice to not suggest a given
> release number for a feature until the feature is actually going
> in for real in this release, otherwise it creates unnecessary
> frustration when the release comes out and the feature isn't there.

You referred to an email listing the goals.  Did you mean Martin's from
02/08/06?

I'm sorry if you're disappointed that we didn't get all that done.  I
don't think anyone expected that we could.  Martin said:
"here are some things people might like to work on, and that Canonical
people will be working on", to introduce the feature list.  The email
also makes reference Robert's "0.10 release process - time based
release?" email, where he notes "...to ensure the release happens, any
feature that isn't ready will just get punted to 0.11"

Perhaps we could have been clearer that these were targets for things
that *might* appear in 0.10.0, but that's a hell of a lot to get done in
three weeks.

> A feature-status page like this, if updated frequently, would get
> people excited about things really being worked on, without
> actually promising a release time.

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.

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

iD8DBQFE8w4H0F+nu1YWqI0RApaSAJ0VVmxeI77klYu0uxuza0YpLCV3JQCcCljq
AA6lQs0ST+mkg+U9R50DOYs=
=dvoe
-----END PGP SIGNATURE-----