---
# System prepended metadata

title: 'RFC: Contribution process changes during version 8 beta'

---

# RFC: Contribution process changes during version 8 beta

## Mostly moved to https://github.com/microsoft/fluentui/issues/15222

## Release branch updates

| | v8 snap | v8 beta release | v8 official release |
| -------- | -------- | -------- |-------- |
| `@fluentui/react-northstar` |  `master` (manual release) | `master` (manual release)  | `master` (manual release) |
| `@fluentui/web-components` |  TBD. `7.0` branch, or pause release ?? | `master`  | `master` |
| all other packages | `7.0` branch | `master`  | `master` |

## INTERNAL: More notes and potential problems

### Cross-dependencies with northstar

In cases where northstar depends on 

- Probably non-issue since they're dev-only
  - eslint-plugin
  - react-conformance
  - indirect
    - jest-serializer-merge-styles
    - test-utilities
- Indirect, probably non-issue due to infrequent changes
  - merge-styles (from utilities)
  - set-version
- Maybe an issue
  - date-time-utilities (northstar)
  - dom-utilities (northstar)
  - keyboard-key (accessibility, docs, bindings, northstar)
  - react-compose (bindings, northstar)
  - utilities (bindings, northstar)

### Packages not needed in `7.0`

We may want to delete these from `7.0` after snap for clarity (and potentially to prevent publishing collisions):
- all northstar
- web-components
- react-next
- new v8 components:
  - react-avatar
  - react-button
  - react-checkbox
  - react-flex
  - react-icons?
  - react-image
  - react-link
  - react-slider
  - react-spinbutton
  - react-tabs
  - react-toggle
- other new packages used only in 8 or northstar:
  - a11y-rules
  - a11y-testing
  - codemods
  - ie11-polyfills
  - react-compose
  - react-stylesheets
  - react-theme-provider
- Things from vr-tests, storybook, examples which use v8 stuff

### Hotfixes to sub-packages after version 8 release

Once v8 releases, we'll need a strategy to avoid versioning conflicts for `7.0` hotfixes in *sub-packages which didn't major bump*. 

[Xu: this is concerning. Was the reason for not doing lock-step to avoid package duplication?]

### applying package updates
applying package updates [changes](https://github.com/microsoft/fluentui/commit/35c5455294a2a288aa4b7d4f125de5550bd68752) need to be cherry-picked to master branch during time when publishing is not done from master.