On Mon, Oct 19, 2009 at 2:59 PM, Michael Roberts <[email protected]> wrote:
> I think we should report the pharo tests the same way we report the > pharo-core tests. Unless someone disagrees I will look to split out > the wiki into a number of test areas. I agree we can not necessarily > fix all the tests owned by the packages but we should publish a > baseline. This will be important for inclusion of new packages, a > prerequisite being not introducing new failures. > > + 1 > thanks > Mike > > On Mon, Oct 19, 2009 at 5:31 PM, Adrian Lienhard <[email protected]> wrote: > > We have to check the packages that are part of the Pharo image before > > we release 1.0. Currently we have 40 failures and 55 errors, which is > > simply not good enough. There is code loaded that can not work > > (considering there are 38 undeclared references...). > > > > Adrian > > > > On Oct 19, 2009, at 17:08 , Damien Cassou wrote: > > > >> 2009/10/19 Mariano Martinez Peck <[email protected]>: > >>> What I propose is to identify the red tests of Pharo dev and look > >>> for the > >>> package and ask the maintainers (if there is anyone) to fix it. And > >>> the > >>> regarding tests, we can tag them as 1.1 > >> > >> Ok. Can you have a look at that please? The problem is that we will > >> also have to maintain these tests. > >> > >> > >>>>> Moreover, if packages are included in Pharo dev it is because it > >>>>> is a > >>>>> Pharo decision. So, if pharo thinks that, for example, ocompletion > >>>>> must be in Pharo, so, I think that ocompletion tests must be green. > >>>> > >>>> But I don't think that the package lists (web and dev images) are > >>>> blessed by the Pharo board. > >>>> > >>> And I am not agree with this also. I think Pharo board, and even the > >>> community has to choose the Pharo packages. Please, take in mind > >>> that the > >>> final users will use and see Pharo, NOT PHARO CORE. > >> > >> I confirm. The Pharo user community has the last word on what gets > >> integrated into images I generate, not me. The list of packages is at: > >> http://code.google.com/p/pharo/wiki/Packages. > >> > >> -- > >> Damien Cassou > >> http://damiencassou.seasidehosting.st > >> > >> "Lambdas are relegated to relative obscurity until Java makes them > >> popular by not having them." James Iry > >> > >> _______________________________________________ > >> 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 >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
