Dear Neil,
You have a second chance. :-) You may take over the namespace but you
should keep strict compatibility with the original module. In such a
situation new features and different behavior can be introduced via new
methods and extra parametrization of the old ones.
Cheers
Gabor
Neil
Dear Neil,
I'm afraid I can not maintain a package on CPAN. I have no idea how to do
it, what are the expectations, what are the rules of operation and what is
the responsibility of the maintainer.
Yes, this is a personal problem, I could learn it. However I think the
current situation cannot be
Hi Gábor,
If I had taken on the module, my plan would have been to revert to the 0.2 code
and just leave that in place on CPAN for the next 10 years or more. I’m fairly
sure that’s Johan’s plan for Data::Properties now, and if he wants to do
something else, he’ll use a different namespace.
Hi John,
Thanks for reverting Data::Properties to the original code (from Brian). If you
hadn’t done that, I was going to offer to adopt it so I could put the old code
back out for Gábor.
A lesson learned. One that I have learned previously, so I should have been
more conservative in this
Hi,
Allow me to chime in...
On Tue, 7 Sep 2021 11:07:40 +0200, "Kiss, Gábor" wrote:
> However I think the
> current situation cannot be solved correctly. We cannot know if anybody
> already relies on Johan's Data::Properties 1.05+. So switching back to
> Brian's original code can shock someone
Hi Gábor,
As you noticed, Brian Moseley wasn’t interested in maintaining
Data::Properties, and was happy for Johan (copied on this) to take on the
module.
As Johan said in a further email, given you were relying on the old module,
would you like to adopt it, and do a new release which
Hi Johan,
I’m emailing you wearing my PAUSE admin hat.
You’ve done a few releases of module Data::Properties, including two releases
this week.
These aren’t being indexed, because there is already a Data::Properties on
CPAN, released by Brian Moseley (PAUSE id: IX) in 2001:
