Patrick R. Michaud wrote:
I think I prefer
to take one night's rest and get it right in the morning, than to
force it out this evening and perhaps have to clean up a lot of
small mistakes.)
Sensible.
1. The t/library/pg.t tests require libpq.so to be installed
in order to run -- should I be testing ('make fulltest') with
this library installed?
>
More generally, is there a specific set of platforms I should
be performing 'make fulltest' on prior to release? And do I
need to be maximizing test coverage by making sure certain
libraries or capabilities are available on my test platform(s)?
The libpg.o is one example... but what about things such as
ICU, readline, and the like?
Ideally 'make fulltest' would be run both with and without libpq.so (so
you know the skip is working, and know the tests are passing with the
library). But it's not really practical for one person to manually
reconfigure their box a dozen times to hit all the possible
configuration alternatives. But a handful of people each testing a
particular platform with a small set of configuration alternatives is
practical. This is part of the "platform porters" role.
For now, I'd install libpq.so, as it's more important to know the tests
are passing than that the skip is working.
Again, it's no problem for me to install the libraries -- I'm
just curious about the correct procedure so I can document it
for later release managers.)
2. In r17137, I'm getting one test failure from 'make fulltest':
Failed Test Stat Wstat Total Fail List of Failed
-------------------------------------------------------------------------------
t/pmc/pmethod_test.t 1 256 2 1 2
Anyone know anything more about this failure, and should it just
be marked 'TODO' or shall I see about fixing it?
I already had the file open on my laptop. It's the new stuff for
implementing the Parrot calling conventions in C. It's still under
development, and not core to using Parrot, so put in an RT ticket noting
the failure. It passes on PPC OSX as well. Does it only fail for you in
'make -s all world fulltest' or does it also fail when you run a default
ordinary 'make' and 'make test'? If the former, don't bother marking it
as TODO. If the latter, mark it as TODO referencing the ticket number.
3. The release instructions don't make any mention of verifying
MANIFEST or running 'make manitest' -- should this be a required
step in creating a release? Or is it happening somewhere that
I'm not seeing?
It happens in Configure.PL.
4. Anyone have a good name for the release? I'm satisfied with
leaving 0.4.9 unnamed unless there's a sense that we really
need to name it (in which case I'll come up with one or
accept suggestions from others :-).
It's a tradition! From the wikipedia list I suggest 'Socorro'.
Allison
