Review "Pending" patches and divide them into the following kinds: 1) Send it to upstream if applicable, and change the status to Submitted 2) Change the status to Rejected and add the reason if upstream rejects it 3) Remove the patch if not needed any more And publish some numbers on the mailing list showing we're making a difference too, once a milestone or once a month, and so on.
This is only for M1, we may create other ER bugs for M2, M3 and M4.
This is important work but we're unlikely to block milestone releases on it so I've set the target to just 2.4 in the expectation that it will be a medium priority defect. This makes sense since upstream developers actions are hard to schedule.
Done for: ltp, avahi, chrpath, dropbear
I have add a web page for the statistic of the packages' pending, submitted, accept status, we can see the web page here: https://dengkedu.github.io/pkg-statistic.html I will update it when every time I deal with a package.
This bug is intended to cover all recipes, not just WR ones. We've reset the milestone to 2.5 to reflect that this is ongoing. The statistics page is interesting: is that a static web page or something generated automatically with a tool? It would be good to extend it to cover all of oe-core.
(In reply to comment #5) > This bug is intended to cover all recipes, not just WR ones. We've reset > the milestone to 2.5 to reflect that this is ongoing. > > The statistics page is interesting: is that a static web page or something > generated automatically with a tool? It would be good to extend it to cover > all of oe-core. Yes, I will let it cover all recipes, it is a static web page based on js.
This is too vague and ongoing to be a bugzilla entry, so I'm closing this.