Conversation
MAKING A RELEASE :-)
clean blank space
1) Make sure that any feature branches you want have been merged. | ||
git clone git@github.com:fedora-infra/fas.git | ||
cd fas | ||
git flow init |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also redundant as people already did flow init before start working on their new features, hotfixes, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sure that any feature branches you want have been merged.
git clone git@github.com:fedora-infra/fas.git
cd fas/
It looks good this way?
2. If time allows, read and do the :id:`Getting Translated` section below. | ||
3. Pull in new translations using tx pull -a -f. Add any new translations to | ||
1) Any features, hotfixes, etc go to branches before being merged | ||
to develop then master. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, let's rework step 1 better as my comment is really not a step.
Here's what I think should be helpful.
- Release has to be done from branch "develop". Make sure you have a working and up-to-date develop's branch (your local branch must not be behind any remote-server's commits)
- if you have no local copy of fas's repository
git clone [...] - if you have a local copy of fas's repository already
git pull develop
/!\ WARNING: this will overwrite any uncommited changes.
I Working in this! When finish I sent the new pull request. |
Update HACKING #23