Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

[Felix Cheung]

This test is consistently failing when I build, any idea what’s wrong in my
setup?

- should print unicode correctly *** FAILED *** (101 milliseconds)
ExecuteSuccess(JObject(List((text/plain,JString(☺) did not equal
ExecuteSuccess(JObject(List((text/plain,JString(☺)
(PythonInterpreterSpec.scala:272)


On Tue, Mar 26, 2019 at 1:36 PM Marcelo Vanzin 
wrote:

> The Livy PPMC has voted to release Livy 0.6.0 RC2 as the next Livy release.
>
> Livy enables programmatic, fault-tolerant, multi-tenant submission of
> Spark jobs from web/mobile apps (no Spark client needed). So, multiple
> users can interact with your Spark cluster concurrently and reliably.
>
> Vote thread:
>
> https://lists.apache.org/thread.html/24c6c184f33c611aa83ec5d1c9948c96610b36df503b5e7f100ff4a2@%3Cdev.livy.apache.org%3E
>
> (Note I messed up the subject on the first e-mail, that thread is for
> the RC2 vote.)
>
> Result thread:
>
> https://lists.apache.org/thread.html/70c715f6394f06f0a49f76671b0f57cd1cdca35f7862a9ad2cf87fd7@%3Cdev.livy.apache.org%3E
>
> The RC is based on tag v0.6.0-incubating-rc2:
> https://github.com/apache/incubator-livy/commit/28be98cabc
>
> The release files can be found here:
> https://dist.apache.org/repos/dist/dev/incubator/livy/0.6.0-incubating-rc2/
>
> The staged maven artifacts can be found here:
> https://repository.apache.org/content/repositories/orgapachelivy-1008
>
> The list of resolved JIRAs in this release can be found here:
> https://issues.apache.org/jira/projects/LIVY/versions/12342736
>
> Vote will be open for at least 72 hours. Thanks!
>
> --
> Marcelo
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Setting up Tuweni

[Antoine Toulme]

Should I take further action to have infra's attention regarding [1]?

I believe there is a good process for that.

> On Mar 26, 2019, at 4:43 PM, Antoine Toulme  wrote:
> 
> Hi all,
> 
> I have added Tuweni to podlings,xml [0].
> I have also started tasks with infra to set up DNS and LDAP [1].
> 
> Please review and let me know if you see additional actions that may be taken.
> 
> I will request mailing lists, git repository and websites after DNS is 
> granted.
> 
> Cheers,
> 
> Antoine
> 
> [0]: http://svn.apache.org/viewvc?view=revision&revision=1856351 
> 
> [1]: https://issues.apache.org/jira/browse/INFRA-18110 
> 
> 


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

Re: [DISCUSS] Retirement Policy for Artifacts

[Henk P. Penning]

On Wed, 27 Mar 2019, Dave Fisher wrote:


Date: Wed, 27 Mar 2019 16:10:00 +
From: Dave Fisher 
To: general@incubator.apache.org
Subject: [DISCUSS] Retirement Policy for Artifacts

In INCUBATOR-198 Infra asked us to clean up Release artifacts from
archive.apache.org  for retired podlings.
I created INCUBATOR-233 so that we can make sure we are clear about
the policy before we undertake proper cleanup.


  Nothing should be removed from archive.apache.org,
  except, parhaps, for legal reasons.

  Groeten,

  HPP

   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/


When a Podling retires from the Incubator there are two exit states that might 
happen:

(1) Development simply stops.
(2) Development moves elsewhere. Either back to the donating entity or simply 
elsewhere.

Artifacts that are left that relate to code that may or may not be compliant 
with Apache Policy are:

(A) Code Repositories.
(B) Release Archives.
(C) Release Distributions.
(D) Dev Distributions. (These should always be deleted.)

A simple answer would be to keep everything where it is, and that would be easy except 
when the code has not been cleared for licensing issues. Fortunately, assuming that the 
podling PPMC or its Mentors have maintained the Podling Status Page we do have dates for 
licensing clearance that can be used. These are the dates in the “Copyright” and “Verify 
Distribution Rights” sections. Are there other dates to check? Are we over to the dates in 
content/podlings/.yml. Once we agree on the correct “date" to use. I 
propose that we adopt the following policy for retiring podlings:

(1) If the “date” is empty then we remove every Release and Repository. (We can 
allow a delay for people to grab “historical” copies.)
(2) If the "date" is filled in then the Repositories are marked Read Only and all 
Releases prior to that “date" are removed.

The effect is that we only preserve artifacts and code that can be considered 
to be conforming with Apache Release Policy and Code that is likely to be in 
good shape with respect to licensing.

I’d like to go for LAZY CONSENSUS after discussion for the next week or so.

Regards,
Dave



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

[DISCUSS] Retirement Policy for Artifacts

[Dave Fisher]

In INCUBATOR-198 Infra asked us to clean up Release artifacts from 
archive.apache.org  for retired podlings. I created 
INCUBATOR-233 so that we can make sure we are clear about the policy before we 
undertake proper cleanup.

When a Podling retires from the Incubator there are two exit states that might 
happen:

(1) Development simply stops.
(2) Development moves elsewhere. Either back to the donating entity or simply 
elsewhere.

Artifacts that are left that relate to code that may or may not be compliant 
with Apache Policy are:

(A) Code Repositories.
(B) Release Archives.
(C) Release Distributions.
(D) Dev Distributions. (These should always be deleted.)

A simple answer would be to keep everything where it is, and that would be easy 
except when the code has not been cleared for licensing issues. Fortunately, 
assuming that the podling PPMC or its Mentors have maintained the Podling 
Status Page we do have dates for licensing clearance that can be used. These 
are the dates in the “Copyright” and “Verify Distribution Rights” sections. Are 
there other dates to check? Are we over to the dates in 
content/podlings/.yml. Once we agree on the correct “date" to use. I 
propose that we adopt the following policy for retiring podlings:

(1) If the “date” is empty then we remove every Release and Repository. (We can 
allow a delay for people to grab “historical” copies.)
(2) If the "date" is filled in then the Repositories are marked Read Only and 
all Releases prior to that “date" are removed.

The effect is that we only preserve artifacts and code that can be considered 
to be conforming with Apache Release Policy and Code that is likely to be in 
good shape with respect to licensing.

I’d like to go for LAZY CONSENSUS after discussion for the next week or so.

Regards,
Dave

[jira] [Closed] (INCUBATOR-66) extract building community guide from the graduation guide

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher closed INCUBATOR-66.

Resolution: Done

Done, but never closed.

> extract building community guide from the graduation guide
> --
>
> Key: INCUBATOR-66
> URL: https://issues.apache.org/jira/browse/INCUBATOR-66
> Project: Incubator
>  Issue Type: Improvement
>  Components: site
>Reporter: Martijn Dashorst
>Priority: Major
>
> The graduation guide is quite a hand full and contains very important 
> information on how to build a community, that though important is not part of 
> the graduation procedure.
> Moving it into a separate guide and using it during incubation will make it 
> more clear and useful



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802912#comment-16802912
 ] 

Dave Fisher commented on INCUBATOR-234:
---

Some of the now outdated ideas in INCUBATOR-70 could be incorporated in the 
Cookbook

> Incubator Cookbook
> --
>
> Key: INCUBATOR-234
> URL: https://issues.apache.org/jira/browse/INCUBATOR-234
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> As discussed at [1] the goal is to create a single page Incubator Cookbook, 
> with all the details of the incubation process, in chronological order of the 
> incubation journey.
> This should be as concise as possible, with links to more information where 
> strictly needed, and adopt a friendly tone in the sense of clearly making the 
> Incubator a service to our podlings.
> Draft page at [http://incubator.apache.org/cookbook/] , built from small 
> pieces of content found under 
> [https://github.com/apache/incubator/tree/master/pages/cookbook]
> As a next step I'll focus on getting a mostly consistent set of topics and we 
> can then share the writing work.
>  [1] 
> https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Issue Comment Deleted] (INCUBATOR-231) Cleanup Git-generated Incubator website

[Dave Fisher (JIRA)]

 [ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Fisher updated INCUBATOR-231:
--
Comment: was deleted

(was: A few suggestions / questions.
# technical - add a hash link so that it is easy to link to specific sections 
of the cookbook. I have an idea of how to do that.
# Release Distribution Policy is an important part to discuss within releases. 
Not only does a podling need to follow Legal Policy for an Apache Release, but 
there must be a Release on Apache Distribution. This needs to be clear.
# How should exceptions to the normal course be handled in the cookbook? Should 
we use a footnote, glossary, or "info box")

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802900#comment-16802900
 ] 

Dave Fisher commented on INCUBATOR-234:
---

A few suggestions / questions.
# technical - add a hash link so that it is easy to link to specific sections 
of the cookbook. I have an idea of how to do that.
# Release Distribution Policy is an important part to discuss within releases. 
Not only does a podling need to follow Legal Policy for an Apache Release, but 
there must be a Release on Apache Distribution. This needs to be clear.
# How should exceptions to the normal course be handled in the cookbook? Should 
we use a footnote, glossary, or "info box"

> Incubator Cookbook
> --
>
> Key: INCUBATOR-234
> URL: https://issues.apache.org/jira/browse/INCUBATOR-234
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> As discussed at [1] the goal is to create a single page Incubator Cookbook, 
> with all the details of the incubation process, in chronological order of the 
> incubation journey.
> This should be as concise as possible, with links to more information where 
> strictly needed, and adopt a friendly tone in the sense of clearly making the 
> Incubator a service to our podlings.
> Draft page at [http://incubator.apache.org/cookbook/] , built from small 
> pieces of content found under 
> [https://github.com/apache/incubator/tree/master/pages/cookbook]
> As a next step I'll focus on getting a mostly consistent set of topics and we 
> can then share the writing work.
>  [1] 
> https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Comment Edited] (INCUBATOR-231) Cleanup Git-generated Incubator website

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802896#comment-16802896
 ] 

Dave Fisher edited comment on INCUBATOR-231 at 3/27/19 3:07 PM:


A few suggestions / questions.
# technical - add a hash link so that it is easy to link to specific sections 
of the cookbook. I have an idea of how to do that.
# Release Distribution Policy is an important part to discuss within releases. 
Not only does a podling need to follow Legal Policy for an Apache Release, but 
there must be a Release on Apache Distribution. This needs to be clear.
# How should exceptions to the normal course be handled in the cookbook? Should 
we use a footnote, glossary, or "info box"


was (Author: wave):
A few suggestions / questions.
# technical - add a hash link so that it is easy to link to specific sections 
of the cookbook. I have an idea of how to do that.
# Release Distribution Policy is an important part to discuss within releases. 
Not only does a pooling need to follow Legal Policy for an Apache Release, but 
there must be a Release on Apache Distribution. This needs to be clear.
# How should exceptions to the normal course be handled in the cookbook? Should 
we use a footnote, glossary, or "info box"

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website

[Dave Fisher (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802896#comment-16802896
 ] 

Dave Fisher commented on INCUBATOR-231:
---

A few suggestions / questions.
# technical - add a hash link so that it is easy to link to specific sections 
of the cookbook. I have an idea of how to do that.
# Release Distribution Policy is an important part to discuss within releases. 
Not only does a pooling need to follow Legal Policy for an Apache Release, but 
there must be a Release on Apache Distribution. This needs to be clear.
# How should exceptions to the normal course be handled in the cookbook? Should 
we use a footnote, glossary, or "info box"

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[Sebb (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802834#comment-16802834
 ] 

Sebb commented on INCUBATOR-234:


Also podlings may become part of an existing TLP rather than a new TLP

> Incubator Cookbook
> --
>
> Key: INCUBATOR-234
> URL: https://issues.apache.org/jira/browse/INCUBATOR-234
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> As discussed at [1] the goal is to create a single page Incubator Cookbook, 
> with all the details of the incubation process, in chronological order of the 
> incubation journey.
> This should be as concise as possible, with links to more information where 
> strictly needed, and adopt a friendly tone in the sense of clearly making the 
> Incubator a service to our podlings.
> Draft page at [http://incubator.apache.org/cookbook/] , built from small 
> pieces of content found under 
> [https://github.com/apache/incubator/tree/master/pages/cookbook]
> As a next step I'll focus on getting a mostly consistent set of topics and we 
> can then share the writing work.
>  [1] 
> https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802756#comment-16802756
 ] 

Bertrand Delacretaz commented on INCUBATOR-234:
---

Another suggestion by Nick Kwiatkowski on Twitter ( 
https://twitter.com/quetwo/status/1110863303465684999 ) is to add a 
"differences between podlings and top-level projects" section about this:

bq. Maybe better define PMC / PPMC?  Maybe a section on "Who should be on the 
PPMC / what values should a PPMC have" and "What is the difference between a 
PPMC member and a committer?"


> Incubator Cookbook
> --
>
> Key: INCUBATOR-234
> URL: https://issues.apache.org/jira/browse/INCUBATOR-234
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> As discussed at [1] the goal is to create a single page Incubator Cookbook, 
> with all the details of the incubation process, in chronological order of the 
> incubation journey.
> This should be as concise as possible, with links to more information where 
> strictly needed, and adopt a friendly tone in the sense of clearly making the 
> Incubator a service to our podlings.
> Draft page at [http://incubator.apache.org/cookbook/] , built from small 
> pieces of content found under 
> [https://github.com/apache/incubator/tree/master/pages/cookbook]
> As a next step I'll focus on getting a mostly consistent set of topics and we 
> can then share the writing work.
>  [1] 
> https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802754#comment-16802754
 ] 

Bertrand Delacretaz commented on INCUBATOR-234:
---

Suggestion from [~isa...@apache.org] on Twitter:

bq. What I would have found helpful in the "does your project fit the Apache 
Incubator" would have been a link of Apache's values so potential podlings can 
check if they match with what they want to aspire to. Maybe a link to 
https://blogs.apache.org/foundation/entry/the-apache-way-to-sustainable ?

> Incubator Cookbook
> --
>
> Key: INCUBATOR-234
> URL: https://issues.apache.org/jira/browse/INCUBATOR-234
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> As discussed at [1] the goal is to create a single page Incubator Cookbook, 
> with all the details of the incubation process, in chronological order of the 
> incubation journey.
> This should be as concise as possible, with links to more information where 
> strictly needed, and adopt a friendly tone in the sense of clearly making the 
> Incubator a service to our podlings.
> Draft page at [http://incubator.apache.org/cookbook/] , built from small 
> pieces of content found under 
> [https://github.com/apache/incubator/tree/master/pages/cookbook]
> As a next step I'll focus on getting a mostly consistent set of topics and we 
> can then share the writing work.
>  [1] 
> https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802642#comment-16802642
 ] 

Bertrand Delacretaz commented on INCUBATOR-234:
---

I have created an initial version at [http://incubator.apache.org/cookbook/] , 
covering (hopefully) all phases of incubation. There's a number of TODO, mostly 
about adding links to reference docs.

I'm not sure if building this page out of multiple small documents is really 
useful but that's a detail, I suggest that for now we focus on the content and 
try to make this a central place for podling community members to find 
information and get an overview on how things work.

Looking at the other incubator.a.o pages, a lot of information is presented as 
being specific to podlings - I'd rather point to the same docs as for top-level 
projects and just outline the small differences that apply to podlings, which 
works well in the context of that cookbook page.

This should allow us to greatly simplify the rest of the website.

> Incubator Cookbook
> --
>
> Key: INCUBATOR-234
> URL: https://issues.apache.org/jira/browse/INCUBATOR-234
> Project: Incubator
>  Issue Type: Task
>  Components: site
>Reporter: Bertrand Delacretaz
>Priority: Major
>
> As discussed at [1] the goal is to create a single page Incubator Cookbook, 
> with all the details of the incubation process, in chronological order of the 
> incubation journey.
> This should be as concise as possible, with links to more information where 
> strictly needed, and adopt a friendly tone in the sense of clearly making the 
> Incubator a service to our podlings.
> Draft page at [http://incubator.apache.org/cookbook/] , built from small 
> pieces of content found under 
> [https://github.com/apache/incubator/tree/master/pages/cookbook]
> As a next step I'll focus on getting a mostly consistent set of topics and we 
> can then share the writing work.
>  [1] 
> https://lists.apache.org/thread.html/51fe5d659778bed5b6385c7c39bbdf688d02f1b1dbe02d595d514cbb@%3Cgeneral.incubator.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

[Mark Struberg]

* sig ok
* LICENE ok
* NOTICE ok
* sha512 ok
* sources seem to have all the license headers
NetBeans 11 rc4  tested for 3 days now. Had a weird JavaFX module not 
found issue in the beginning but that somehow resolved itself after 
re-opening the projects.



+1 (IPMC binding)


LieGrue,
strub


Am 26.03.19 um 10:14 schrieb Laszlo Kishalmi:

Dear all,

As its community has been voted positively on it, the incubating 
Apache NetBeans project wishes to release their 11.0 version.


PPMC Vote Thread: 
https://lists.apache.org/thread.html/290786ea9eda2215a93ca18084945d655053597ca9745ecc6d555d79@%3Cdev.netbeans.apache.org%3E


PPMC Result Thread: 
https://lists.apache.org/thread.html/c406ae1a45c282811af1a77089173c67b44f674507c894407e05c844@%3Cdev.netbeans.apache.org%3E


We have one +1 IPMC binding vote to carry over from:

Ate Douma (http://people.apache.org/phonebook.html?uid=ate)

Please see our release specific Wiki page for other details:
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.0


Apache NetBeans 11.0 (incubating) constitutes all clusters in the 
Apache NetBeans Git repo, which together provide the NetBeans Platform 
(i.e., the underlying application framework), as well as all the 
modules that provide the Java SE, Java EE, PHP, JavaScript and Groovy 
features of Apache NetBeans.


In short, Apache NetBeans 11.0 (incubating) is a full IDE for Java SE, 
Java EE, PHP and JavaScript development with some Groovy language 
support.


Build artifacts available here:
https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans/incubating-11.0-vc4/ 



Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and 
NOTICE files, as well as a README file with build instructions, which 
are the same as these:


https://github.com/apache/incubator-netbeans/blob/release110/README.md

We are voting on:
https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans/incubating-11.0-vc4/incubating-netbeans-11.0-vc4-source.zip 



SHA512:
e1ffe7873142bf6718f4365480501bec81126dc8e90884ea74f0cbc5d86a034ae3182515c4b78ccb250786bf84774d600f0b9451a6c518f773ca611cf82e4197 
./incubating-netbeans-11.0-vc4-source.zip


KEYS file:

https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS

Apache NetBeans Git Repo tag: 11.0-vc4 :
https://github.com/apache/incubator-netbeans/tree/11.0-vc4

Note: NetBeans license violation checks are managed via the 
rat-exclusions.txt file:


https://github.com/apache/incubator-netbeans/blob/release110/nbbuild/rat-exclusions.txt 



Rat report shows no unknown licenses, except for license files:

https://builds.apache.org/job/incubator-netbeans-release/404/artifact/rat-release-temp/nbbuild/build/rat-report.txt 



Included as a convenience binary, not relevant for the voting purposes 
(unzip it, run it and you'll see Apache NetBeans):


https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans/incubating-11.0-vc4/incubating-netbeans-11.0-vc4-bin.zip 



SHA512:
9d7fbe5c6bcf781fc1d3f8e2aee62db0435dd716c60dc73ef900ee2817473cc5b0a8e12c1453b7e57aedcece70cff778673a8cf563c1fa4eea816d9636955d4b 
./incubating-netbeans-11.0-vc4-bin.zip


Release specific wiki page:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.0

How (and what) to try out the release:

1. Download the artifact to be voted on and unzip it.
2. Check that the artifact does not contain any jar files,
   save the: 
platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar 
and
   enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar and 
enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar 
which are only jars by their name

3. Verify the cryptographic signatures, the NOTICE and LICENSE file
4. Build it using the README provided by the artifact.
5. Look in nbbuild/netbeans for the NetBeans installation created by 
the build process.



This vote is going to be open at least 72 hours, vote with +1, 0, and 
-1 as usual.


Thank you for the hard work!

Laszlo Kishalmi
Volunteer Release Manager of Apache NetBeans 11.0




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

Re: Setting up Tuweni

[Antoine Toulme]

Thanks for the help!

> On Mar 26, 2019, at 4:54 PM, Dave Fisher  wrote:
> 
> Actually the start date and monthly report dates needed to be changed.
> 
> I appreciate that the instructions are not very clear.
> 
> Regards,
> Dave
> 
>> On Mar 26, 2019, at 4:49 PM, Dave Fisher  wrote:
>> 
>> Hi Antoine,
>> 
>> The podlings.xml change looks good to me.
>> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Mar 26, 2019, at 4:43 PM, Antoine Toulme  wrote:
>>> 
>>> Hi all,
>>> 
>>> I have added Tuweni to podlings,xml [0].
>>> I have also started tasks with infra to set up DNS and LDAP [1].
>>> 
>>> Please review and let me know if you see additional actions that may be 
>>> taken.
>>> 
>>> I will request mailing lists, git repository and websites after DNS is 
>>> granted.
>>> 
>>> Cheers,
>>> 
>>> Antoine
>>> 
>>> [0]: http://svn.apache.org/viewvc?view=revision&revision=1856351 
>>> 
>>> [1]: https://issues.apache.org/jira/browse/INFRA-18110 
>>> 
>>> 
>> 
>> 
>> -
>> 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
> 


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