Move pyronova and effinitive to Experimental#868
Merged
Conversation
Both were emerging; reclassify to the new experimental tier (modes kept: pyronova tuned, effinitive standard). Updated meta.json (source) and frameworks.json, regenerated data.js. They now appear amber under the opt-in Experimental filter.
Contributor
|
👋 Heads up! This PR modifies the following frameworks:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reclassify two frameworks from Emerging to the new Experimental tier (modes preserved: pyronova tuned, effinitive standard).
meta.json(source) +frameworks.jsonupdated;data.jsregenerated.Let me know if you disagree with the new classification, experimental is suited for projects that are still very early and have no users around it.