[CANCEL][VOTE] Apache Crail 1.0-incubating (RC2)

[Jonas Pfefferle]

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 leading directory named after the release would be better:

$ tar tvfz apache-crail-1.0-rc2-incubating-source.tar.gz |head -3
drwxr-xr-x  0 jpf    jpf         0 Apr 23 04:32 apache-crail-1.0-incubating-src/
drwxr-xr-x  0 jpf    jpf         0 Apr 23 04:32 
apache-crail-1.0-incubating-src/client/
-rw-r--r--  0 jpf    jpf      2625 Apr 23 04:32 
apache-crail-1.0-incubating-src/client/pom.xml


We can include the rcX in the filename but leave it out in the directory 
name. What do you think?


Release artifacts have been signed with the following key:
https://people.apache.org/keys/committer/pepperjo.asc

(I will include this in future call for vote emails)

Thanks,
Jonas

   On Fri, 11 May 2018 17:12:43 +1000
   Justin Mclean  wrote:

Hi,

-1 (binding) as missing DISCLAIMER and NOTICE is incorrect

I checked:
- incubating in name
- DISCLAIMER is missing
- NOTICE is not correct (see below)
- LICENSE is fine
- no binary files in release
- all source files have asf headers

The notice fine has two conflicting copyright with overlapping years I’m not 
sure how it can be copyright ASF and IBM at the some time, unless those 
copyright lines refer to parts of the code base?

Apache Crail incubating
Copyright (C) 2017-2018, The Apache Software Foundation.   Copyright (C) 
2015-2018, IBM Corporation Would also be nice to sign the artefacts with an 
apache.org email address.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org







-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3

[sebb]

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 need to copy into your NOTICE
>> file. But for other permissive licenses you don't do this.
>>
>
> 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 NOTICE file is potentially different depending on the included code.

If ASF project A includes code from ASF project B, the project A
NOTICE file may or may not need updating to take account of the NOTICE
file from project B.
This depends on whether the code from project B needs any specific
terms from NOTICE B.

> --
> Matt Sicker 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3

[Justin Mclean]

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 NOTICE file is potentially different depending on the included code.

He was just referring to the copyright line not the entire NOTICE file I 
believe. As both projects are ASF license there’s no need to duplicate that 
line. [1]

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#bundle-asf-product
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3

[Justin Mclean]

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

Re: [VOTE] Release Apache Daffodil (incubating) 2.1.0-rc3

[Matt Sicker]

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” :-)
>
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Matt Sicker 

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Sijie Guo]

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 checked:
> - incubating in name
> - signatures and hashes correct
> - DISCLAIMER exists
> - LICENSE and NOTICE good
> - Unexpected jar in source release [1]
> - All source files have headers
>
> Thanks,
> Justin
>
>
> 1.  pulsar-functions/utils/src/test/resources/multifunction.jar
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Matt Sicker]

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 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 checked:
> > - incubating in name
> > - signatures and hashes correct
> > - DISCLAIMER exists
> > - LICENSE and NOTICE good
> > - Unexpected jar in source release [1]
> > - All source files have headers
> >
> > Thanks,
> > Justin
> >
> >
> > 1.  pulsar-functions/utils/src/test/resources/multifunction.jar
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>



-- 
Matt Sicker 

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Sijie Guo]

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 here: we need to validate the
> specific
> > feature by dynamically loading a Jar.
> >
>
> By generating the binary jar from source files at test time, you'd avoid
> bundling any binary output files.
>

I made the original change long time back in pulsar-functions for testing
submitting user-defined function. When we first contribute pulsar-functions
to pulsar, we probably didn't clean that up.
The intention behind that change is not including any source code or jar in
the test dependency tree. As including source code would make the testing
function as part of the test dependency, it would volatile the purpose of
testing submitting a user defined function. In this case,
"multifunction.jar" is the a "user-defined" function as the test resource.





>
>
> > > (e.g., injecting a
> > module-info.class file at build time rather than requiring Java 9+ to
> build
> > regardless).
> >
> > I don't see any place in the code where we are using "module-info.class"
> > and the project requires Java 8 and not 9.
> >
>
> Sorry for the confusion, that was just an example from a problem I've seen
> before in another project.
>
> --
> Matt Sicker 
>

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

