I think the issue tracker should reflect all changes. Like this, to
see whether something is harvested you look there instead of the
SqueakSource repository. I think Stef always updates the status of the
issues when pushing them into the update stream. When they are
rejected there exists also a special state for this situation.
So maybe PharoRejected is not needed, not sure.
Adrian
On Jul 8, 2008, at 10:21 , Stéphane Ducasse wrote:
why not. I think that this may improve communication.
the harvested will have to be more cautious but this is ok for me.
<[EMAIL PROTECTED]> wrote:
I still have some difficulties to know exactly what have been
integrated in Pharo after putting some .mcz in the PharoInbox.
I have to check manually if packages have been integrated or just
put
in PharoTreated (and i to repropose another version of the fix to
the
PharoInbox repository).
What about a PharoRejected box?
--
Damien Cassou
Peter von der Ahé: «I'm beginning to see why Gilad wished us good
luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
