Development Resources » History » Revision 34

Revision 33 (Dominic Cleal, 07/31/2015 04:42 AM) → Revision 34/57 (Dominic Cleal, 08/10/2015 06:25 AM)

h1. Development Resources 

 {{toc}} 

 h2. Current Sprint 

 * [[Current Sprint Information]] 

 h2. Deep Dives 

 h3. Content has been promoted to the Foreman web site 

 The content from this page has been incorporated into the official "theforeman.org":http://theforeman.org/ web site.    You can access it here: 

 * "*Foreman screenshots & videos: Deep Dives*":http://theforeman.org/media.html#deepdives 

 The archived version of this page is "still available":/projects/foreman/wiki/Development_Resources?version=13 

 h3. Upcoming deep dives 

 Upcoming topics are on the [[Upcoming Deep Dives]] page - feel free to add more suggested topics! 

 h2. Patch reviews 

 * [[Reviewing patches]] - some notes about things to check for when reviewing PRs 
 * [[Reviewing_patches-commit_message_format]] - commit message standard for Foreman projects 

 h2. Packaging 

 Foreman is packaged as both RPMs (for EL, Fedora) and Debian packages. 

 * [[RPM Packaging]] 
 ** [[Koji]] 
 * [[Debian Packaging]] 
 * [[Installer Packaging]] 

 h2. Release process 

 Each major release of Foreman is managed by a release manager. 

 * [[Release Management]] contains general guidance on the process, controlling what's released etc. 
 * [[Release Process]] describes the process the manager nanny.    They will follow (and amend) to prepare and publish each release 

 Each release schedule is available below: the process in [[Release Process]]. 

 * [[Foreman 1.7 Schedule]] 
 * [[Foreman 1.8 Schedule]] 
 * [[Foreman 1.9 Schedule]] 
 * [[Foreman 1.10 Schedule]] 
 * [[Foreman 1.11 Schedule]] 

 h2. Developer documentation and designs 

 * [[granular_permission_system|Granular permission system (aka new permission system)]]  
 * [[create_host_UI_when_build_from_source|Create a host in UI when building and runnning Foreman from sources]] 
 * [[API v2 Development Guidelines]] 
 * [[friendly_id]] gem is used by Foreman to unify the the common find logic between UI and API based on id or friendly_id "name" of resource 

 h2. Redmine 

 * [[Triage process]] - how to triage redmine issues 

 h2. Infrastructure 

 * [[Jenkins]] - how our CI is configured, managing jobs etc. 
 * [[Koji]] - our RPM build system 
 * [[KojiBuilderSetup]] - adding builders to Koji