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 }}
Repository navigation
[Support Levels] Blog post on adding tool to your CI #224
@Eomm My understanding, during the meeting where this ticket was created, was that there was the blog post from #248 to cover the general idea of the Support Levels property and how our group came to the conclusions we did.
This ticket is for a blog post after changes are made to our implementation based on any feedback from the discussion on the previous blog post. This blog post would be about using your tool to validate the support level property (whether in package.json or otherwise) as part of CI, not a call for feedback about the general idea of the support levels property like the other blog post.
I could be mistaken though. @mhdawson or anyone else have any thoughts on this?
Activity
Eomm commentedon Aug 31, 2019
Isn't this issue a duplicate of #248 ?
Emuentes commentedon Sep 30, 2019
@Eomm My understanding, during the meeting where this ticket was created, was that there was the blog post from #248 to cover the general idea of the Support Levels property and how our group came to the conclusions we did.
This ticket is for a blog post after changes are made to our implementation based on any feedback from the discussion on the previous blog post. This blog post would be about using your tool to validate the support level property (whether in package.json or otherwise) as part of CI, not a call for feedback about the general idea of the support levels property like the other blog post.
I could be mistaken though. @mhdawson or anyone else have any thoughts on this?
Eomm commentedon Oct 1, 2019
Thanks for the clarification 👍
mhdawson commentedon Oct 4, 2019
@Emuentes I honestly can't remember but your explanation seems like something we should do....