Hi @All,
Thanks for your votes. Sorry for the late response, I was traveling the last
4 days.
I'm canceling the vote.
I will create a new release candidate addressing the following issues:
- DISCLAIMER
- NOTICE
- Leading directory name in tar/zip file:
I vote for what Julian suggested
A leadin
On 13 May 2018 at 16:51, Matt Sicker wrote:
> On 11 May 2018 at 19:07, Justin Mclean wrote:
>
>> Hi,
>> I think the confusion around copyrights in NOTICE files happens because
>> when you bundle a 3rd party ALv2 for with a minimum NOTICE file it is
>> likely that it contains a copyright line you
Hi,
>> And then, for example, if an Apache project were to bundle code from
>> another Apache project (and licensed as such), then that code is still
>> covered by the same exact NOTICE usually since it's still referring to the
>> ASF.
>
> Huh?
> There is no single NOTICE file here.
> Each ASF NO
Hi,
Change that to “may not be” :-)
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Right, I was referring to the copyright line. Of course, if an Apache
project has multiple copyright attributions, then the downstream project
would need to include those as well if bundling the code.
On 14 May 2018 at 04:21, Justin Mclean wrote:
> Hi,
>
> Change that to “may not be” :-)
>
> Jus
On Sat, May 12, 2018 at 3:52 PM, Justin Mclean
wrote:
> Hi,
>
> Sorry but it’s -1 binding due to compiled code in source release.
>
Can anyone point me the ASF policy page about this - "compiled code in
source release"?
>
> Frankly I’m surprised to see so many +1s with this obvious issue.
>
>
I'm not sure about a specific policy, but sources by definition aren't the
binaries. Sources combine with a tool or tools to create binaries.
On 14 May 2018 at 12:41, Sijie Guo wrote:
> On Sat, May 12, 2018 at 3:52 PM, Justin Mclean
> wrote:
>
> > Hi,
> >
> > Sorry but it’s -1 binding due to co
On Sun, May 13, 2018 at 7:49 PM, Matt Sicker wrote:
> On 13 May 2018 at 12:10, Matteo Merli wrote:
>
> > The code in question is testing a feature that takes Jars from a user and
> > execute the code contained. Indeed the Jar should not be in the sources,
> > though I believe the test is correct
On Thu, May 10, 2018 at 6:50 PM, Julian Hyde wrote:
> ...In other words, there are several ways to prove that a binary release
> is WRONG but (to Greg’s point) there is no way to prove it RIGHT
One useful thing that people could do with binary artifacts is to say
"I use the binary with sha256
Hi -
> On May 14, 2018, at 10:57 AM, Sijie Guo wrote:
>
> On Sun, May 13, 2018 at 7:49 PM, Matt Sicker wrote:
>
>> On 13 May 2018 at 12:10, Matteo Merli wrote:
>>
>>> The code in question is testing a feature that takes Jars from a user and
>>> execute the code contained. Indeed the Jar shou
On Mon, May 14, 2018 at 10:53 AM, Matt Sicker wrote:
> I'm not sure about a specific policy, but sources by definition aren't the
> binaries. Sources combine with a tool or tools to create binaries.
>
Okay. But this is a test "resource" used by other sources on testing.
Image you are writing an
On Mon, May 14, 2018 at 11:16 AM, Dave Fisher wrote:
> Hi -
>
> > On May 14, 2018, at 10:57 AM, Sijie Guo wrote:
> >
> > On Sun, May 13, 2018 at 7:49 PM, Matt Sicker wrote:
> >
> >> On 13 May 2018 at 12:10, Matteo Merli wrote:
> >>
> >>> The code in question is testing a feature that takes Jar
If it is part of a releasable artifact, then source needs to be provided.
> On May 14, 2018, at 2:16 PM, Sijie Guo wrote:
>
> On Mon, May 14, 2018 at 10:53 AM, Matt Sicker wrote:
>
>> I'm not sure about a specific policy, but sources by definition aren't the
>> binaries. Sources combine with a
I am pleased to announce that the Incubator PMC has approved the release
of Apache Daffodil (incubating) 2.1.0.
The vote has passed with 4 binding +1 votes and no other votes.
The votes were:
+1 Matt Sicker (binding)
+1 Justin Mclean (binding)
+1 Dave Fisher (binding)
+1 John D. Ament (binding)
Hi Folks!
Several committers/PMC members from Apache Airflow cannot publish updates
to the Airflow incubator project page.
The steps below used to work for us:
Page at https://cwiki.apache.org/confluence/display/AIRFLOW/
Committers%27+Guide instructs doing the following:
1. Check out the svn
Hi,
> Okay. But this is a test "resource" used by other sources on testing.
Tests resources are not exempt.
> Image you are writing an image processing library, you include some
> "images" for testing the library. Is it allowed to include those "images"
> in the source release?
Including images
hi sid
can you access https with your credentials using curl e.g
curl --user https://cms.apache.org/incubator/publish
?
Martin
__
From: Sid Anand
Sent: Monday, May 14, 2018 5:30 PM
To: general@incubator.apache.o
I get the same error (I've hidden my password).
sianand@LM-SJN-21002367:~ $ curl --user sanand:
https://cms.apache.org/incubator/publish
404 Not Found
Page Not Found
The requested URL was not found on this server. If you are trying to
edit a CMS-driven page, your local working copy m
So, perhaps I (sanand) don't have the necessary permissions?
-s
On Mon, May 14, 2018 at 6:11 PM, Sid Anand wrote:
> I get the same error (I've hidden my password).
>
> sianand@LM-SJN-21002367:~ $ curl --user sanand:
> https://cms.apache.org/incubator/publish
>
>
>
>
>
> 404 Not Found
>
>
Hi Sid
as long as you have JavaScript enabled in the browser
and you gave the same issue with curl then AFAIK its a permissions error
can you contract admin or webmaster and have them email you valid
username/password
?
Martin
__
___
The Incubator website is no longer managed via CMS. Please review
https://incubator.apache.org/guides/website.html
John
On Mon, May 14, 2018 at 9:17 PM Martin Gainty wrote:
> Hi Sid
>
>
> as long as you have JavaScript enabled in the browser
> and you gave the same issue with curl then AFAIK i
21 matches
Mail list logo
