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
What I love is to know which features are implemented without to read closed pull requests.
So, I think it's good if the RFC repository is marked as a release.
And it would be nice if a changelog* shows all implemented features.
That will be nice. I hope I'm not alone.
(*) I recommdend the name implemented(.md)
With following structure (also a recommendation from me, only); [...] means optional
{Version}[ - {Date of release}]
{RFC's name without its number} {RFC's number} # as a link to the RFC document
...
/some space/
...
The text was updated successfully, but these errors were encountered:
@sa-tasche what is the use case for what you are proposing? Each RFC has a link to their corresponding ponyc issue in the header, such as RFC 65 linking to issue #3557 for example. I'm not sure what purpose there would be for listing the completed RFC implementations here that cannot be accomplished by searching for RFC issues on the ponyc repo. But it's possible that I am misunderstanding the suggestion.
What I love is to know which features are implemented without to read closed pull requests.
So, I think it's good if the RFC repository is marked as a release.
And it would be nice if a changelog* shows all implemented features.
That will be nice. I hope I'm not alone.
(*) I recommdend the name implemented(.md)
With following structure (also a recommendation from me, only); [...] means optional
/some space/
The text was updated successfully, but these errors were encountered: