-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In light of this, is it not worthwhile giving bugzilla another shot, and require all cooker bug reports to be put into bugzilla (whether by the reporter, or by a more trusted cooker member who has bigzilla write access, or by the maintainer).
The other thing that I think needs to be done is that test suites (or at least procedures) should be setup for all the critical software, and that such software is not accepted as stable until it has passed all those tests. This might have helped prevent the smbfs issue, since it would have been evident that kernel 2.4.18 broke smbfs (which is quite an important feature of the linux kernel, considering that it is the only unix which can do this). I know thie may cause a lot of work, but it may save a lot of work, and the testing needn't be done by one person. Whenever we put a new samba release into cooker, I try and confirm that some of the features work: - - First my home samba test box to check the basics. - - I normally try and get the RPMs onto our production PDC after hours and test all the domain controlling features (authentication, profiles, login scripts), - - Then our production print server to test printing functions - - Then my home desktop box to test winbind and ACLs etc. However, I always wonder what would happen if one feature was broken, and I never managed to test it ... something should be done to ensure this does not happen. Buchan Warly wrote: | Juan Quintela <[EMAIL PROTECTED]> writes: | | Just to answer on this particular subject. | | |>Using bugzilla: |>- have to go there to read it | | | No, you receive the new bug per mail | | |>- have to read each bug report | | | You can just answer the mail, the comment are added into bugzilla and | the bug poster receive the mail too. | | |>- fix errors |>- go to _every_ single error that I fix, and answer that it should be |> fixed | | | you can just reply the mail with @resolution=fixed | | |>- wait for users to ack or nack the fix | | | he can reply per mail too | | |>- go through the bug reports mark them as fixed | | | you can send a mail for that. | | |>:((( |> |>My experience is that bugzilla is very good for small packages, or |>packages that don't have a lot of bug reports (a lot is more that 1/2 |>daily). For bigger packages, email is easier/better in my experience. | | | Bugzilla is not perfect yet, mainly because nobody takes care of it, I try | to when I heve some free time, not so often I must admit. | | It lacks some faster browsing and a more powerful mail interface, but most | of the thing to use it via mail are there. | - -- |----------------Registered Linux User #182071-----------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/gpg.key -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE8l6FYrJK6UGDSBKcRAiuGAJ94dKuvZEnoj7JhOAxLexIIFttl3gCdHaVB 4dCdPlGnFGDNmPrV7obL/hs= =ND5f -----END PGP SIGNATURE-----
