[MERGE] Remove things deprecated in 0.8 and 0.7

[Aaron Bentley]

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

John Arbash Meinel wrote:
> While there has certainly been enough versions, have we had enough time
> for deprecation? My understanding was it was something like 6-months
> from introduction, and X months (or 1 version) from deprecation. I don't
> remember our explicit support declaration.

I don't remember a specific timeframe for API deprecations.  I thought
the 6-months thing was only for file formats.

Personally, I feel that one version is enough notice for deprecations,
because people are strongly motivated to fix them, and the fixes are
usually simple.

I'd be inclined against a 6-month period, because deprecated code is
usually untested code, and therefore, unmaintained code.  In 6 months, I
would expect a lot of it to start silently breaking.

I think a two-month/two-release schedule for removing deprecated
functionality would be reasonable.  What do other people think?

> bzr-0.7 was released in Jan 2006, and 0.8 in May. So it seems like we
> could remove 0.7 deprecated stuff, but not 0.8 deprecated stuff.

If we decide we can't get rid of the 0.8 stuff yet, I'll send a bundle
for just 0.7.

> By the way, this wiki page really needs to be updated:
> http://bazaar-vcs.org/BzrHistory

> It looks like it is mostly just a wikified version of NEWS, is that true?

Page history suggests part of it came from the release roadmap.  Page
history also suggests that you're the most frequent contributor to that
page ;-)

It would probably make sense to auto-include all docs from the latest
release somewhere on the site.

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

iD8DBQFE41CE0F+nu1YWqI0RAq7XAJ9ztrpRx+O+dkDUmSP1tCcVGcCMAQCfdF04
nubecJ/H1eMbUj06LcCGND8=
=N8Dr
-----END PGP SIGNATURE-----