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
This issue in the CFA repo should now be against this repo, so I'm moving it over.
@daguar: "@phae asked me to add this. I encountered breakage recently (I had used pre-version URL implementation), so it would be good to have some system to track and alert users."
@migurski: "Thanks guys. There are three pegged versions of the style guide (0, 1, 2). They differ in small ways mostly connected to fonts. I’ll add information about this to the front page."
@migurski: "Moving forward, it's going to be mostly-correct to peg to a version for anything that's not the website, and to use root for the website."
The text was updated successfully, but these errors were encountered:
phae
changed the title
Edit New issue A mechanism for alerting style users of version bumps
A mechanism for alerting style users of version bumps
Jan 15, 2015
@phae: Looks like right now if you elect to 'Watch' a repo on Github you'll get notifications about releases/pull requests. MVP could be encouraging people to do so if they rely on the pattern library.
What do you think is an ideal solution for this? Put my email in a box, get an email with release notes/upgrade path info whenever a new release is pushed?
This issue in the CFA repo should now be against this repo, so I'm moving it over.
@daguar: "@phae asked me to add this. I encountered breakage recently (I had used pre-version URL implementation), so it would be good to have some system to track and alert users."
@migurski: "Thanks guys. There are three pegged versions of the style guide (0, 1, 2). They differ in small ways mostly connected to fonts. I’ll add information about this to the front page."
@migurski: "Moving forward, it's going to be mostly-correct to peg to a version for anything that's not the website, and to use root for the website."
The text was updated successfully, but these errors were encountered: