On Mar 2, 2005, at 20:46, Lex Spoon wrote:
goran.krampe@bluefish.se wrote:
- Get a bug tracker going so that we can see what specific packages
have open release-critical bugs in them. Otherwise, the work in #1 is much less useful, because we have no way to tell how stable different packages are.
For the "official packages" and for the staked out partitions of the image I simply think we should use Mantis just like we already do. We already use it for the image and for some packages.
Yes, but what about for other packages? Mantis is not effective for them, because it does not target bugs at individual packages. It has some notion of "projects", which might be usable, but not until something is done to make the list have an option for every package.
Without a decent bug tracker, we can't do a great job of releasing stable sets of packages.
The Category pulldown can have whatever strings the Mantis manager wants to place there. If you go to project Squeak for example the following categories are currently available: Balloon3D Celeste Chronology Compiler Debugger Etoys IRC Kernel LanguageEditor MVC Morphic Network SARInstaller SUnit Scamper Sound VM XML-Yaxo
So a bug report can be entered that has any one of these as its category. You can also filter the bug reports by category.
regards ------------------------ Frank Caggiano frankcag at crystal-objects dot com http://www.crystal-objects.com
The best education for the best is the best education for all. Robert Maynard Hutchins
Frank Caggiano frankcag@crystal-objects.com wrote:
Without a decent bug tracker, we can't do a great job of releasing stable sets of packages.
The Category pulldown can have whatever strings the Mantis manager wants to place there.
[...]
So a bug report can be entered that has any one of these as its category. You can also filter the bug reports by category.
One thing that would be great from our bug tracker, is if there were a way to tell which packages have open bugs of high severity. We could use this as the main criterion for going into a stable release: packages don't go into a stable release, until at *least* all of their high severity bugs are fixed. With a good bug tracker, this information can be at the release managers' fingertips.
With the current setup, that is not the case -- there are many fewer Mantis categories than active packages (the stable 3.7 universe has over 200 packages, IIRC, which might be one approximation of the active packages). Thus, the release manager would have to slog through all open bugs and read the descriptions, in order to find out what packages are having problems.
-Lex
squeak-dev@lists.squeakfoundation.org