From Fedora Project Wiki
(→How) |
(→How) |
||
Line 11: | Line 11: | ||
*** <code>git checkout BRANCH_NAME</code> | *** <code>git checkout BRANCH_NAME</code> | ||
** Make a new spin-kickstarts tar ball | ** Make a new spin-kickstarts tar ball | ||
*** git tag 0.x.y (where x is the Fedora version and y is a sequence number) | *** <code>git tag 0.x.y</code> (where x is the Fedora version and y is a sequence number) | ||
*** git push --tags | *** <code>git push --tags<code> | ||
*** make | *** <code>make</code> | ||
** Publish the tar ball | ** Publish the tar ball | ||
*** make publish | *** <code>make publish</code> | ||
** To make a new package of spin-kickstarts for a Fedora branch: | ** To make a new package of spin-kickstarts for a Fedora branch: | ||
*** Go to the local branch directory | *** Go to the local branch directory |
Revision as of 19:10, 29 June 2013
When
This package should get rebuilt shortly before alpha, beta and the release, when there have been changes in spin kickstart files since the last build. An update should be done shortly after a release, if there was a change to the release branch of spin-kickstarts since the last build. When spin-kickstarts (git repo) is branched for a release, a new devel package should be built corresponding to the next Fedora release.
How
- Get a checkout of the appropriate spin-kickstarts branch
git clone ssh://git.fedorahosted.org/git/spin-kickstarts.git spin-kickstarts
cd spin-kickstarts
- If not using the master branch switch to the appropriate branch
git checkout BRANCH_NAME
- Make a new spin-kickstarts tar ball
git tag 0.x.y
(where x is the Fedora version and y is a sequence number)git push --tags
make
- Publish the tar ball
make publish
- To make a new package of spin-kickstarts for a Fedora branch:
- Go to the local branch directory
- Make sure the branch is up to date
git pull
- Update the tar archive using the one built above
fedpkg new-sources /pathto/spin-kickstarts-*.tar.gz
- Edit the spec file for the version tagged and to add a changelog entry
- Commit the changes
git commit -a
git push
- Build the update
fedpkg build
- If this isn't the devel branch go to bodhi and push the release out to testing initially and updates later if there are no problems.