Yeah, I'm pretty sure text-bound comments will work better for bug reports.
However, having a dedicated work item tracker also sounds good - not every
task can be bound to a specific piece of text. Right now we have just one
blueprint for the whole doc, I'm afraid it won't be effective enough.
Regarding addressing some items first... I agree that there are some
critical things to be addressed, but there will always be room for
improvement, and polishing some unused doc over and over to suit some
hypothetical concerns is really, really boring. I suggest we release a beta
so we can get
Well I can tell you right now there's a lot of very non-hypothetical concerns
to address.
The guide has a lot of what just happened moments where things aren't
explained at all and it's very difficult to follow in many places. (Something I
think you admitted yourself in a previous mail).
we
3 matches
Mail list logo
