[jira] [Updated] (INCUBATOR-265) Maybe incorrect clarification in Graduation Guide
[ https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonglun Zhang updated INCUBATOR-265: Summary: Maybe incorrect clarification in Graduation Guide (was: Maybe typo in Graduation Guide) > Maybe incorrect clarification in Graduation Guide > - > > Key: INCUBATOR-265 > URL: https://issues.apache.org/jira/browse/INCUBATOR-265 > Project: Incubator > Issue Type: Improvement > Components: guides >Reporter: Yonglun Zhang >Priority: Major > > The second section of > [http://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project] > > Graduation *as a project* requires the formation of the new project by the > [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board]. > > I think change *as a project* to *as a top level project* makes sense. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULTS][VOTE] Release Apache NuttX (Incubating) 10.1.0 [RC1]
On Mon, May 17, 2021 at 8:13 PM 张铎(Duo Zhang) wrote: > I think the understanding here is that, for incubator projects, only the > votes from IPMC members are 'binding'. Maybe we could change the wording > next time to avoid confusion. > > There are 4 PPMC members voted +1, so we have enough PPMC members here. That distinction is slightly confusing but the PPMC voted successfully to release so now we are asking the IPMC to cast (binding IPMC) votes. Thanks, Nathan
Re: [RESULTS][VOTE] Release Apache NuttX (Incubating) 10.1.0 [RC1]
I think the understanding here is that, for incubator projects, only the votes from IPMC members are 'binding'. Maybe we could change the wording next time to avoid confusion. There are 4 PPMC members voted +1, so we have enough PPMC members here. Thanks. Willem Jiang 于2021年5月18日周二 上午6:56写道： > Hi, > I just checked the vote result and found out the PPMC vote has 4 > non-binding votes. > Don't we have enough PPMC to vote, or is it just a typo? > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, May 10, 2021 at 7:58 AM Alin Jerpelea wrote: > > > > Hello all, > > > > > > > > This is a call for a vote to release Apache NuttX (Incubating) version > > > > 10.1.0. > > > > > > > > The Apache NuttX community has voted on and approved a proposal to > > > > release Apache NuttX (Incubating) version 10.1.0. > > > > > > > > We now kindly request the Incubator PMC members review and vote on this > > > > incubator release. > > > > > > > > NuttX is a real-time operating system (RTOS) with an emphasis on > > > > standards compliance and small footprint. Scalable from 8-bit to 64-bit > > > > microcontroller environments, the primary governing standards in NuttX > > > > are Posix and ANSI standards. Additional standard APIs from Unix and > > > > other common RTOS’s (such as VxWorks) are adopted for functionality not > > > > available under these standards, or for functionality that is not > > > > appropriate for deeply- embedded environments (such as fork()). > > > > > > > > Because this project targets embedded systems there is more complexity > > > > involved in the build process. > > > > > > > > Apache NuttX community vote and result thread: > > > > Result: > > > > > https://lists.apache.org/thread.html/r497704eea8d24bfb68a309369319ec1955d69b6cfec66480e7b0638d%40%3Cdev.nuttx.apache.org%3E > > > > > > Vote: > > > > > https://lists.apache.org/thread.html/ra60b4173945cfd2a33924cc8d707863039c1764a7ea8e47a1d8502a0%40%3Cdev.nuttx.apache.org%3E > > > > > > > > SCM Information: > > > > Release tag: nuttx-10.1.0-RC1 > > > > Hash for the release incubating-nuttx tag: > > > > 3130ff691e386934eb276587a24d1efacf3bb30b > > > > Hash for the release incubating-nuttx-apps tag: > > > > 4348d91d1356335483089c3865282d80f13bedcd > > > > > > > > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC1/ > > > > [2] > > > > > https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes > > > > [3] https://www.apache.org/dev/release.html#approving-a-release > > > > [4] > > > > > https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release > > > > > > > > The vote will be open for at least 72 hours. > > > > > > > > Please vote accordingly: > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > > > > > Alin Jerpelea > > > > > > > > Apache NuttX > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [RESULTS][VOTE] Release Apache NuttX (Incubating) 10.1.0 [RC1]
Hi, I just checked the vote result and found out the PPMC vote has 4 non-binding votes. Don't we have enough PPMC to vote, or is it just a typo? Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, May 10, 2021 at 7:58 AM Alin Jerpelea wrote: > > Hello all, > > > > This is a call for a vote to release Apache NuttX (Incubating) version > > 10.1.0. > > > > The Apache NuttX community has voted on and approved a proposal to > > release Apache NuttX (Incubating) version 10.1.0. > > > > We now kindly request the Incubator PMC members review and vote on this > > incubator release. > > > > NuttX is a real-time operating system (RTOS) with an emphasis on > > standards compliance and small footprint. Scalable from 8-bit to 64-bit > > microcontroller environments, the primary governing standards in NuttX > > are Posix and ANSI standards. Additional standard APIs from Unix and > > other common RTOS’s (such as VxWorks) are adopted for functionality not > > available under these standards, or for functionality that is not > > appropriate for deeply- embedded environments (such as fork()). > > > > Because this project targets embedded systems there is more complexity > > involved in the build process. > > > > Apache NuttX community vote and result thread: > > Result: > > https://lists.apache.org/thread.html/r497704eea8d24bfb68a309369319ec1955d69b6cfec66480e7b0638d%40%3Cdev.nuttx.apache.org%3E > > > Vote: > > https://lists.apache.org/thread.html/ra60b4173945cfd2a33924cc8d707863039c1764a7ea8e47a1d8502a0%40%3Cdev.nuttx.apache.org%3E > > > > SCM Information: > > Release tag: nuttx-10.1.0-RC1 > > Hash for the release incubating-nuttx tag: > > 3130ff691e386934eb276587a24d1efacf3bb30b > > Hash for the release incubating-nuttx-apps tag: > > 4348d91d1356335483089c3865282d80f13bedcd > > > > [1] https://dist.apache.org/repos/dist/dev/incubator/nuttx/10.1.0-RC1/ > > [2] > > https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-10.1.0-RC1/ReleaseNotes > > [3] https://www.apache.org/dev/release.html#approving-a-release > > [4] > > https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release > > > > The vote will be open for at least 72 hours. > > > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Alin Jerpelea > > > > Apache NuttX - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: How to understand cut a release
Thanks for John and Sheng pointed out these statements can be treated equally. If so, I can do a paraphrase instead of a direct translation. -- Zhang Yonglun Apache ShenYu (Incubating) Apache ShardingSphere Sheng Wu 于2021年5月17日周一 下午11:20写道： > I think this is better to explain from English native speakers. :) > > From my understanding, cut sometimes is about having the commit id(point) > to begin the release process. publish is more closing to release done. > But from translating perspective, such as in the Chinese perspective, there > is no much difference, even they are even truly having the above > difference(maybe not). > > Sheng Wu 吴晟 > Twitter, wusheng1108 > > > Zhang Yonglun 于2021年5月17日周一 下午11:10写道： > > > Hi, > > > > In the 'Creating an Apache Release' section of the graduation guide [1], > I > > am a little confused by the statements of 'cut a release', 'publish a > > release' and 'create a release'. What's the difference between them? > > I really know what this section means generally, but when I tried to > > translate I met difficult. > > I thought these three statements are equal previous, but I'm not sure > now. > > > > > Podlings do not need to actually *publish *a release to demonstrate > that > > they understand how to accomplish such a feat. However, creating a > release > > that is approved by the incubator project management committee is usually > > the simplest way to do this. > > > > What does the highlight *publish* imply? Anyway, I get 'create a release' > > is better. > > > > > If you are going to cut a release (which is highly recommended), then > > please read the Incubator Release Management Guide for hints, tips and > > guidelines for cutting a release that will get approved by the IPMC > without > > problems. > > > > Why recommend 'cut a release' this time instead of 'create a release'? > > > > I am trying to translate this guide to local language, it's very > appreciate > > if anyone could help. > > > > > > [1] > http://incubator.apache.org/guides/graduation.html#creating_an_apache > > _release > > > > -- > > > > Zhang Yonglun > > Apache ShenYu (Incubating) > > Apache ShardingSphere > > >
Re: How to understand cut a release
I think this is better to explain from English native speakers. :) >From my understanding, cut sometimes is about having the commit id(point) to begin the release process. publish is more closing to release done. But from translating perspective, such as in the Chinese perspective, there is no much difference, even they are even truly having the above difference(maybe not). Sheng Wu 吴晟 Twitter, wusheng1108 Zhang Yonglun 于2021年5月17日周一 下午11:10写道： > Hi, > > In the 'Creating an Apache Release' section of the graduation guide [1], I > am a little confused by the statements of 'cut a release', 'publish a > release' and 'create a release'. What's the difference between them? > I really know what this section means generally, but when I tried to > translate I met difficult. > I thought these three statements are equal previous, but I'm not sure now. > > > Podlings do not need to actually *publish *a release to demonstrate that > they understand how to accomplish such a feat. However, creating a release > that is approved by the incubator project management committee is usually > the simplest way to do this. > > What does the highlight *publish* imply? Anyway, I get 'create a release' > is better. > > > If you are going to cut a release (which is highly recommended), then > please read the Incubator Release Management Guide for hints, tips and > guidelines for cutting a release that will get approved by the IPMC without > problems. > > Why recommend 'cut a release' this time instead of 'create a release'? > > I am trying to translate this guide to local language, it's very appreciate > if anyone could help. > > > [1] http://incubator.apache.org/guides/graduation.html#creating_an_apache > _release > > -- > > Zhang Yonglun > Apache ShenYu (Incubating) > Apache ShardingSphere >
Re: How to understand cut a release
On Mon, May 17, 2021 at 11:10 AM Zhang Yonglun wrote: > Hi, > > In the 'Creating an Apache Release' section of the graduation guide [1], I > am a little confused by the statements of 'cut a release', 'publish a > release' and 'create a release'. What's the difference between them? > I really know what this section means generally, but when I tried to > translate I met difficult. > I thought these three statements are equal previous, but I'm not sure now. > > > Podlings do not need to actually *publish *a release to demonstrate that > they understand how to accomplish such a feat. However, creating a release > that is approved by the incubator project management committee is usually > the simplest way to do this. > > What does the highlight *publish* imply? Anyway, I get 'create a release' > is better. > I think from a translation POV you should treat all of these statements the same. We may even find that it makes sense to simplify the guide to cut down on englsih specific idioms that may not translate well. They all essentially mean that the graduating podling: - Knows the licensing requirements of what code is going into your *source release* - Knows where to stage the source release - Knows how to conduct votes on the releases - Knows how to archive old releases > > > If you are going to cut a release (which is highly recommended), then > please read the Incubator Release Management Guide for hints, tips and > guidelines for cutting a release that will get approved by the IPMC without > problems. > > Why recommend 'cut a release' this time instead of 'create a release'? > > I am trying to translate this guide to local language, it's very appreciate > if anyone could help. > > > [1] http://incubator.apache.org/guides/graduation.html#creating_an_apache > _release > > -- > > Zhang Yonglun > Apache ShenYu (Incubating) > Apache ShardingSphere >
How to understand cut a release
Hi, In the 'Creating an Apache Release' section of the graduation guide [1], I am a little confused by the statements of 'cut a release', 'publish a release' and 'create a release'. What's the difference between them? I really know what this section means generally, but when I tried to translate I met difficult. I thought these three statements are equal previous, but I'm not sure now. > Podlings do not need to actually *publish *a release to demonstrate that they understand how to accomplish such a feat. However, creating a release that is approved by the incubator project management committee is usually the simplest way to do this. What does the highlight *publish* imply? Anyway, I get 'create a release' is better. > If you are going to cut a release (which is highly recommended), then please read the Incubator Release Management Guide for hints, tips and guidelines for cutting a release that will get approved by the IPMC without problems. Why recommend 'cut a release' this time instead of 'create a release'? I am trying to translate this guide to local language, it's very appreciate if anyone could help. [1] http://incubator.apache.org/guides/graduation.html#creating_an_apache _release -- Zhang Yonglun Apache ShenYu (Incubating) Apache ShardingSphere
[jira] [Commented] (INCUBATOR-265) Maybe typo in Graduation Guide
[ https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17346217#comment-17346217 ] John D. Ament commented on INCUBATOR-265: - I don't think typo is correct but clarification sure. The board would not vote on an existing TLP consuming a podling as a subproject. Typically though, a podling would only graduate into an existing TLP if that TLP was the sponsor instead of the incubator being the sponsor. > Maybe typo in Graduation Guide > -- > > Key: INCUBATOR-265 > URL: https://issues.apache.org/jira/browse/INCUBATOR-265 > Project: Incubator > Issue Type: Improvement > Components: guides >Reporter: Yonglun Zhang >Priority: Major > > The second section of > [http://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project] > > Graduation *as a project* requires the formation of the new project by the > [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board]. > > I think change *as a project* to *as a top level project* makes sense. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Liminal (incubating) 0.0.2rc1-INCUBATING
Sorry to resurrect an old vote thread, but to follow up on this: In Airflow 2.1 we have removed _our_ cat-X core dep, but that doesn't help the Liminal project as they need the Docker and Kubernetes client libraries for their core. I have opened https://github.com/psf/requests/pull/5797 and Jarek has done a lot of the testing work, and it looks likely that the "requests" maintainers will accept this PR. And the other LGPL dep from the python Kubernetes client is in the process of changing to Apache2 license https://github.com/websocket-client/websocket-client/issues/665 On 2021/04/21 14:55:14, Ash Berlin-Taylor wrote: > Hi Aviem, > > Hi everyone, Airflow PMC here. > > First off, eek. Not sure how this happened, it's been like this for a while. > > I agree -- we could possibly fix the direct dependency on requests/chardet in > Airflow, but as you have already discovered there are many more python > libraries that depend upon requests - docker and kubernetes being the two > that are hard to work around!. > > (Kubernetes has a _direct_ dep on a lgpl'd dep too) > > I'm writing a post to le...@apache.org, as _my_ reading is that depending > upon LGPLd library at runtime only, but not shipping it is "work that uses > the Library", and as per clause 5 of the LGPL 2.1 license should be fine > https://opensource.org/licenses/LGPL-2.1 > > > A program that contains no derivative of any portion of the Library, but is > > designed to work with the Library by being compiled or linked with it, is > > called a "work that uses the Library". Such a work, in isolation, is not a > > derivative work of the Library, and therefore falls outside the scope of > > this License. > > (There are a few caveats to this, so be careful about what else you might do > with the code, such as creating) > > We'll see what Legal say about this. > > Thanks, > Ash > > On 2021/04/21 10:39:58, Aviem Zur wrote: > > We can try to reach out. It looks like `chardet` can't change their license > > and `requests` have a won't fix / no time to fix attitude towards it. > > > > Meanwhile what do we do regarding releases of our artifacts? > > I don't see how we can develop a python project without having an indirect > > dependency on `requests` package as detailed above. > > > > On Wed, Apr 21, 2021 at 12:51 PM Justin Mclean > > wrote: > > > > > Hi, > > > > > > Sorry I’m not sure what to suggest. Normally I’d say contact the project > > > and ask if they would be willing to distribute the library under another > > > license e.g. dual license it under LGPL and ALv2 but this seem unlikely > > > [1]. I guess it wouldn't hurt to ask again. > > > > > > Kind Regards, > > > Justin > > > > > > > > > 1. https://github.com/chardet/chardet/issues/36 > > > - > > > 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
[jira] [Commented] (INCUBATOR-265) Maybe typo in Graduation Guide
[ https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17346151#comment-17346151 ] Yonglun Zhang commented on INCUBATOR-265: - Hi Sheng, Thanks for your comments. The full text of the second section is: "Graduation as a subproject is only possible if the subproject still falls within the scope of the project and requires the consent of the project [PMC|http://www.apache.org/foundation/how-it-works.html#structure]. Graduation as a project requires the formation of the new project by the [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board].; I think the first sentence refer to graduate to a subproject, while the latter refer to graduate to a top level project. > Maybe typo in Graduation Guide > -- > > Key: INCUBATOR-265 > URL: https://issues.apache.org/jira/browse/INCUBATOR-265 > Project: Incubator > Issue Type: Improvement > Components: guides >Reporter: Yonglun Zhang >Priority: Major > > The second section of > [http://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project] > > Graduation *as a project* requires the formation of the new project by the > [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board]. > > I think change *as a project* to *as a top level project* makes sense. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-265) Maybe typo in Graduation Guide
[ https://issues.apache.org/jira/browse/INCUBATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17346145#comment-17346145 ] Sheng Wu commented on INCUBATOR-265: `As a project` is an accurate sentence I think. The incubating product could graduate not as a TLP, but as a sub project of existing TLP. > Maybe typo in Graduation Guide > -- > > Key: INCUBATOR-265 > URL: https://issues.apache.org/jira/browse/INCUBATOR-265 > Project: Incubator > Issue Type: Improvement > Components: guides >Reporter: Yonglun Zhang >Priority: Major > > The second section of > [http://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project] > > Graduation *as a project* requires the formation of the new project by the > [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board]. > > I think change *as a project* to *as a top level project* makes sense. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-265) Maybe typo in Graduation Guide
Yonglun Zhang created INCUBATOR-265: --- Summary: Maybe typo in Graduation Guide Key: INCUBATOR-265 URL: https://issues.apache.org/jira/browse/INCUBATOR-265 Project: Incubator Issue Type: Improvement Components: guides Reporter: Yonglun Zhang The second section of [http://incubator.apache.org/guides/graduation.html#whether_to_graduate_to_subproject_or_to_top_level_project] Graduation *as a project* requires the formation of the new project by the [Board|http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#board]. I think change *as a project* to *as a top level project* makes sense. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
