You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2024. It is now read-only.
Ryppl is currently missing (or at least I don't see a prominent link on the home page) any way of determining the "Big Picture" status of the ryppl project itself. For example, http://clang.llvm.org/cxx_status.html and http://gcc.gnu.org/gcc-4.6/cxx0x_status.html provide "Big Picture" views of two compiler's C++0x progress.
For Ryppl, I'd like to see a table with rows for the major features, as seen by users. "Boost modularization", "Library builds", "Local regression tests", "Remote regression tests", "Test reporting", "User library installation", etc. Perhaps two columns, "Ryppl Feature" and "Status". Status might be "Nothing yet", "alpha", "beta", "ready".
KISS would certainly apply. The table needs to be very easy to understand, and very easy to maintain.
--Beman
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ryppl is currently missing (or at least I don't see a prominent link on the home page) any way of determining the "Big Picture" status of the ryppl project itself. For example, http://clang.llvm.org/cxx_status.html and http://gcc.gnu.org/gcc-4.6/cxx0x_status.html provide "Big Picture" views of two compiler's C++0x progress.
For Ryppl, I'd like to see a table with rows for the major features, as seen by users. "Boost modularization", "Library builds", "Local regression tests", "Remote regression tests", "Test reporting", "User library installation", etc. Perhaps two columns, "Ryppl Feature" and "Status". Status might be "Nothing yet", "alpha", "beta", "ready".
KISS would certainly apply. The table needs to be very easy to understand, and very easy to maintain.
--Beman
The text was updated successfully, but these errors were encountered: