Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add releases and roadmap links and context. #1351

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

brainwane
Copy link
Contributor

Why

Previous commits cbebe09#diff-04c6e90faac2675aa89e2176d2eec7d8 , 18c55b9#diff-04c6e90faac2675aa89e2176d2eec7d8 , and cf13756#diff-04c6e90faac2675aa89e2176d2eec7d8 replaced the tabular roadmap with a link to the Product Brief roadmap, then removed that link. Interested potential users would like to know when we can expect the improvements discussed in the May eLife article and the update from 2017, and easily find out when the project published its most recent release.

What

I added contextual information from the official Texture webpage and linked to the roadmap section of the Product Brief document.

@codecov
Copy link

codecov bot commented Sep 4, 2019

Codecov Report

Merging #1351 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1351   +/-   ##
=======================================
  Coverage   86.53%   86.53%           
=======================================
  Files         387      387           
  Lines        7426     7426           
=======================================
  Hits         6426     6426           
  Misses       1000     1000

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9652776...d51563b. Read the comment docs.

@brainwane
Copy link
Contributor Author

I see that the Substance website has changed radically. Please reply with feedback on this PR to point me to the new roadmap. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant