[Pharo-project] Issue tracker & dev images
folks, I was looking at issue 364 which is a bug in the pharo-dev image. Have we defined what the bug process is for the dev image vs the core? I wasn't sure. I.e are we happy to collate both on the one tracker; do we have appropriate types; is it not expected; etc. thanks Mike
On Sat, Dec 20, 2008 at 5:58 PM, Michael Roberts <mike@mjr104.co.uk> wrote:
folks, I was looking at issue 364 which is a bug in the pharo-dev image. Have we defined what the bug process is for the dev image vs the core? I wasn't sure. I.e are we happy to collate both on the one tracker; do we have appropriate types; is it not expected; etc.
pharo-dev is currently non-official but will soon become. I think we should keep a single tracker. -- Damien Cassou http://damiencassou.seasidehosting.st
On Dec 22, 2008, at 10:42 , Damien Cassou wrote:
On Sat, Dec 20, 2008 at 5:58 PM, Michael Roberts <mike@mjr104.co.uk> wrote:
folks, I was looking at issue 364 which is a bug in the pharo-dev image. Have we defined what the bug process is for the dev image vs the core? I wasn't sure. I.e are we happy to collate both on the one tracker; do we have appropriate types; is it not expected; etc.
pharo-dev is currently non-official but will soon become. I think we should keep a single tracker.
not sure... We have to take care that we do not end like Squeak Mantis with literally thousands of open bug reports. If we use the same tracker for Pharo-Core and Pharo, I strongly suggest that we tag the reports to clearly separate them. Adrian
yes On Dec 22, 2008, at 10:42 AM, Damien Cassou wrote:
On Sat, Dec 20, 2008 at 5:58 PM, Michael Roberts <mike@mjr104.co.uk> wrote:
folks, I was looking at issue 364 which is a bug in the pharo-dev image. Have we defined what the bug process is for the dev image vs the core? I wasn't sure. I.e are we happy to collate both on the one tracker; do we have appropriate types; is it not expected; etc.
pharo-dev is currently non-official but will soon become. I think we should keep a single tracker.
-- Damien Cassou http://damiencassou.seasidehosting.st
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Mon, 22 Dec 2008 12:50:36 +0100 Adrian Lienhard <adi@netstyle.ch> wrote:
not sure... We have to take care that we do not end like Squeak Mantis with literally thousands of open bug reports. If we use the same tracker for Pharo-Core and Pharo, I strongly suggest that we tag the reports to clearly separate them.
Speaking from the point of view of a user stumbling upon a bug, which seems to be my special gift :-), a single point of entering bug reports is extremely helpful. I don't want to have to ask "where does this bug go?" as I'll probably not be able to easily decide if it belongs to the base or dev image. If reporting a bug is too much work, I might be too lazy to even start reporting it or just not have the time to do it right. bugs.gentoo.org is quite easy to use in this regard, as bugs can be (and are) reassigned to other parts than they were reported for. s.
On Dec 22, 2008, at 6:30 PM, Stefan Schmiedl wrote:
On Mon, 22 Dec 2008 12:50:36 +0100 Adrian Lienhard <adi@netstyle.ch> wrote:
not sure... We have to take care that we do not end like Squeak Mantis with literally thousands of open bug reports. If we use the same tracker for Pharo-Core and Pharo, I strongly suggest that we tag the reports to clearly separate them.
Speaking from the point of view of a user stumbling upon a bug, which seems to be my special gift :-),
I'm pretty good at that in any software or hardware and life :)
a single point of entering bug reports is extremely helpful. I don't want to have to ask "where does this bug go?" as I'll probably not be able to easily decide if it belongs to the base or dev image. If reporting a bug is too much work, I might be too lazy to even start reporting it or just not have the time to do it right.
bugs.gentoo.org is quite easy to use in this regard, as bugs can be (and are) reassigned to other parts than they were reported for.
Indeed but may be there more ubuntuers than squeakers so we should take care.
s.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (5)
-
Adrian Lienhard -
Damien Cassou -
Michael Roberts -
Stefan Schmiedl -
Stéphane Ducasse