And remember: like Apache Subversion, the project can keep a
*compatibility* layer around using the old name. But "all" new development
work would occur under the new org.apache name...
On Thu, Aug 3, 2017 at 11:34 AM, John D. Ament
wrote:
> One caveat - if your packages are "com.theoldcompany.
On Aug 4, 2017 10:37, "Andy Seaborne" wrote:
On 04/08/17 13:09, Shane Curcuru wrote:
> John D. Ament wrote on 8/4/17 7:59 AM:
>
>> On Fri, Aug 4, 2017 at 7:17 AM Shane Curcuru
>> wrote:
>>
> ...snip...
>
>> - Other reverse domain names *really* should change to org.apache;
>>> otherwise it's
Hi,
+1 binding
I checked:
- incubating in name
- signatures and hashes correct
- DISCLAIMER exists
- LICENSE and NOTICE good
- No unexpected binary files in source release
- All source files have ASF headers where needed
- Can compile from source
One minor thing I found is that several files [2
On Fri, Aug 4, 2017 at 1:13 PM P. Taylor Goetz wrote:
> > On Aug 4, 2017, at 3:10 PM, Josh Elser wrote:
> >
> > It looks like you're missing a Copyright propagation for work by Trevor
> Robinson in your NOTICE file. The license headers are for ASL (you are
> correct to have omitted this from LIC
On Fri, Aug 4, 2017 at 12:10 PM Josh Elser wrote:
> +1 (binding)
>
> It looks like you're missing a Copyright propagation for work by Trevor
> Robinson in your NOTICE file. The license headers are for ASL (you are
> correct to have omitted this from LICENSE), but I believe you still need
> to pro
Hi,
+1 binding
I checked:
- name includes incubating
- hashes and signatures correct
- DISCLAIMER exists
- LICENSE is missing a few permissive licensed bundled items. Please fix for
the next release
- NOTICE is good
- no unexpected binary files
- all source files have ASF headers
- Could compile
+1 (binding)
- DISCLAIMER exists
- L&N look good
- spot checked for ALv2 license headers
- no binaries in source dist
- can build from source (though I had to skip tests due to a failure)
- checksum and signature good
> On Aug 4, 2017, at 3:10 PM, Josh Elser wrote:
>
> It looks like you're miss
The rat scripts are only part of the issue. The entire build and check
process should be documented and as automated as possible.
I say this not as a specific pre-requisite for gaining approval for a
release, but as a pragmatic issues. There are 10x more people who will give
you a few minutes of t
On Fri, Aug 4, 2017 at 11:01 AM, John D. Ament
wrote:
> What Ted said, minus the trolling part.
>
Trolling as a synonym for fishing, not magical creatures living under a
bridge.
+1 (binding)
Francis
On Friday, August 4, 2017 12:11 PM, Josh Elser wrote:
+1 (binding)
It looks like you're missing a Copyright propagation for work by Trevor
Robinson in your NOTICE file. The license headers are for ASL (you are
correct to have omitted this from LICENSE), but I bel
+1 (binding)
It looks like you're missing a Copyright propagation for work by Trevor
Robinson in your NOTICE file. The license headers are for ASL (you are
correct to have omitted this from LICENSE), but I believe you still need
to propagate the copyright notice to your NOTICE in the src relea
You are welcome to use our RAT automation scripts from Apache Arrow:
https://github.com/apache/arrow/tree/master/dev/release
On Fri, Aug 4, 2017 at 2:11 PM, Smith, Nathanael P
wrote:
> Correction,
>
> the issue is SPOT-214
> https://issues.apache.org/jira/browse/SPOT-214
>
> - Nathanael
>
>
>
Correction,
the issue is SPOT-214
https://issues.apache.org/jira/browse/SPOT-214
- Nathanael
> On Aug 4, 2017, at 11:08 AM, Smith, Nathanael P
> wrote:
>
> Hi John,
>
> Ray and I had a discussion around this first thing today.
>
> I’ve already opened the issue [spot-213] and we’re working
Hi John,
Ray and I had a discussion around this first thing today.
I’ve already opened the issue [spot-213] and we’re working on that.
for my own understanding,
Would it be helpful if we bumped this issue up the priority list and resolved
prior to this release?
- Nathanael
> On Aug 4, 2017
What Ted said, minus the trolling part.
There needs to be a script that runs RAT of some kind, which should
hopefully be pretty simple to add. Your rat excludes should be in the
release.
I think all of this can be solved in a following release, so please add a
ticket to address. I'll continue t
Hello IPMC -
I voted on the podling vote thread with an IPMC (binding) +1. At least one
other mentor is reviewing the release as well.
If you have a chance please take a look.
Regards,
Dave
> On Aug 3, 2017, at 5:23 PM, Matteo Merli wrote:
>
> This is the first release candidate for Apache P
?!
The normal standard is that this all runs from the build process.
And certainly it should be documented.
Remember, you are trolling for volunteers to sign off on your release.
On Fri, Aug 4, 2017 at 8:03 AM, Raymundo Panduro
wrote:
> John:
>
> To RUN Rat this is how we do it:
>
> Downloa
Hi Saisai,
You can create the folder yourself for your release using SVN commands, I
did that for our project SPOT.
On Fri, Aug 4, 2017 at 7:14 AM, Saisai Shao wrote:
> Hi John,
>
> Sorry I should bring up in the dev list first, will do it next time when
> meet similar issues. Thanks a lot for
John:
To RUN Rat this is how we do it:
Downloading the SPOT Code:
wget https://dist.apache.org/repos/dist/dev/incubator/spot/1.0-
incubating/apache-spot-1.0-incubating.tar.gz
Uncompress the code:
tar -zxvf apache-spot-1.0-incubating.tar.gz
Download RAT:
wget http://apache.claz.org//creadur/apach
John:
To RUN Rat this is how we do it:
Downloading the SPOT Code:
wget
https://dist.apache.org/repos/dist/dev/incubator/spot/1.0-incubating/apache-spot-1.0-incubating.tar.gz
Uncompress the code:
tar -zxvf apache-spot-1.0-incubating.tar.gz
Download RAT:
wget
http://apache.claz.org//creadur/apache
On 04/08/17 13:09, Shane Curcuru wrote:
John D. Ament wrote on 8/4/17 7:59 AM:
On Fri, Aug 4, 2017 at 7:17 AM Shane Curcuru wrote:
...snip...
- Other reverse domain names *really* should change to org.apache;
otherwise it's just confusing.
Agreed. The one caveat to all this is the imple
Hi John,
Sorry I should bring up in the dev list first, will do it next time when
meet similar issues. Thanks a lot for your help.
Best regards,
Saisai
On Fri, Aug 4, 2017 at 6:40 PM, John D. Ament wrote:
> Hi Saisai,
>
> Just wondering, did you bring this up on your dev list? Mentors are
> r
John D. Ament wrote on 8/4/17 7:59 AM:
> On Fri, Aug 4, 2017 at 7:17 AM Shane Curcuru wrote:
...snip...
>> - Other reverse domain names *really* should change to org.apache;
>> otherwise it's just confusing.
>>
>>
> Agreed. The one caveat to all this is the implementation of javax.
> namespace wh
On Fri, Aug 4, 2017 at 7:17 AM Shane Curcuru wrote:
> Andy Seaborne wrote on 8/4/17 5:00 AM:
> > On 03/08/17 23:20, John D. Ament wrote:
> >> Which must's do you see greg?
> >>
> >> On Aug 3, 2017 1:09 PM, "Greg Trasuk" wrote:
> >>
> >>> Does this actually need to be policy? What’s the harm to
On 4 August 2017 at 12:17, Shane Curcuru wrote:
> Andy Seaborne wrote on 8/4/17 5:00 AM:
>> On 03/08/17 23:20, John D. Ament wrote:
>>> Which must's do you see greg?
>>>
>>> On Aug 3, 2017 1:09 PM, "Greg Trasuk" wrote:
>>>
Does this actually need to be policy? What’s the harm to the foundat
Andy Seaborne wrote on 8/4/17 5:00 AM:
> On 03/08/17 23:20, John D. Ament wrote:
>> Which must's do you see greg?
>>
>> On Aug 3, 2017 1:09 PM, "Greg Trasuk" wrote:
>>
>>> Does this actually need to be policy? What’s the harm to the foundation
>>> if a project continues to use a non-Apache packag
Hi Saisai,
Just wondering, did you bring this up on your dev list? Mentors are
responsible for creating the dist area.
I went ahead and created one for you, in both /dist/dev and /dist/release.
John
On Fri, Aug 4, 2017 at 5:05 AM Saisai Shao wrote:
> Hi Team,
>
> We're working on the first A
Hi Team,
We're working on the first Apache release of incubator-livy project, as the
document mentioned that source release should be staged under this folder,
but I don't find a folder named "livy", how do I create this folder, please
suggest, thanks!
The Incubator PMC expects the source release
On 03/08/17 23:20, John D. Ament wrote:
Which must's do you see greg?
On Aug 3, 2017 1:09 PM, "Greg Trasuk" wrote:
Does this actually need to be policy? What’s the harm to the foundation
if a project continues to use a non-Apache package name, assuming that the
code was donated appropriately
29 matches
Mail list logo
