1.0.3 tracker bug

[olly]

1.0.0 is very nearly out, and a lot has changed since 0.9.10, so it's quite likely there will be some problems to address. This bug is for tracking them.

I'd like to keep HEAD in a stable, releasable state for a couple of weeks so we can make any follow-up releases required without too high a risk of introducing further problems. But we can be less conservative than we have been for the past few weeks.

Anyone should feel free to suggest bugs by marking them as blockers on this one, but remember, no incompatible ABI or API changes!

I think it's probably OK to bump the remote protocol version in the 1.0.x series, but we should try to batch up patches which do this.

[olly]

Note that bug#153 has a patch to add a "minor version" to the remote protocol which should make it less awkward to upgrade when we only change the remote protocol by adding new MSG_XXX/REPL_XXX combinations. We should try to coordinate changes where possible though, as bumping the minor version still requires that the server be upgraded first which isn't otherwise required.

[olly]

Now tracking bugs for 1.0.2 release.

[olly]

Now tracking bugs to fix in 1.0.3.

[olly]

Closing this - we're now using bug#200 for tracking 1.0.4 as the bug number is more memorable.

[olly]

Fixed in 1.0.4

[olly]

Erm, ignore that last comment...

[richard]

Aww, do I have to? It's a cute way of looking at things.