[Bertrand Delacretaz]

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 digest XYZ and it works for me" - but
that doesn't make the Apache Releases, they are still unverifiable
binaries regardless.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Dave Fisher]

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 should not be in the sources,
>>> though I believe the test is correct here: we need to validate the
>> specific
>>> feature by dynamically loading a Jar.
>>> 
>> 
>> By generating the binary jar from source files at test time, you'd avoid
>> bundling any binary output files.
>> 
> 
> I made the original change long time back in pulsar-functions for testing
> submitting user-defined function. When we first contribute pulsar-functions
> to pulsar, we probably didn't clean that up.
> The intention behind that change is not including any source code or jar in
> the test dependency tree. As including source code would make the testing
> function as part of the test dependency, it would volatile the purpose of
> testing submitting a user defined function. In this case,
> "multifunction.jar" is the a "user-defined" function as the test resource.

To be succinct The ASF produces open source software and including a 
pre-compiled binary in the release means that the project fails the open source 
definition. [1]

It really doesn’t matter how or why. You will need to provide the source (as 
simple as it might be) and the maven configuration to build that trivial jar.

Regards,
Dave

[1] https://opensource.org/osd

> 
> 
> 
> 
> 
>> 
>> 
 (e.g., injecting a
>>> module-info.class file at build time rather than requiring Java 9+ to
>> build
>>> regardless).
>>> 
>>> I don't see any place in the code where we are using "module-info.class"
>>> and the project requires Java 8 and not 9.
>>> 
>> 
>> Sorry for the confusion, that was just an example from a problem I've seen
>> before in another project.
>> 
>> --
>> Matt Sicker 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Sijie Guo]

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 image processing library, you include some
"images" for testing the library. Is it allowed to include those "images"
in the source release?

If you change "image" to "functions", pulsar-functions provides a
framework/library for processing functions, we include some user-defined
"functions" (aka jars) as test resources for testing the library. Is it
allowed or not?

>From what I can see here, the jars included in source binary are test
resources for testing. What is the ASF policy for handling test resources?


- Sijie




>
> 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 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 checked:
> > > - incubating in name
> > > - signatures and hashes correct
> > > - DISCLAIMER exists
> > > - LICENSE and NOTICE good
> > > - Unexpected jar in source release [1]
> > > - All source files have headers
> > >
> > > Thanks,
> > > Justin
> > >
> > >
> > > 1.  pulsar-functions/utils/src/test/resources/multifunction.jar
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>
>
>
> --
> Matt Sicker 
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Sijie Guo]

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 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 here: we need to validate the
> >> specific
> >>> feature by dynamically loading a Jar.
> >>>
> >>
> >> By generating the binary jar from source files at test time, you'd avoid
> >> bundling any binary output files.
> >>
> >
> > I made the original change long time back in pulsar-functions for testing
> > submitting user-defined function. When we first contribute
> pulsar-functions
> > to pulsar, we probably didn't clean that up.
> > The intention behind that change is not including any source code or jar
> in
> > the test dependency tree. As including source code would make the testing
> > function as part of the test dependency, it would volatile the purpose of
> > testing submitting a user defined function. In this case,
> > "multifunction.jar" is the a "user-defined" function as the test
> resource.
>
> To be succinct The ASF produces open source software and including a
> pre-compiled binary in the release means that the project fails the open
> source definition. [1]
>
> It really doesn’t matter how or why. You will need to provide the source
> (as simple as it might be) and the maven configuration to build that
> trivial jar.
>

Okay. So if we provide the source file of that jar, is it allowed to
include a pre-compiled binary as test resources?



>
> Regards,
> Dave
>
> [1] https://opensource.org/osd
>
> >
> >
> >
> >
> >
> >>
> >>
>  (e.g., injecting a
> >>> module-info.class file at build time rather than requiring Java 9+ to
> >> build
> >>> regardless).
> >>>
> >>> I don't see any place in the code where we are using
> "module-info.class"
> >>> and the project requires Java 8 and not 9.
> >>>
> >>
> >> Sorry for the confusion, that was just an example from a problem I've
> seen
> >> before in another project.
> >>
> >> --
> >> Matt Sicker 
> >>
>
>

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Jim Jagielski]

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 tool or tools to create binaries.
>> 
> 
> Okay. But this is a test "resource" used by other sources on testing.
> 
> 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?
> 
> If you change "image" to "functions", pulsar-functions provides a
> framework/library for processing functions, we include some user-defined
> "functions" (aka jars) as test resources for testing the library. Is it
> allowed or not?
> 
> From what I can see here, the jars included in source binary are test
> resources for testing. What is the ASF policy for handling test resources?
> 
> 
> - Sijie
> 
> 
> 
> 
>> 
>> 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 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 checked:
 - incubating in name
 - signatures and hashes correct
 - DISCLAIMER exists
 - LICENSE and NOTICE good
 - Unexpected jar in source release [1]
 - All source files have headers
 
 Thanks,
 Justin
 
 
 1.  pulsar-functions/utils/src/test/resources/multifunction.jar
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 
 
