1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA512 |
3 |
|
4 |
What we have been doing in Portage so far is that when we fix it in |
5 |
git, we put IN_PROGRESS + InVCS, and write a comment that links to the |
6 |
commit on gitweb. Then when we actually release Portage, we consider |
7 |
it to be fixed, and make it RESOLVED. |
8 |
|
9 |
I would not want to tie our choosing RESOLVED to be tied to whether |
10 |
there is a stabilised package in the tree or not, because there are |
11 |
other Portage users than Gentoo. But I would not oppose such an |
12 |
enforcement too strongly at this time. |
13 |
|
14 |
We don't really need anything presently in Bugzilla beyond |
15 |
UNCONFIRMED/CONFIRMED/IN_PROGRESS/RESOLVED, as well as the keywords |
16 |
InVCS, PATCH, STABLE, STABLEREQ, and Tracker. |
17 |
|
18 |
|
19 |
Unrelated to your trimming, Michał, a field for the relevant gitweb |
20 |
link would be very useful to us. Is there any chance we could get that |
21 |
as a result of this redesign? |
22 |
- -- |
23 |
Alexander |
24 |
bernalex@g.o |
25 |
https://secure.plaimi.net/~alexander |
26 |
-----BEGIN PGP SIGNATURE----- |
27 |
Version: GnuPG v2 |
28 |
|
29 |
iQIcBAEBCgAGBQJXY6iyAAoJENQqWdRUGk8BUTkP/2b2CNd1NjK3LeD7CJis192F |
30 |
uDgR1zb4RGnOzgwF7ngSnkELrTioiUcTpshkhKQvocNjwgqCRJNeM8W5LWwc3AaR |
31 |
KfR1LEw0Sj/XoTLW9xkm00tPnecFqDOvOiA+Qo89CYIFn3C/xQFGfddGHFj99sLO |
32 |
JXSiZ7ujEgojOwv1HKJzHQDQEtGmZMXiyPdm37VW16QhacbhlwWA8pKCgdibDUKN |
33 |
iT308W4H1zFQwTS9T14BDQQwFd2gQbyFf6afN3mQGrT21uJ7hM3gwHpSrT/Otwa0 |
34 |
3MKvkYFzPmny47Vj6s2nLpsm+usOzE0JCflUPzC07Mm0TPnoM1ts6hBZlAg/w3KK |
35 |
kRCRIZEEvuHNYhxmGdeqGOAsWSR/M7287PHpYSIN5TMdjijskf7I06cIZ/OCEb4m |
36 |
cTSO/9GyZSXLlxp0BS4VHVvEVKyvbhVP0ENxBU75BhKCkF9O9ygVGXCnwWFMQQpx |
37 |
m/TSYq7hd1fU3pqvi3CSY0ps6jQCcJ9LqvBZ5negD466wWYpKgkTvbaX/tJD56rV |
38 |
/ROG4CA3SCqolHpi/oDZka94gl5QhHNEs7fk430jKYsuXeMxVutyJcPdBldhL5GP |
39 |
DVbCOdoS4LSJvMZLRGP/wdkz716DvzMyLn4joGVO9yESBFgyr2fsLUa3Ah+zir48 |
40 |
8bPXgPRu+XV6OSjXCEfu |
41 |
=hDfl |
42 |
-----END PGP SIGNATURE----- |