Opened 5 years ago

Last modified 3 years ago

#2626 new enhancement

Users for Changes

Reported by: dustin Owned by: tycoish
Priority: major Milestone: 0.9.+
Version: Keywords: simple


In the Data API, Changes don't have users, even though that data is in the DB API. Change users should be included in changes.

Change History (4)

comment:1 Changed 5 years ago by tardyp

there might be at least 2 users for a change:

the author of the patch the committer of the patch (aka the integrator or maintainer)

not even talking about Tested-By, Acked-By, etc linux people are using.

All those people deserve to be in the blame list, and have a nice dashboard with all builds for patches they are working on.

Last edited 5 years ago by tardyp (previous) (diff)

comment:2 Changed 4 years ago by dustin

Correct, so in the Data API, a change should have a list of users, rather than a single user.

comment:3 Changed 4 years ago by dustin

  • Summary changed from [nine] Users for Changes to Users for Changes

comment:4 Changed 3 years ago by dustin

  • Milestone changed from 0.9.0 to 0.9.+
Note: See TracTickets for help on using tickets.