>>> 
>> 
>> 
>> 
>> --
>> Matt Sicker 
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE] Release Apache Daffodil (incubating) 2.1.0

[Steve Lawrence]

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)

Vote thread:
https://lists.apache.org/thread.html/bfa624a2eefb1c1c193f0c497f6dcc46172d9fa9a0e3fcd37464f95e@%3Cgeneral.incubator.apache.org%3E

Thank you for your support!

We'll continue with the release now.
- Steve

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Cannot access https://cms.apache.org/incubator/publish

[Sid Anand]

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 repo at https://svn.apache.org/
   repos/asf/incubator/public/trunk/content/projects
   
   2. Update {local_working_dir}/content/projects/airflow.xml
   3. svn commit -m "Adding xxx as committer/pmc member to apache airflow"
   4. Publish to the incubator website using https://cms.apache.org/
   incubator/publish
   5. Verify your change on http://incubator.apache.
   org/projects/airflow.html


I completed first 3 steps but I can't access the link (
https://cms.apache.org/incubator/publish) on 4th step and it gives me
following error:

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 may have been pruned.
> Please go to cms.apache.org, find your project, and click on 'force new
> working copy' to create a new working copy to edit.

Re: [VOTE] Pulsar Release 2.0.0-rc1-incubating Candidate 3

[Justin Mclean]

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 is fine they are not compiled code, it's not that binary files 
are not allowed but compiled code isn’t allowed. If you have compiled code it’s 
not open source even if you include the source code. There’s also probably no 
way to determine if the compile coded come from the included source code or not.

Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Cannot access https://cms.apache.org/incubator/publish

[Martin Gainty]

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.org
Subject: Cannot access https://cms.apache.org/incubator/publish

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 repo at https://svn.apache.org/
   repos/asf/incubator/public/trunk/content/projects
   
   2. Update {local_working_dir}/content/projects/airflow.xml
   3. svn commit -m "Adding xxx as committer/pmc member to apache airflow"
   4. Publish to the incubator website using https://cms.apache.org/
   incubator/publish
   5. Verify your change on http://incubator.apache.
   org/projects/airflow.html


I completed first 3 steps but I can't access the link (
https://cms.apache.org/incubator/publish) on 4th step and it gives me
following error:

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 may have been pruned.
> Please go to cms.apache.org, find your project, and click on 'force new
> working copy' to create a new working copy to edit.

Re: Cannot access https://cms.apache.org/incubator/publish

[Sid Anand]

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 may have been pruned.

Please go to cms.apache.org, find
your project, and click on 'force new working copy' to create a new

working copy to edit.




On Mon, May 14, 2018 at 4:22 PM, Martin Gainty  wrote:

> 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.org
> *Subject:* Cannot access https://cms.apache.org/incubator/publish
>
> 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 repo at https://svn.apache.org/
>repos/asf/incubator/public/trunk/content/projects
> content/projects>
>2. Update {local_working_dir}/content/projects/airflow.xml
>3. svn commit -m "Adding xxx as committer/pmc member to apache airflow"
>4. Publish to the incubator website using https://cms.apache.org/
>incubator/publish
>5. Verify your change on http://incubator.apache.
>org/projects/airflow.html
>
>
> I completed first 3 steps but I can't access the link (
> https://cms.apache.org/incubator/publish) on 4th step and it gives me
> following error:
>
> 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 may have been pruned.
> > Please go to cms.apache.org, find your project, and click on 'force new
> > working copy' to create a new working copy to edit.
>

Re: Cannot access https://cms.apache.org/incubator/publish

