Project

General

Profile

Actions

action #1286

closed

Define API how to track staging groups

Added by coolo about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2014-01-27
Due date:
% Done:

0%

Estimated time:
12.00 h

Description

As groups move from within OBS logic to external logic, we need to track quite some things about SRs. To avoid an external database, we should try how far we can stress the concept of (ab)using OBS storables to store external informations.

The project _meta bears 2 fields that are for the user: title and description. The title is 255 chars and should give a good summary on what we're testing - e.g. package names or common devel project.

The description should give more infos than that: package name, requests associated with them, possibly more. The text should be human readable and machine parsable and we need functions to add requests, remove requests, check review state of them, ...

Think also about useful test cases for osc plugins.


Related issues 4 (0 open4 closed)

Related to Staging project workflow - action #1319: Taking a request into staging group needs to link itRejected2014-01-27

Actions
Related to Staging project workflow - action #1329: Create API and cli for wiping out long-failing stagingClosed2014-01-28

Actions
Blocks Staging project workflow - action #1296: Need a way to split a staging groupResolved2014-01-27

Actions
Blocks Staging project workflow - action #1344: Check the review state of requests in staging projectResolvedcoolo2014-01-28

Actions
Actions #1

Updated by coolo about 10 years ago

  • Assignee set to scarabeus_iv
  • Target version set to Staging sprint 1
Actions #2

Updated by coolo about 10 years ago

  • Status changed from New to Resolved

we worked on that - even though it was never in progress and no time spent on it :)

Actions

Also available in: Atom PDF