Priorities for next (0.14.0?) release

[WilliamParker]

My thoughts are that the following should be our priorities for the next release:

• Reduce transitions between transient and persistent memory and facilitate performance enhancements to fire-rules #268
• Proposal for efficient updates of facts in the session #249
• Variable Binding Scope #267

The changes for #268 don't strictly speaking change any contracts, but since users could have been relying on the prior behavior of eager insertions and retractions I'm inclined to bump to 0.14.0 rather than 0.13.1 for a release with those changes.

#268 is done now, and #249 is fairly close. I don't know if anyone has done any work on #267 (I have not) but it seems like a severe enough bug to me that we should get it fixed in the relatively near term. After some investigation it seems we've been running into this as well.

Thoughts?

[rbrush]

Seems like a good list, and 0.14.0 makes sense over 0.13.1.

I haven't had a chance to address #267 yet (too many unrelated demands), but have poked around it and have a good idea of the fix. I can grab that one next week unless someone else really wants to, and we can push 0.14.0 once these are in.

[WilliamParker]

@rbrush all yours from me on #267

[WilliamParker]

All of the previously mentioned issues are done now. I think we're ready to release 0.14.0; does anyone have any thoughts and/or objections?

[rbrush]

I'm fine with a 0.14.0 release. The above features seem like they certainly justify it.

[WilliamParker]

I will proceed with releasing 0.14.0 and will close this issue when I'm done.

[WilliamParker]

The release is now complete. Closing.