I'd suggest grouping all minor editorial bugs by chapter. That's how I'll process them.
As noted in the release notes, Rev 22 is particularly rough WRT algorithm formatting because of some technical issues I was still working through. Don't bother reporting those sorts of issues for this revision. I already know about them. Prioritize the reporting of actual semantic errors over minor editorial issues. allen On Feb 10, 2014, at 1:30 AM, Michael Dyck wrote: > I've more-or-less finished composing my comments on rev22, and I find that, > even after eliminating comments that have already been made, I'm still left > with about 280. > > Now, there's no way I'm going to create 280 bugs at bugs.ecmascript.org. > I'd go crazy with all the copying and pasting. Even if I group them by > section, that's still about 175 bugs. I could use bigger groupings, but > that maybe leads to unmanageable bugs. > > I suppose I could write a script that sends a bunch of HTTP POST requests > to create new bugs, but that sounds like something that could cause a lot > of trouble. > > So, what to do? > > ---- > > On a more meta level, do the process plans for ES7 include any new > mechanisms for: > (a) submitting comments on spec drafts, or > (b) reducing the number of errors in spec drafts to begin with? > > -Michael > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
