On Fri, Jan 31, 2014 at 12:24:06PM +0100, Łukasz Stelmach wrote: > It was <2014-01-30 czw 17:02>, when Philippe Coval wrote: > > Hi > > > > So here a little recap where we are as the date of today, > > and a few suggestions to enhance the cooperation workflow through gerrit > > and build/publish system. > > [...] > > > ### NEED TO SUBMIT TO BUILD AND PUBLISH IN REPOS ### > > > > This topic is also important, because if the change was merged through > > gerrit, it does not mean it is actually published ... and requiere > > some deep investigation to know why it wasnt released or if it was > > even submitted (by maintainer)... > > > > On my previous project we allowed developer to submit the build > > themselves once the (their) changes files was merged and yes it was > > mandatory to push it. > > > > Note that could tracked easily if each change where associated to a > > BugId , then as long as the change is not released the bug would > > remain open in jira... ( head to previous discusion > > https://lists.tizen.org/pipermail/dev/2014-January/001493.html and > > https://wiki.tizen.org/wiki/Talk:Packaging/Guidelines ) > > This can be done today. There is just no (or is there) a way to create a > filter in gerrit that would find "tizen" branches without submit and/or > accepted tags.
I don't see a way to do this with Gerrit searches, and it does appear that the REST API supports this type of query. See https://gerrit-documentation.storage.googleapis.com/Documentation/2.8/rest-api-changes.html#get-included-in Regards, Patrick _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
