In the perl 5.39.x branch Test2::Suite has been put into perl core.
Originally Test2-Suite and all its contents were written to be part of the
same Dist as Test2::API, and other things which are in Test-Simple. I split
the functionality out at the urging of RJBS to make it easier to get Test2
accepted into core as the Test2-Suite stuff was less obvious a match.
Now that both dists are in core I would like to merge them back into one
dist, and Test-Simple as the dist name makes the most sense for
legacy/sanity reasons.
My justification is that it will make maintenance significantly easier. It
will also put the Test2::API documentation into the dist where Test2::API
actually lives. (Currently the Test2 manual lives in Test2-Suite, but 90%
of what it documents is in Test-Simple). I also constantly get bug reports
and feature requests on the wrong dist as it is often quite hard to
determine which dist the issue belongs to.
Maintenance is hard right now because Test2::Suite is written using private
internals of Test2::API, so whenever those internals change Test2-Suite
will break without absurd contorting for compatibility with older internal
APIs. Right at this moment I have a change I want to make that will boost
performance slightly. But I cannot do it because making the internal API
change in Test-Simple breaks Test2-Suite and the only way to fix it is a
new Test2::Suite release, but that would mean installing Test-Simple
without upgrading Test2-Suite would break the already installed
Test2-Suite, which I find unacceptable (so am not releasing this change at
this time).
So for these reasons I am seeking input from the group on if reunification
of the sundered dist back into a single dist is acceptable now that they
are both in core?
Thank you,
Chad 'Exodist' Granum
Originally Test2-Suite and all its contents were written to be part of the
same Dist as Test2::API, and other things which are in Test-Simple. I split
the functionality out at the urging of RJBS to make it easier to get Test2
accepted into core as the Test2-Suite stuff was less obvious a match.
Now that both dists are in core I would like to merge them back into one
dist, and Test-Simple as the dist name makes the most sense for
legacy/sanity reasons.
My justification is that it will make maintenance significantly easier. It
will also put the Test2::API documentation into the dist where Test2::API
actually lives. (Currently the Test2 manual lives in Test2-Suite, but 90%
of what it documents is in Test-Simple). I also constantly get bug reports
and feature requests on the wrong dist as it is often quite hard to
determine which dist the issue belongs to.
Maintenance is hard right now because Test2::Suite is written using private
internals of Test2::API, so whenever those internals change Test2-Suite
will break without absurd contorting for compatibility with older internal
APIs. Right at this moment I have a change I want to make that will boost
performance slightly. But I cannot do it because making the internal API
change in Test-Simple breaks Test2-Suite and the only way to fix it is a
new Test2::Suite release, but that would mean installing Test-Simple
without upgrading Test2-Suite would break the already installed
Test2-Suite, which I find unacceptable (so am not releasing this change at
this time).
So for these reasons I am seeking input from the group on if reunification
of the sundered dist back into a single dist is acceptable now that they
are both in core?
Thank you,
Chad 'Exodist' Granum