This issue outlines a plan for all components of the Mercury Suite (not just Mercury Core) that need to be completed before the release of Mercury 3, the hosted version of Mercury Core currently at mercs.dev. Of course, launching Mercury 3 isn't our actual aim; it's improving the tools in the Mercury Suite, however Mercury Core's previous development processes have proven that launching a live revival platform is a good indicator for our actual metric and allows us to attract more testers.
This timeline is in roughly chronological order from now to public release, is not final, and excludes items we don't plan to complete before the release.
I'll edit this issue to add the relevant sub-issues soon.
This issue outlines a plan for all components of the Mercury Suite (not just Mercury Core) that need to be completed before the release of Mercury 3, the hosted version of Mercury Core currently at mercs.dev. Of course, launching Mercury 3 isn't our actual aim; it's improving the tools in the Mercury Suite, however Mercury Core's previous development processes have proven that launching a live revival platform is a good indicator for our actual metric and allows us to attract more testers.
This timeline is in roughly chronological order from now to public release, is not final, and excludes items we don't plan to complete before the release.
I'll edit this issue to add the relevant sub-issues soon.