[Pkg-postgresql-private] Bug classification and cleaning request

Martin Pitt martin@piware.de
Sat, 18 Oct 2003 12:06:18 +0200


--G4iJoqBmSsgzjUCe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi!

To get an overview over the work to be done on postgresql, I just
waded through the bug list and made my personal classification list
with some comments. Since it may be useful for you I just paste it
here.

The first paragraph contains the bug we should and can deal with by
now; there may still be some false positives here, I did not look at
them very thoroughly, so please reclassify them if appropriate. In the
middle of doing it I noticed that it would have been better to copy
the subject, but the other paragraphs are fine without it.

Oliver, I don't want to mess up your bugs too badly (sorry for the BTS
"spam" you already got :-) ), thus I would feel better if you could
sort out the last three paragraphs and the to-be-flagged bugs yourself
(unless you want to give us "authorization" to close and alter bugs on
our own).

I have used the alioth bug tracker for the last two bugs I closed, but
I don't get along very well with it. I reverted to the owner tagging
in the Debian BTS, but I would be interested in hearing your opinion
about that.

Regarding CVS: would it be possible to have cvs checkin changelogs
mailed to the list?

Unless anybody objects, I will proceed with cleaning up the -doc
package (#201715, #201717). I feel that I shouldn't continue with
#209171 and #161200 until we have reached a concensus/solution how to
manage upgrades in the future.

Have a nice day!

Martin

------------ snip -------------
Bugs that we should deal with:
167864=20
183427
201165
210428 (Andreas wants to deal with this)
212271
47821
107741
137833
139389 160470 160476 (merged)
140938
143159
146199
149789
149994
151082
161218
167803
167841 168496 (these should be merged)
180776
185994 (this should be discussed)
189915
190071
190601
194653
195821
199890
209171 (Martin already works on it)
212526
212716
121491 (The documentation should point to different date formats)
161200 (this is related to #209171)
201715 (Martin will do it)
201717 (Martin will do it)
204000

Real bugs concerning db upgrading:
111636
187464

Bugs that are already fixed in alioth CVS:
180197
180199
193493
200687

Don't care about (woody, wontfix, moreinfo):
160673
161815
170913 (should be tagged woody!)
186572
190806
193073
193174
194296
195419 189398 (these should be merged)
143677
157306
195266
216018=20

Upstream bugs:
198425

Bugs that should be tagged and forwarded upstream:
152295=20
190329
200964
201850
210232

Bugs that are somewhat dubious (discuss, moreinfo, probably close later):
215683
186056
191710
195637
195638
200030
203357
206761

Bugs that should be closed immediately:
209792 (was probably generated automatically for every one-line description)
201696
203519
213277
201718
------------ snip -------------

--=20
Martin Pitt
home:  www.piware.de
eMail: martin@piware.de

--G4iJoqBmSsgzjUCe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/kRCZDecnbV4Fd/IRAsrwAKCAe6DSmo/U2OUd3VF/RH/HSUcxmgCcDHBJ
btGJhIuK2gCyLXJorGazkW8=
=yVne
-----END PGP SIGNATURE-----

--G4iJoqBmSsgzjUCe--