[Process improvement]: Updating SAMWDS could negatively impact development to production

[joshbruce]

Description

Brought the conversation in from the meeting notes, with format changes:

1. New feature being developed in production codebase.
2. Must update SAMWDS.
3. Submit PR to SAMWDS.
4. Get PR approved - results in changes being in gh-pages-staging.
5. Code from gh-pages-staging would have to published to NPM.
6. NPM modules would need to be updated in production codebase.
7. Only then could we use the new HTML pattern and CSS.

Alternatively:

Update the Standards after the code has been implemented on production....what are advantages and disadvantages here?

Conversation from meeting notes:

• Jen: Need info
• AI: Relates to first one.
• Diego: How do we sync the CSP-GitHub repo with the SAMWDS site?
  • Diego: What if we had a SAMWDS beta branch that would auto-release to NPM - that way we get the develop SAMWDS immediately into our environment - but not publish a release of the SAMWDS.
  • Carlos: Kind of want to keep it separate - the standards and the angular site.

How? And what can we actually implement ourselves?

• Josh: Maybe - move the tool suite part to a separate repo on CSP...??
• Diego: For the CSP we would have to manually. For locals - can NPM publish a beta?
• Josh: Yes. Beta is possible - only one user is able to publish the package at this time. Anyway to overcome for local development?
• Diego & Josh: Table it for now...!!

https://coderwall.com/p/l_7acq/publish-beta-versions-of-npm-modules

@carlosvalle, @diego-ruiz-rei, @jagannathch, @JihadMotii-REISys, @jbabbs, @MatiasNino-REISYS, @tarandhupar, @christyhermansen