Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

RELEASE NOTES - Beta.1 #334

khawkins98 opened this issue Apr 1, 2019 · 0 comments


None yet
1 participant
Copy link

commented Apr 1, 2019

馃毃These are draft release notes 馃毃


  • features with checkboxes are to-be-implemented and are part of the acceptance criteria for beta.1
  • beta.1 does not yet have a planned release date

馃憢Hello world

beta.1 of the Visual Framework 2.0 core component system is here, it's ready for testing as the cornerstone of your design system. The beta advances us from a proof-of-concept alpha to something that 鈥 as a developer 鈥 you begin to use and provide critical feedback and ideas.

Want to get started, read the guide.

馃敯 What is the VF 2.0? A modular, compatible framework for life science websites and services. Need to know more? Read this

馃彈 Building with the Visual Framework 2.0

馃攳鈿欙笍 Refinement and technical improvements

  • All component files are tracked in npm by default #333
  • Modularisation of the gulp and build process
  • Make use of .yml for adding in data/content #316
  • We've set the default branch back to master #335

馃搾 Documentation

  • Better documentation of JS and CSS optional implementations #317


  • A slew of fundamental components (tables, cards, etc.) have been added
  • Had a tidy: Cleanup, remove, deprecate patterns from npm #336

馃All the things

  • We've documented how and when something is in or out of vf-core #114

馃搮 What's next?

  • Releases are planned for the last Thursday of each month.
  • We'll focus primarily on incremental feature and bug enhancement while we gain further feedback and results of testing
  • 馃梻 See all issues tagged for beta.2

Release to-do script

  1. Finish up outstanding ticket/tasks
  2. Do release notes
  3. Update vf-core package.json version
  4. npm publish vf-core
  5. Push to npm (lerna)
    • Frist, test the command by doing "skip-npm"
      • lerna publish --no-git-tag-version --conventional-commits --no-push --skip-npm
    • If all went well, reset your branch
    • Then publish to npm
      • lerna publish --no-git-tag-version --conventional-commits --no-push
    • You'll probably have lost your local git changes, so:
      • reset your branch
      • lerna publish --no-git-tag-version --conventional-commits --no-push --skip-npm
      • verify no tags added: git tag
      • push your branch
      • PR version changes
  6. PR Merge to develop
  7. PR Merge develop to master
  8. Tag release on master

@khawkins98 khawkins98 added this to the v2.0.0-beta.1 milestone Apr 1, 2019

@khawkins98 khawkins98 referenced this issue Jul 1, 2019


RELEASE NOTES - v2.0.0-alpha.7 #448

8 of 8 tasks complete

@khawkins98 khawkins98 referenced this issue Jul 8, 2019


RELEASE NOTES - v2.0.0-alpha.8 #475

0 of 8 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can鈥檛 perform that action at this time.