Revision as of 12:50, 22 April 2011

Apps Sprint

Success criteria:

Deliver a working process to:

1. (x) Upload source
2. (x) Build binary rpm
3. ( ) Allow promotion to Apps:Testing
4. ( ) Automatically validate and accept to Apps:Testing
5. ( ) Build in Apps:Testing
6. ( ) Start Community test process
7. ( ) Accept/reject application (notify user)
8. ( ) Publish to Apps
9. ( ) Notify http://apps-beta.meego.com/
10. ( ) Available in http://apps-beta.meego.com/
11. ( ) Install on ...? DE?

Implementation/Acceptance details

When something is ticked in the main list, details should be provided here

Upload source

This is standard OBS functionality.

The user is expected to have a home: area and know how to issue a submit request.

Build binary rpm

MeeGo:1.2:Apps and MeeGo:1.2:Apps:Testing projects have been created.

These build against MeeGo:1.2 (which for now is MeeGo:Trunk, which is a snapshot of 1.1.99.3.20110419.9)

A developer needs to build against MeeGo:1.2 in home:<username>

Allow promotion to Apps:Testing

A nice test package is omweather in home:vasvlad. This already builds against MeeGo:1.2.

Automatically validate and accept to Apps:Testing

This activity is carried out by a BOSS process.

The "REQUEST_CREATE" event targetting Apps:Testing is captured and a process started.

The process is:

Ruote.process_definition :name => 'Apps_submit do
  sequence do
  end
end

• need better 'process/event' mapping and tracking

Build in Apps:Testing

Start Community test process

Accept/reject application (notify user)

Publish to Apps

Notify http://apps-beta.meego.com/

Available in http://apps-beta.meego.com/

Install on ...? DE?

Tasks Arising

This is for the "hmmm, we really need to have a ...." ideas that come out in the sprint

• Tutorial docs for OBS and App process