• I've moved the presentational dots in the header from the
  templates to the CSS

Awesome

Justin, the only reason this was a "last-minute" change is because
you only brought the issue to my attention recently That said, the change is a "customization extra" rather than something essential, so if it
creates/has created extra work for you, I will happily revert this change and
leave it for 2 11 Or you can do the same Or leave it as-is if you think
it's fine Or whatever

No - I was talking about classing out the radio/checkbox input types
- that's a change that's way too late to get on the bus;

• I've changed the class name "spacer" to "floatclear" for the sake of clarity (The class is a CSS hack used to clear floats, not to add
  space )

Got it, and changed everything I need;

[I repeat: it sounds like To me I don't mean to put words in
anyone's mouth I could be misinterpreting, or could simply be wrong Lord
knows it's happened before ]

You're correct :)

I am perfectly content with "putting this on the back burner" until
after the 2 10 0 stable release I don't think I ever suggested otherwise

OK - can you put this in the roadmap? I'll personally forget about it :)

But again, I'm not personally sold on the idea of having to class out
the input/radio fields I think we were talking about this on the
list already;

It's quite possible that a technique to avoid this problem of having
to wind down development is to branch out right before the release of
a version, so development work can continue to happen, while at the
same time, a release gets polished up I'm not sure that's the kind
of juggling I personally want to do :)

I just want to personally stress how important it is to me personally
to get a release out I'm almost finished with what I need to do, but
I'm still going to put a week between the rc that'll come out on
Tuesday and the actual release

It's gonna be killer, that's all I know :)

Justin Simoni