---
# System prepended metadata

title: 'Post beta release, how would v7 fix looks like'

---

#  Post beta release, how would v7 fix looks like

## Assumption
We won't lock-step major version for sub-packages (e.g. `utiltlies` won't have major version `8` when we release `v8` suit pacakage). Reason is to avoid package duplications for parteners. When both `@fluentui/react@v8` and `v7` are loaded in the app, no duplicated sub-packages are loaded.

## Facts
- different branches cannot be publishing same package with same major version at the same time.
- 2 types of fixes our users need
    - Patch, minor fixes (commonly needed) 
    - Hotfix (rarely needed; e.g. 7.140.0-hotfix.1)
- Once we release `v8`, majority of the users will still be on `v7`. I do expect almost all fixes need to be ported on both branches during beta. (TODO: is this true?)

## Proposed solution
Before our beta release (the moment we start publising v7 from `7.0` and v8 from `master`), we need to remove all sub-packages from `7.0` and use real NPM dependencies in OURF package going forward. This means any fix to v7 which touches any sub-package will need to take following steps starting from beta release:
  1. make and merge the fix in sub-package in `master`.
  2. wait for sub-package to be released from `master`.
  3. bump sub-package dependency version in `7.0`.
  4. publish dependency change in `7.0`.

*Similarly, hotfix will make hotfix publish from both `master` and `7.0` branches.*

### Caveats
- how does this affect our doc/website for v7?

