Re: ASF policy check on CPAN published artifacts

2020-10-21 Thread Justin Mclean
Hi,
You might want to improve the branding / trademark with that release, I think 
it could be made clearer that the project is "Apache Avro" and that's a 
trademark of the ASF.
Thanks,
Justin


Re: ASF policy check on CPAN published artifacts

2020-07-16 Thread Ryan Skraba
Hello, I've read through the release policy in the past, but please
correct me if I'm wrong.  The convenience Perl modules hosted on CPAN
should be treated roughly equivalent to the Java binaries hosted on
maven, but the "real" release is the source distribution on
downloads.apache.org[1].

The good news: all of the code in the Avro namespace in the CPAN Perl
Avro 1.10.0 module[2] corresponds exactly to the source package, the
reported version matches the release, and the NOTICE and LICENSE files
are present.  CPAN lists the package as "License: apache_2_0" and
there is a link back to the Anyone using/reading/writing with the Avro
module will have the exact same code whether fetched from CPAN or from
the source distribution.  Until this point, only the latter was
available to Perl devs.

The bad news: this was our first publication on PAUSE/CPAN, and a
learning experience with the requirements for uploading to CPAN.
There was one change to the perl Makefile to correctly set the module
metadata during the upload (Thanks @sekikn!). We discussed whether to
make the fix manually for the current CPAN upload or wait until a
1.10.1 release in the AVRO-1461 JIRA.  As a consequence, anyone
uploading a CPAN module from the source distribution will have CPAN
errors without the fix[3].

I'm sure we can help check out any other CPAN concerns for the board
or find a way to address the current 1.10.0 if it's legally faulty
with respect to the release guidelines!

Best regards, Ryan

[1]: https://downloads.apache.org/avro/avro-1.10.0/perl/
[2]: https://metacpan.org/pod/release/SEKIKN/Avro-1.10.0/lib/Avro.pm
[3]: 
https://github.com/apache/avro/commit/98c29fbf866302c6215cca7762c47e65ff062fb7
[4]: https://issues.apache.org/jira/browse/AVRO-1461


On Thu, Jul 16, 2020 at 8:03 AM Kengo Seki  wrote:
>
> Hi Sean,
>
> The way to publish the Perl distribution to CPAN is described in the
> following wiki, as step 10.
> (I think Ismaël added this step. Thanks!)
> The cpan-upload command used here can be installed from CPAN as the
> CPAN::Uploader package.
> https://cwiki.apache.org/confluence/display/AVRO/How+To+Release#HowToRelease-Publishing
>
> But my apologies, when uploading the 1.10 distribution, I didn't
> notice that page,
> and I uploaded it manually using a web form on the PAUSE site
> (https://pause.perl.org/).
> So it's not tested yet if the above command works as expected, I think.
>
> Kengo Seki 
>
> On Thu, Jul 16, 2020 at 3:02 AM Sean Busbey  wrote:
> >
> > Hi folks,
> >
> > At the board meeting this morning a question was raised asking if our CPAN
> > published artifacts meet release guidance.
> >
> > Can anyone point me to what, if any, stuff we have for pushing things out
> > to CPAN after a release? Like a guide or automated tooling or whatever?


Re: ASF policy check on CPAN published artifacts

2020-07-16 Thread Kengo Seki
Hi Sean,

The way to publish the Perl distribution to CPAN is described in the
following wiki, as step 10.
(I think Ismaël added this step. Thanks!)
The cpan-upload command used here can be installed from CPAN as the
CPAN::Uploader package.
https://cwiki.apache.org/confluence/display/AVRO/How+To+Release#HowToRelease-Publishing

But my apologies, when uploading the 1.10 distribution, I didn't
notice that page,
and I uploaded it manually using a web form on the PAUSE site
(https://pause.perl.org/).
So it's not tested yet if the above command works as expected, I think.

Kengo Seki 

On Thu, Jul 16, 2020 at 3:02 AM Sean Busbey  wrote:
>
> Hi folks,
>
> At the board meeting this morning a question was raised asking if our CPAN
> published artifacts meet release guidance.
>
> Can anyone point me to what, if any, stuff we have for pushing things out
> to CPAN after a release? Like a guide or automated tooling or whatever?


ASF policy check on CPAN published artifacts

2020-07-15 Thread Sean Busbey
Hi folks,

At the board meeting this morning a question was raised asking if our CPAN
published artifacts meet release guidance.

Can anyone point me to what, if any, stuff we have for pushing things out
to CPAN after a release? Like a guide or automated tooling or whatever?