[Sid Anand]

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
>
> 
>
> 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 may have been pruned.
>
> Please go to cms.apache.org, find
> your project, and click on 'force new working copy' to create a new
>
> working copy to edit.
>
> 
>
>
> On Mon, May 14, 2018 at 4:22 PM, Martin Gainty 
> wrote:
>
>> 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.org
>> *Subject:* Cannot access https://cms.apache.org/incubator/publish
>>
>> 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 repo at https://svn.apache.org/
>>repos/asf/incubator/public/trunk/content/projects
>>> tent/projects>
>>2. Update {local_working_dir}/content/projects/airflow.xml
>>3. svn commit -m "Adding xxx as committer/pmc member to apache airflow"
>>4. Publish to the incubator website using https://cms.apache.org/
>>incubator/publish
>>5. Verify your change on http://incubator.apache.
>>org/projects/airflow.html
>>
>>
>> I completed first 3 steps but I can't access the link (
>> https://cms.apache.org/incubator/publish) on 4th step and it gives me
>> following error:
>>
>> 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 may have been pruned.
>> > Please go to cms.apache.org, find your project, and click on 'force new
>> > working copy' to create a new working copy to edit.
>>
>
>

Re: Cannot access https://cms.apache.org/incubator/publish

[Martin Gainty]

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
__




From: Sid Anand 
Sent: Monday, May 14, 2018 9:12 PM
To: Martin Gainty
Cc: general@incubator.apache.org
Subject: Re: Cannot access https://cms.apache.org/incubator/publish

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
>
> 
>
> 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 may have been pruned.
>
> Please go to cms.apache.org, find
> your project, and click on 'force new working copy' to create a new
>
> working copy to edit.
>
> 
>
>
> On Mon, May 14, 2018 at 4:22 PM, Martin Gainty 
> wrote:
>
>> 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.org
>> *Subject:* Cannot access https://cms.apache.org/incubator/publish
>>
>> 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 repo at https://svn.apache.org/
>>repos/asf/incubator/public/trunk/content/projects
>>> tent/projects>
>>2. Update {local_working_dir}/content/projects/airflow.xml
>>3. svn commit -m "Adding xxx as committer/pmc member to apache airflow"
>>4. Publish to the incubator website using https://cms.apache.org/
>>incubator/publish
>>5. Verify your change on http://incubator.apache.
>>org/projects/airflow.html
>>
>>
>> I completed first 3 steps but I can't access the link (
>> https://cms.apache.org/incubator/publish) on 4th step and it gives me
>> following error:
>>
>> 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 may have been pruned.
>> > Please go to cms.apache.org, find your project, and click on 'force new
>> > working copy' to create a new working copy to edit.
>>
>
>

Re: Cannot access https://cms.apache.org/incubator/publish

[John D. Ament]

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 its a permissions error
>
>
> can you contract admin or webmaster and have them email you valid
> username/password
>
> ?
>
> Martin
> __
>
>
>
> 
> From: Sid Anand 
> Sent: Monday, May 14, 2018 9:12 PM
> To: Martin Gainty
> Cc: general@incubator.apache.org
> Subject: Re: Cannot access https://cms.apache.org/incubator/publish
>
> 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
> >
> > 
> >
> > 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 may have been pruned.
> >
> > Please go to cms.apache.org,
> find
> > your project, and click on 'force new working copy' to create a new
> >
> > working copy to edit.
> >
> > 
> >
> >
> > On Mon, May 14, 2018 at 4:22 PM, Martin Gainty 
> > wrote:
> >
> >> 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.org
> >> *Subject:* Cannot access https://cms.apache.org/incubator/publish
> >>
> >> 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 repo at https://svn.apache.org/
> >>repos/asf/incubator/public/trunk/content/projects
> >> >> tent/projects>
> >>2. Update {local_working_dir}/content/projects/airflow.xml
> >>3. svn commit -m "Adding xxx as committer/pmc member to apache
> airflow"
> >>4. Publish to the incubator website using https://cms.apache.org/
> >>incubator/publish
> >>5. Verify your change on http://incubator.apache.
> >>org/projects/airflow.html
> >>
> >>
> >> I completed first 3 steps but I can't access the link (
> >> https://cms.apache.org/incubator/publish) on 4th step and it gives me
> >> following error:
> >>
> >> 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 may have been pruned.
> >> > Please go to cms.apache.org, find your project, and click on 'force
> new
> >> > working copy' to create a new working copy to edit.
> >>
> >
> >
>