|
|
| (176 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| = What is Eclipse Fedora Packager? =
| |
| = Steps for Maintaining New Fedora Packages =
| |
| == Creating Account for New Contributors ==
| |
| === Creating a new account on Fedora Account System ===
| |
| === Creating a Bugzilla Account===
| |
| === Initial Setup ===
| |
|
| |
|
| == Making a Package ==
| |
| === Packaging Guidlines ===
| |
| === Creating an RPM package: ====
| |
|
| |
| == Submiting For Review ==
| |
| === Joining the Mailing Lists ===
| |
| === Uploading the Package ===
| |
| === Creating Review Request ===
| |
| === Bugzilla feedback ===
| |
|
| |
| == Ready to Ship ==
| |
| === Obtaining Member Sponsorship ===
| |
| === Requesting a new package SCM ===
| |
| === Checking Out the Empty Module from SCM ===
| |
|
| |
| == Updating the SCM ==
| |
| === Importing and Committing the Package Contents ===
| |
|
| |
| = Using Eclipse Fedorapackager =
| |
| == Importing a Fedora Git Project ==
| |
| == Fedora Packaging Work ==
| |
| === Uploading Source Files Required for a Package ===
| |
| === Downloading Source Files Required for a Package ===
| |
| === Using the Spec-File Editor ===
| |
| === Committing Changes to the Local Git Repository ===
| |
| === Switching Branches (Git Checkout) ===
| |
| === Building the Package ===
| |
| ==== Preparing Sources for Local Build ====
| |
| ==== Building RPM for a Local Architecture ====
| |
| === Make Locally Committed Changes Public (Git Push) ===
| |
| === Pushing a Build to Koji ===
| |
| === Pushing a Bodhi Update ===
| |
|
| |
| = title? =
| |
| === Feedback/Reporting Bugs ===
| |
| === Closing the Bugzilla Ticket ===
| |
| === Enabling Upstream Release Monitoring ===
| |
