Boils down to: Decide the list of issues part of the next release. Update JIRA to reflect that. Provide the release nodes and what else needs to be documented. Personally, cut a resolver release 1.2.0 from current resolver master and throw out tons of RCs of current core master using either 3.4.0 or 4.0.0 as the version. It's important this gets used by a large group of people. For this, documentation needs to be ready and published so that you do not need to answer the same questions over and over again. A link to the documentation needs to be the answer. I am still not keen on writing documentation I can throw out of the window right after committing.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
