Difference between revisions of "Debian-team"
mediawiki>Digitalelf (→mission statement) |
(→Mission Statement) |
||
| Line 4: | Line 4: | ||
To produce a high quality, current, Debian native CFEngine package suitable for inclusion directly in Debian stable release. |
To produce a high quality, current, Debian native CFEngine package suitable for inclusion directly in Debian stable release. |
||
| − | + | == Starting point == |
|
| + | The Debian CFengine release now (20130728) related to CFengine 3.0.5. CFengine now is at 3.5 and has major changes and improvements with regards to stability and fuunctionailty. We the Debian-team decided to build the native CFengine Debian package om CFengine version 3.5.1. |
||
== Plan == |
== Plan == |
||
Revision as of 22:10, 27 July 2013
Contents
Provisional page for the CFEngine Debian-team
Mission Statement
To produce a high quality, current, Debian native CFEngine package suitable for inclusion directly in Debian stable release.
Starting point
The Debian CFengine release now (20130728) related to CFengine 3.0.5. CFengine now is at 3.5 and has major changes and improvements with regards to stability and fuunctionailty. We the Debian-team decided to build the native CFengine Debian package om CFengine version 3.5.1.
Plan
- preconditions
- scope
- risks
- gouvernance
- relationships to the commercial edtion and third party solutions
- Planning and milestones to be obeserved
tenants
- As much as possible cfengine-core should support Debian natively
- Prefer patching cfengine rather than Debian
- Use IFDEF where necessary
- Strictly adhere to Debian packaging policies
- Debian FHS layout
Creating a buildable debian package should be as easy as obtaining the cfengine source and dropping in the debian directory.
Terug naar: Webhuis Infrastructuur
