Page Comparison

What needs to be done:

will we want to create a separate Repo for the standalone storage libraries?
Alternative is to create a tag + build on master with all of the RChain binaries. (this does offer a side benefit of putting everything on the dev's machine) - need to find out if this is a desirable UX or not.
Use Git releases
Separate Repo → Git Issues becomes easier. Use Git Issues for storage. See if we can do a Jira integration for Git issues - impt. for bugs.
- Alternative option is to set up a storage project in Jira and set it to Anonymous access for tickets.

Roscala:

...

When ready, merge to Master
- Code is in CI with 1 no-op test:
- Create installer
- Determine the format of the documentation (html, pdf)
- Prolog documentation
- query unification documentation
- User guide
- Query help docs
Meet with the community and present the release
- Documentation review
- Demo of features ?
- Code walk through ?
Create a tag on Master & label release
- Build release package
Outward facing release communication
- Update RChain.CoOp website to include a section for Storage
- Determine website content - Daniel?
- Create mailing lists
- Create Gitter channels & link on website
- Create link to download the bits on the website
Griff McClellan (Unlicensed): Advise if anything is missing, and if this approach is reasonable

Issues Capturing the above tasks

Jira Legacy

target audience - Developers
technical documentation
Summary of the project
Someone needs to write some articles about the storage system, why they are interesting, how they work, why it's cool
Write some blog posts, post on reddit, linkedin, steamit, etc...
At the bottom, there is a release page, come back in 3 months.
Tech guys love to read interesting articles. It's a great way to generate buzz.
Articles on Prolog unification, Benefits of type unification, Benefits of using LMDB

Roscala:

For Roscala.Void

Rholang:

For Roscala.Transition

Versions Compared