On Mon, Aug 15, 2016 at 3:55 AM, Brian Dolbec <dol...@gentoo.org> wrote: > > I have some trouble with not being able to close bugs as resolved when > the fixes have been released. But I do see that the majority of what is > being discussed relates to pkg ebuilds more than it does to coding > projects. In that sense it sounds reasonable. But for me, most of my > work is project coding, so it overlaps with making releases which > involves the ebuild. As a project coder, I want to be able to close a > bug when a release has been made that contains the fix. In some cases > that release might not get stabilized, but another one later does. >
I'd suggest that we agree early-on that the scope of this is around ebuild work. Not "upstream" work where the upstream is Gentoo. Of course, there could be overlap. portage-1.23.ebuild might have a bug, and that gets fixed in the portage dev git, and later gets released to portage-1.24, and then ends up in stable sometime later. Those could be two separate bugs (the gentoo repo ebuild bug vs the portage "upstream" bug), but I'm not sure that makes life easier. If they were two separate bugs (as they would be if Gentoo weren't the upstream) then the scope of this effort is focused on the Gentoo ebuild repo bug. -- Rich
