Hi, On Dienstag, 17. März 2015, Raphael Hertzog wrote: > > The repository dictionary has what you are looking for. The releases > > dictionary indeed lists all versions in all existing releases. > The repository dictionary doesn't have the data that I'm interested in. ack > > Maybe you would prefer the releases dict to only have keys squeeze, > > wheezy, jessie and sid and an additional sub-release key? > > Yes, the entries in "releases" must be predictable. I must be able to > lookup issue_data['releases']['squeeze']['status'] and have the status in > squeeze no matter what sub-release has the latest version. ok. so i will add a subrelease key, speciying the "first" subrelease where the issue is fixed. subrelease will have one of these values: null, 'security' or lts'. > I also noticed that we have nowhere data that says that an > issue is <undetermined>... maybe those issues should be entirely dropped? I agree that those issues should not be displayed in the tracker, but I'm not entirely convinced they should be dropped from the json... (that's also how I understood Moritz in this bug) - but if you insist, it's easy to drop them. cheers, Holger
Attachment:
signature.asc
Description: This is a digitally signed message part.