This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| spec:issues [2014/07/21 11:37] – [3. Address (and communicate!) your Issues] fantasai | spec:issues [2014/07/22 02:01] – [4. Save your Progress] fantasai | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Best Practices for Issue Resolution ====== | ====== Best Practices for Issue Resolution ====== | ||
| - | So you're a spec editor now. Congrats! You my think you will be spending your days drafting beautifully-crafted spec text to describe the newest features you've just dreamed up, but in fact, you will //mostly // be living in a mailing list addressing all the bugs in what you (or your predecessor) have already written. | + | So you're a spec editor now. Congrats! You may think you will be spending your days drafting beautifully-crafted spec text to describe the newest features you've just dreamed up, but in fact, you will //mostly // be living in a mailing list addressing all the bugs in what you (or your predecessor) have already written. |
| Fear not! There is a (temporary) end to the issues (if you are diligent enough to hit Inbox Zero). Note: This is sometimes called Last Call. It will flood you with more issues. | Fear not! There is a (temporary) end to the issues (if you are diligent enough to hit Inbox Zero). Note: This is sometimes called Last Call. It will flood you with more issues. | ||
| Line 107: | Line 107: | ||
| * It helps with spec archaeology by providing easily-findable major revisions. | * It helps with spec archaeology by providing easily-findable major revisions. | ||
| + | Publish early, publish often. | ||