From Fedora Project Wiki

Line 18: Line 18:
* Obtain member sponsorship (to check in and build your package)
* Obtain member sponsorship (to check in and build your package)
*  Add package to Source Code Management (SCM) system and Set Owner
*  Add package to Source Code Management (SCM) system and Set Owner
* Check out the module from SCM
* Check out the empty module from SCM
: <pre>fedpkg clone <packagename></pre>
: fedpkg clone <packagename>
* Install the client tools
* Install the client tools
: Koji, generate a client side certificate at FAS, install fedora-packager
: Koji, generate a client side certificate at FAS, install fedora-packager
* Test your package
* Test your package ?
: using Mock or Koji build systems
 
=== Update your SCM ===
* Import and commit your SRPM into master branch
* build your package
* Close the bugzilla account
* Add the package to the comp files
* Enable Upstream Release Monitoring

Revision as of 14:58, 19 May 2011

Fedora Package Process

Make a Package

  • Make sure it is a new package.
  • Create an RPM package:
Create a new RPM project, create a spec file, upload source files, export source/binary RPM
  • Make sure it is a suitable package (Read the packaging guidelines - Read other submissions)

Submit For Review

  • Create accounts (if you are a new maintainer)
Create a FAS account , Red Hat bugzilla
  • Join the mailing lists (introduce yourself)
  • Upload your package (somewhere on the internet)
  • Create your review request (inform upstream)
  • Watch the bugzilla report for feedback

Ready to Ship

Follow these steps after your package is approved by reviewers.

  • Obtain member sponsorship (to check in and build your package)
  • Add package to Source Code Management (SCM) system and Set Owner
  • Check out the empty module from SCM
fedpkg clone <packagename>
  • Install the client tools
Koji, generate a client side certificate at FAS, install fedora-packager
  • Test your package ?
using Mock or Koji build systems

Update your SCM

  • Import and commit your SRPM into master branch
  • build your package
  • Close the bugzilla account
  • Add the package to the comp files
  • Enable Upstream Release Monitoring