Status of e-ballot #2

["Larry Golding (Myriad Consulting Inc)" <v-lgold@microsoft.com>]

Here is the up-to-the-minute status of e-ballot #2 (where “#1” is the one we voted on last week).

 

The following issues will be on the ballot. There are change drafts available for all of them, and they are all merged into the provisional draft:

 

• Issue #168: Provide “immutable data” in code flows and graph traversals (e-ballot: review design change and change draft)
• Issue #291: Logical locations for XML and JSON documents (e-ballot: review change draft; design change was previously approved)
• Issue #309: “file” => “artifact” (this was a huge change) (e-ballot: review change draft; design change was previously approved)
• Issue #320: Cached threadFlowLocations (e-ballot: review change draft; design change was previously approved)
• Issue #321: inlineExternalProperties (e-ballot: review design change and change draft)
• Issue #326: graphs changes from dictionary to array (e-ballot: review design change and change draft)
• Issue #335: Renames of external-property related properties  (e-ballot: review design change and change draft) (combined change draft with #321)
• Issue #341: instanceGuid => guid (e-ballot: review change draft; design change was previously approved)

 

The following issues will not be on the ballot because the TC has already approved them. They are also merged into the provisional draft:

 

• Issue #330: Rename notification-related properties on invocation object (no change draft since it was a simple rename)
• Issue #340: Inlined logicalLocation property on the location object (TC approved the change draft at TC 33)

 

The remaining issues aren’t on the ballot because I haven’t finished writing the drafts yet. I’ll start on #179 (toolComponents/driver/extensions) after lunch, but I doubt I’ll finish it in time to get it on the ballot.

 

David: Note that #327 (remove invocation.attachments), which you thought might be on the ballot, will not be there, because it depends on #179 (you can’t remove that property until you have the tool.extensions property to give them its contents new home).

 

Michael: I’m not wild about #327 anyway. Let’s talk about whether “extensions” is really the right place for these.

 

That’s it for now.

 

Larry