Thank you, Yitz, for the wiki maintenance!<div><br></div><div><b>vector</b> and <b>time-extras </b>- these should be updated by the proposers as they have been "reproposed"</div><div><b>async</b>, <b>vector</b>, and <b>time-extras</b> - I think these all need to be updated to reflect the current discussion period.</div>
<div><br></div><div>While required by the process, I'd urge proposers to link to the specific version of the package under consideration. While the proposal is for inclusion of the package going forward (hence evolving versions over time), it really helps API discussions to pin them to a particular version. If discussion causes you to update a package, then the proposal discussion can "re-<font color="#993399">vector</font>" to the new version.</div>
<div><br></div><div>Please <font color="#993399">split</font> discussion of particular proposals off from this thread.</div><div><br></div><div>Lastly, just to be clear, the dates I set out are the dates by which I need proposals handled and decided in order to get the release out on schedule. The proposal process is not tied to releases, and can continue <font color="#993399">aysnc</font> from release if any proposal needs <font color="#993399">time-extra</font>.</div>
<div><br></div><div> - Mark</div>