Build Service/Concepts
From openSUSE
(Difference between revisions)
| Revision as of 12:54, 8 July 2009 AdrianSuSE (Talk | contribs) Draft Concepts � Previous diff |
Revision as of 08:47, 20 July 2009 Kfreitag (Talk | contribs) Draft Concepts Next diff → |
||
| Line 11: | Line 11: | ||
| * [[Build_Service/Concepts/CrossDevelopment/Preinclude|Better package handling in kiwi builds]] | * [[Build_Service/Concepts/CrossDevelopment/Preinclude|Better package handling in kiwi builds]] | ||
| * [[Build_Service/Concepts/User Data|Storage of User Related Data]] in the openSUSE infrastructure. | * [[Build_Service/Concepts/User Data|Storage of User Related Data]] in the openSUSE infrastructure. | ||
| + | [[Build_Service/Concepts/AppDirectory|Application Directory Interface]] | ||
| == Implemented Concepts == | == Implemented Concepts == | ||
Revision as of 08:47, 20 July 2009
Contents |
Concepts for further development of Build Service
This page discusses concepts for the openSUSE Build Service.
Draft Concepts
These concepts are under discussion to be implemented in the next versions of the Build Service. Input is very welcome, please join in the discussion on the openSUSE Build Service Mailinglist.
- Source generate or pre-process service
- Windows Support
- Better package handling in kiwi builds
- Storage of User Related Data in the openSUSE infrastructure.
Application Directory Interface
Implemented Concepts
These concepts are implemented in the Buildservice codebase already or will show up very soon in the upcoming version.
- Source branching
- Requests
- Submit Request
- Devel Project
- Notification System
- Product Definition
- Cross Architecture Development
- User Trust Handling (WIP, not yet ready)
Obsoleted Concepts
- Merge Request (obsoleted by Submit Request)

