[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=16807414#comment-16807414
 ] 

Dave Fisher commented on INCUBATOR-231:
---

I've split up the process as so and plan to put it into production tomorrow.
 # build_clutch.sh will do the svn repository old style page build and the 
clutch analysis. It then copies these into the git trunk.
 # build_site.sh does a simple bake and then does the git pull, replace content 
and push on the ash-site branch.

> 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=16807412#comment-16807412
 ] 

Dave Fisher commented on INCUBATOR-234:
---

In general I like the idea. Some thoughts:
 * We should rearrange the menus and change the templates to the old pages 
first until we tease out all of the cross-links.
 * We need to find a clear space for ip-clearance, projects, clutch (or do we 
move these all to whimsy?)
 * Maybe we should parallel the cookbook with an IPMC member cookbook.
 ** Mentor
 ** Champion
 ** Shepherd
 ** Chair
 ** Resources
 ** Improvement Plans

> 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/ ,  
> |http://incubator.apache.org/cookbook/]source 
> [https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad]
> 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]
> h2. How to contribute to this effort
>  * Feedback and suggestions are welcome here.
>  * Pull requests at [https://github.com/apache/incubator] also work
>  * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
> list, [https://lists.apache.org/list.html?general@incubator.apache.org]



--
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: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Ross Gardler]

Sure, policy is "Release votes SHOULD remain open for at least 72 hours."

The reasons for the SHOULD have been outlined already and should be well known 
to anyone who is in a podling since it's core to everything we do. I would have 
hoped champions would have explained this before even making the proposal. Not 
that it does any harm to repeat it.

Same goes for properly documenting what your +1 means. In the ASF +1 does not 
mean YES it means yes AND I have done what is necessary (in the case of 
indicating appropriate due diligence) or yes AND I will help make it happen (in 
the case of approving an action plan). Again, no harm in repeating this often.

It might be useful to give an example of where there is no need for a release 
vote to go 72 hours. A well run project will seek to have their code in a 
releasable state at all times. That means reviewing for IP, test coverage, 
backward compatibility breaks etc. on every commit. In the case of a minor 
point release or a bug fix release such projects MAY choose to release when 3 
+1s are received. After all, if an issue is discovered on the 73rd hour a fix 
can be committed and a new release voted started immediately without creating 
additional work for anyone.

Ross


From: Justin Mclean 
Sent: Monday, April 1, 2019 3:42 PM
To: general@incubator.apache.org
Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking 
IPMC to vote

Hi,

When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
> intending to rewrite foundation policy.
>

Sure I thought so as well, but other newer people here might not of been
aware of it.

Thanks,
Justin

>

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

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Adrian Cole]

TL;DR; I suppose is that in the case of 3 mentor/IPMC already +1 a release
we can switch to a "review after commit" style notification so that folks
eager to double check can, but not to burden the project or IPMC with a
secondary step.

This not only reduces bookkeeping but encourages each podling to engage
mentors, helping with the original intent of this thread.

Anything noted as blocker review after commit would be addressed.

In the rare case that IPMC members acting in a podling are doing a bad job,
that could be addressed as a learning exercise as presumably they would
also be doing a bad job at the later vote too.

On Tue, Apr 2, 2019, 9:42 AM Adrian Cole  wrote:

> one part that may not be obvious is the bookkeeping overhead on projects
> with many repositories and also the load on the IPMC.
>
> For example in zipkin, we are migrating several repositories. You can
> imagine a surge of release verification votes which if people here want to
> take the burden of responding to, surely can. Noting that there are already
> several IPMC involved it might for some members feel less priority and they
> may choose to not vote at all (such as our last release).
>
> Probably secondary to folks here is the burden on the podling to track the
> incomplete releases. It is less about rush more about excess tracking. It
> is possible that a project can achieve a "good driver status" to reduce the
> burden of having to create a wait condition especially if it is not the
> case people do anything during it.
>
> my 2p
>
> On Tue, Apr 2, 2019, 5:59 AM Dave Fisher  wrote:
>
>>
>>
>> > On Apr 1, 2019, at 3:42 PM, Justin Mclean 
>> wrote:
>> >
>> > Hi,
>> >
>> > When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
>> >> intending to rewrite foundation policy.
>> >>
>> >
>> > Sure I thought so as well, but other newer people here might not of been
>> > aware of it.
>>
>> The only exception to the 72 hour rule that I’ve heard about is a
>> critical security fix needs to be made in which case I would hope the
>> reason for the hurry would be explained on private lists.
>>
>> I would not put words into Ross’s mouth. He may in fact mean that he
>> would go quickly when there are three +1 votes and reasons other than
>> security.
>>
>> Regards,
>> Dave
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Adrian Cole]

one part that may not be obvious is the bookkeeping overhead on projects
with many repositories and also the load on the IPMC.

For example in zipkin, we are migrating several repositories. You can
imagine a surge of release verification votes which if people here want to
take the burden of responding to, surely can. Noting that there are already
several IPMC involved it might for some members feel less priority and they
may choose to not vote at all (such as our last release).

Probably secondary to folks here is the burden on the podling to track the
incomplete releases. It is less about rush more about excess tracking. It
is possible that a project can achieve a "good driver status" to reduce the
burden of having to create a wait condition especially if it is not the
case people do anything during it.

my 2p

On Tue, Apr 2, 2019, 5:59 AM Dave Fisher  wrote:

>
>
> > On Apr 1, 2019, at 3:42 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> > When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
> >> intending to rewrite foundation policy.
> >>
> >
> > Sure I thought so as well, but other newer people here might not of been
> > aware of it.
>
> The only exception to the 72 hour rule that I’ve heard about is a critical
> security fix needs to be made in which case I would hope the reason for the
> hurry would be explained on private lists.
>
> I would not put words into Ross’s mouth. He may in fact mean that he would
> go quickly when there are three +1 votes and reasons other than security.
>
> Regards,
> Dave
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Incubator (git) website published

[Dave Fisher]

All good now. New error state to add to the build - SVN connection reset.

Anyway - I am splitting out the clutch analysis from normal builds tomorrow 
after I add that new protection.

Regards,
Dave

> On Apr 1, 2019, at 7:05 PM, Dave Fisher  wrote:
> 
> The site is messed up. Checking.
> 
> Sent from my iPhone
> 
>> On Apr 1, 2019, at 6:39 PM, Apache Jenkins Server 
>>  wrote:
>> 
>> The Apache Jenkins build system has built Incubator Site (build #887)
>> 
>> Status: Successful
>> 
>> Check console output at https://builds.apache.org/job/Incubator%20Site/887/ 
>> to view the results.
>> 
>> 
>> -
>> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: cvs-h...@incubator.apache.org
> 
> 
> -
> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> For additional commands, e-mail: cvs-h...@incubator.apache.org
> 


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

Re: Incubator (git) website published

[Dave Fisher]

The site is messed up. Checking.

Sent from my iPhone

> On Apr 1, 2019, at 6:39 PM, Apache Jenkins Server  
> wrote:
> 
> The Apache Jenkins build system has built Incubator Site (build #887)
> 
> Status: Successful
> 
> Check console output at https://builds.apache.org/job/Incubator%20Site/887/ 
> to view the results.
> 
> 
> -
> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> For additional commands, e-mail: cvs-h...@incubator.apache.org


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

Re: List of Projects that went straight to Top Level Projects

[Sam Ruby]

On Mon, Apr 1, 2019 at 4:52 PM Dave Fisher  wrote:
>
> >
> > Pre-incubator:
> >  Ant,
> Jakarta
> > Avalon,
> Jakarta
> > DB,
> Jakarta

Thanks for the corrections!

> > HTTP Server, Jakarta, Perl, PHP, TCL, XML
> >
> > Spun out from elsewhere:
> >  Archiva,
> Maven ?

Generally this information can be found in the establish resolution,
in the paragraph that contains the word discharged.  This extraction
can often be automated, so I added this code.

Some older resolutions don't quite follow this pattern (and some PMCs
like Labs, etc aren't what we are looking for), so I hardcoded a
table:

https://github.com/apache/whimsy/commit/9667387e7467a98918dc3047ef32979462a92fc6

Updated results can be found here: https://whimsy.apache.org/incubator/graduated

Note: this site is live in the sense that it will continue to update
as new TLPs are created and projects are retired.  There may
occasionally be special cases to handle like the rename of Zest =>
Polygene.

- Sam Ruby

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

Re: Setting up Tuweni

[Kenneth Knowles]

Thanks Dave! And thanks for updating in SVN too.

Kenn

On Sun, Mar 31, 2019 at 9:58 AM Dave Fisher  wrote:

> Hi -
>
> > On Mar 30, 2019, at 11:41 PM, Kenneth Knowles  wrote:
> >
> > Hi Dave,
> >
> > What should a podling put here? I notice a few things:
> >
> > - you changed the start date from Feb 25 (date of the vote passing) to
> > March 25 (date of the commit)
>
> I put that in because it when we are actually starting.
>
> > - reporting group is left as 2
>
> This signifies the first month report - April reports are already setup
> and tuweni was not yet in the podlings.xml which drives that selection.
>
> > - the first monthly report is May, two months after the new incubation
> > start month
>
> The May report covers activity in April which is really the first month
> that activity and community can discuss.
>
> >
> > I don't know exactly how this corresponds to the instructions [1]. I am
> > asking because I just made the analogous commit for DataSketches and I
> > doubt I did it correctly. Can you help me?
>
> Like tuweni DataSketches will be in group 2 (not 3) and the months will be
> May, June, July.
>
> The main trouble with the instructions is that they just have 1|2|3 - 1 or
> 2 or 3. Recently, we had someone put in 1|2|3 which broke some things in
> Whimsy.
>
> If anyone thinks I am mistaken in this then please let me know.
>
> Justin - I’ll note that nearly half of all current podlings are in group 3
> which makes every 3rd month extra tedious for the Incubator.
>
> Regards,
> Dave
>
> >
> > Kenn
> >
> > [1]
> >
> http://incubator.apache.org/guides/mentor.html#add_to_incubation_summary_file
> >
> > On Tue, 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=1856351 <
> >> http://svn.apache.org/viewvc?view=revision=1856351>
>  [1]: https://issues.apache.org/jira/browse/INFRA-18110 <
> >> 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
>
>

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Dave Fisher]

> On Apr 1, 2019, at 3:42 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
>> intending to rewrite foundation policy.
>> 
> 
> Sure I thought so as well, but other newer people here might not of been
> aware of it.

The only exception to the 72 hour rule that I’ve heard about is a critical 
security fix needs to be made in which case I would hope the reason for the 
hurry would be explained on private lists.

I would not put words into Ross’s mouth. He may in fact mean that he would go 
quickly when there are three +1 votes and reasons other than security.

Regards,
Dave


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

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Justin Mclean]

Hi,

When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not
> intending to rewrite foundation policy.
>

Sure I thought so as well, but other newer people here might not of been
aware of it.

Thanks,
Justin

>

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Julian Hyde]

Per my reading http://www.apache.org/legal/release-policy.html#release-approval 
 it’s not OK 
to stop when you reach 3 +1 votes. Because it’s not 3 +1s absolute, it’s 3 more 
+1s than -1s. So, you have to have a fixed, reasonable timeframe for the vote 
to give those -1s time to accrue.

Release policy says the timeframe SHOULD be 72 hours. I can think of scenarios 
where it could be less, but you still have to give PMC members adequate notice.

When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not intending 
to rewrite foundation policy.

Also note in that same section:

>  Before casting +1 binding votes, individuals are REQUIRED to download
> all signed source code packages onto their own hardware, verify that they
> meet all requirements of ASF policy on releases as described below,
> validate all cryptographic signatures, compile as provided, and test the
> result on their own platform.

This clearly establishes the minimum required of mentors voting for a podling 
release.

Lastly, I absolutely agree with the question in the subject line. Yes, Mentors 
SHOULD vote on podling releases prior to asking IPMC to vote.

As mentors are busy, and are not 100% focused on the podling, the podling 
should give them a little nudge and a little leeway. Case in point: Druid 0.14 
started a vote at 4.08pm on Friday. It is now 3.08pm on Monday, i.e. we’re at 
71 hours. I voted but the other 2 mentors (whom I would describe as “engaged”) 
have not yet. I just emailed them to ask them to vote. If they do not vote in 
the next hour, the release manager should keep the vote open for a while to 
give them chance to vote.

Julian



> On Apr 1, 2019, at 2:59 PM, Justin Mclean  wrote:
> 
> Hi,
> 
>> 72 hours is a guide. As long as your project community is agreeable you can 
>> say "72hrs or 3 +1”.
> 
> 72 hours is a guide, but recommended, as it gives a chance for all PPMC 
> members to have a look at the release. They may be in different timezone or 
> have day jobs or other things going on, we are all volunteers here and not 
> all of us work full time on a project. If that 72 hours was constantly 
> reduced it would exclude certain groups of people looking at the release and 
> I don’t think we want to do that. For instance I don’t think it would be OK 
> if those 3 +1’s came in an hour of announcing the release candidate.
> 
> Thanks,
> Justin

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Justin Mclean]

Hi,

> 72 hours is a guide. As long as your project community is agreeable you can 
> say "72hrs or 3 +1”.

72 hours is a guide, but recommended, as it gives a chance for all PPMC members 
to have a look at the release. They may be in different timezone or have day 
jobs or other things going on, we are all volunteers here and not all of us 
work full time on a project. If that 72 hours was constantly reduced it would 
exclude certain groups of people looking at the release and I don’t think we 
want to do that. For instance I don’t think it would be OK if those 3 +1’s came 
in an hour of announcing the release candidate.

Thanks,
Justin

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Dave Fisher]

Hi -

> On Apr 1, 2019, at 2:51 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> I'd also like to see those mentors / IPMC members vote with more than just a 
> +1 and provide a list of what they checked. If they could use something like 
> this all the better [1].
> 
> I wouldn’t be for removing the second step of letting the IPMC look at it, 
> reasonably often serious issues are found in that step. By skilling that we 
> risk some podlings going all the way to propose graduation while having 
> releases that don’t follow ASF policy. This is a situation I’d like to avoid.

If the podling has three engaged Mentors that do VOTE and move the podling 
forward then I would suggest following Myrle’s plan and the podling releases 
and then sends a [REVIEW] or [DISCUSS].

I also suggest that the are the mentor’s helpful include an are your mentor’s 
voting?

I know from my own experience that knowing that there will be a round of voting 
on general@ makes it easy for me to not hurry to VOTE on dev@.

Regards,
Dave

> 
> Thanks,
> Justin
> 
> 1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
> -
> 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: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Justin Mclean]

Hi,

I'd also like to see those mentors / IPMC members vote with more than just a +1 
and provide a list of what they checked. If they could use something like this 
all the better [1].

I wouldn’t be for removing the second step of letting the IPMC look at it, 
reasonably often serious issues are found in that step. By skilling that we 
risk some podlings going all the way to propose graduation while having 
releases that don’t follow ASF policy. This is a situation I’d like to avoid.

Thanks,
Justin

1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: List of Projects that went straight to Top Level Projects

[Marcelo Vanzin]

On Mon, Apr 1, 2019 at 1:08 PM Lars Francke  wrote:
> > Straight to TLP:
> >   Bahir, DRAT, Kibble, Orc, Serf, STeVe, Whimsy, Zest
>
> ORC was spun out of Hive as far as I remember.

In that sense Bahir was also spun out of Spark, although it added a
lot of things after that.

-- 
Marcelo

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

Re: List of Projects that went straight to Top Level Projects

[Sharan Foga]

Hi Sam

Thanks for the rough cut list as it gives me more of the context so I can see 
where to select projects from for comparison. My thought is to do some analysis 
with Kibble as I did with my previous paper (summary version  is here 
https://s.apache.org/rguz and full version is here https://s.apache.org/y9Mv) 
and maybe follow it up with a survey or interview of the mentors or PMC members.

Will let people know when I have some details / results to share.

Thanks
Sharan 

On 2019/04/01 19:21:39, Sam Ruby  wrote: 
> On Mon, Apr 1, 2019 at 2:28 PM Greg Stein  wrote:
> >
> > On Mon, Apr 1, 2019 at 1:11 PM Julian Hyde  wrote:
> >
> > > Most of the projects mentioned so far have been “internal”
> >
> >
> > Only because all the umbrella-derived projects haven't been mentioned. Most
> > of that "spin out to a TLP" was done a decade ago, so they've been omitted
> > from discussion.
> >
> >
> > > - code developed to help run the ASF. “External” projects also go
> > > straight-to-TLP and are more important because they have many more users
> > > and greater impact on the world.
> > >
> >
> > I recall only two "external" projects have gone straight-to-TLP: Serf,
> > Zest/Polygene. I'm guessing Dave, et al, will surface others, if they
> > exist. I would disagree with your latter statement; they went to TLP based
> > on oversight, rather than on userbase/impact.
> >
> > I would suggest: the 90% of straight-to-TLP have been "internal" or
> > "spun-out".
> 
> My rough cut:
> 
> Straight to TLP:
>   Bahir, DRAT, Kibble, Orc, Serf, STeVe, Whimsy, Zest
> 
> Pre-incubator:
>   Ant, Avalon, Cocoon, DB, HTTP Server, Jakarta, Perl, PHP, TCL, XML
> 
> Spun out from elsewhere:
>   Archiva, Arrow, Avro, Axis, BookkeeperA, Camel, Continuum, Excalibur,
>   Forrest, Gump, Hadoop, HBase, HiveMind, HTTPComponents, JAMES, JMeter,
>   Karaf, Logging Services, Lucene, Mahout, Maven, Mina, POI, Quetzalcoatl,
>   Royale, Santuario, Shale, Struts, Tiles, Tomcat, Turbine, Velocity,
>   Web Services< Xalan, Xerces, XML Graphics, Yetus, Zookepper
> 
> Non-code PMC:
>   Attic, Community Development, Incubator, Labs, Public Relations
> 
> - Sam Ruby
> 
> -
> 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: [Cancelled] [VOTE] Heron Release 0.20.1-incubating (Release Candidate 2)

[Ning Wang]

Let's cancel this vote for now and go back to dev mailing list to discuss
more.

On Mon, Apr 1, 2019 at 1:53 PM Ning Wang  wrote:

> Ok. Thanks!
>
> On Mon, Apr 1, 2019 at 11:55 AM Dave Fisher  wrote:
>
>> -1 - we need to carefully discuss this on dev@heron.
>>
>> I seem to be the only Heron Mentor paying attention. We need more than me!
>>
>> (1) I cannot really follow this email
>> (2) We still need to discuss the docker hub image. (I suggest that this
>> be unofficial for this round.)
>> (3) The binaries on repository.apache.org 
>> are not on dist.apache.org .
>>
>> Apologies, let’s rewind what is included for this release. It needs to be
>> discussed on dev@ in advance.
>>
>> Regards,
>> Dave
>>
>> > On Apr 1, 2019, at 11:08 AM, Ning Wang  wrote:
>> >
>> > *Hello, dear IPMC members,This is a call for a vote to release Apache
>> Heron
>> > (Incubating) version 0.20.1.The Apache Heron Community has voted to make
>> > the Heron Release 0.20.1-incubating release. We kindly request the
>> > Incubator PMC members review and vote on this incubator release.The dev
>> > voting thread is
>> > here:
>> https://lists.apache.org/thread.html/7c61de9884bda8f95b798b40ce0bb90b7c768e05f1a90d45e164a7cf@%3Cdev.heron.apache.org%3E
>> > <
>> https://lists.apache.org/thread.html/7c61de9884bda8f95b798b40ce0bb90b7c768e05f1a90d45e164a7cf@%3Cdev.heron.apache.org%3E
>> >Apache
>> > Heron(incubating) is a realtime, distributed, fault-tolerant stream
>> > processing engine. This release include source code, maven artifacts.
>> > Convenience binary packages are also included but not relevant for
>> voting
>> > purposes.The tag to be voted upon:0.20.1-incubating-rc2
>> > (e6134da336fa290fa1b40972bc747a7507948d8a)The full list of changes and
>> > release notes are available
>> > at:
>> https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
>> > <
>> https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
>> >Source
>> > files can be found in dist.apache.org 
>> > site:
>> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.1-incubating-candidate-2/
>> > <
>> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.1-incubating-candidate-2/
>> >Docker
>> > image is available at:https://hub.docker.com/r/apacheheron/heron/tags
>> > The generated
>> packages,
>> > including maven artifacts, installers and docker image are available
>> here
>> > on GitHub:
>> > <
>> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.0-incubating-candidate-5/
>> >
>> https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
>> > <
>> https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
>> >Source
>> > SHA-512
>> >
>> checksums:c47fc8c228b5543f94dcf8fb5eb0f8083e84602be4f3b5ca52402b6e3e0f893434f971c317f44c3a69e78e597b96642fd69b5bec63e9a8eb7456c816f8e118f3
>> > incubator-heron-0.20.1-incubating-rc2.tar.gzArtifacts are published
>> > to:API:
>> >
>> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-api/0.20.1-incubating-rc2/
>> > <
>> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-api/0.20.1-incubating-rc2/
>> >SPI:
>> >
>> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-spi/0.20.1-incubating-rc2/
>> > <
>> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-spi/0.20.1-incubating-rc2/
>> >Storm
>> > API:
>> >
>> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-storm/0.20.1-incubating-rc2/
>> > <
>> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-storm/0.20.1-incubating-rc2/
>> >Simulator:
>> >
>> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-simulator/0.20.1-incubating-rc2/
>> > <
>> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-simulator/0.20.1-incubating-rc2/
>> >The
>> > artifacts are signed with PGP key 293DB72F865688D1, corresponding to
>> > nw...@apache.org , that can be found in keys
>> > file:https://dist.apache.org/repos/dist/release/incubator/heron/KEYS
>> > Please
>> > download the source package, and follow the compiling
>> > guide(
>> https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
>> > <
>> https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
>> >)to
>> > build and run the Heron locally. Note that currently Bazel 0.14.1 is
>> > required to build this version.The vote will be open for at least 72
>> hours
>> > or until the necessary number of votes are reached.Please vote
>> > accordingly:[ ] +1 approve[ ] +0 no opinion[ ] -1 disapprove with the
>> > reasonThanks,The Apache Heron (Incubating) Team*
>>
>>

Re: [VOTE] Heron Release 0.20.1-incubating (Release Candidate 2)

[Ning Wang]

Ok. Thanks!

On Mon, Apr 1, 2019 at 11:55 AM Dave Fisher  wrote:

> -1 - we need to carefully discuss this on dev@heron.
>
> I seem to be the only Heron Mentor paying attention. We need more than me!
>
> (1) I cannot really follow this email
> (2) We still need to discuss the docker hub image. (I suggest that this be
> unofficial for this round.)
> (3) The binaries on repository.apache.org 
> are not on dist.apache.org .
>
> Apologies, let’s rewind what is included for this release. It needs to be
> discussed on dev@ in advance.
>
> Regards,
> Dave
>
> > On Apr 1, 2019, at 11:08 AM, Ning Wang  wrote:
> >
> > *Hello, dear IPMC members,This is a call for a vote to release Apache
> Heron
> > (Incubating) version 0.20.1.The Apache Heron Community has voted to make
> > the Heron Release 0.20.1-incubating release. We kindly request the
> > Incubator PMC members review and vote on this incubator release.The dev
> > voting thread is
> > here:
> https://lists.apache.org/thread.html/7c61de9884bda8f95b798b40ce0bb90b7c768e05f1a90d45e164a7cf@%3Cdev.heron.apache.org%3E
> > <
> https://lists.apache.org/thread.html/7c61de9884bda8f95b798b40ce0bb90b7c768e05f1a90d45e164a7cf@%3Cdev.heron.apache.org%3E
> >Apache
> > Heron(incubating) is a realtime, distributed, fault-tolerant stream
> > processing engine. This release include source code, maven artifacts.
> > Convenience binary packages are also included but not relevant for voting
> > purposes.The tag to be voted upon:0.20.1-incubating-rc2
> > (e6134da336fa290fa1b40972bc747a7507948d8a)The full list of changes and
> > release notes are available
> > at:
> https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
> > <
> https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
> >Source
> > files can be found in dist.apache.org 
> > site:
> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.1-incubating-candidate-2/
> > <
> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.1-incubating-candidate-2/
> >Docker
> > image is available at:https://hub.docker.com/r/apacheheron/heron/tags
> > The generated packages,
> > including maven artifacts, installers and docker image are available here
> > on GitHub:
> > <
> https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.0-incubating-candidate-5/
> >
> https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
> > <
> https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
> >Source
> > SHA-512
> >
> checksums:c47fc8c228b5543f94dcf8fb5eb0f8083e84602be4f3b5ca52402b6e3e0f893434f971c317f44c3a69e78e597b96642fd69b5bec63e9a8eb7456c816f8e118f3
> > incubator-heron-0.20.1-incubating-rc2.tar.gzArtifacts are published
> > to:API:
> >
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-api/0.20.1-incubating-rc2/
> > <
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-api/0.20.1-incubating-rc2/
> >SPI:
> >
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-spi/0.20.1-incubating-rc2/
> > <
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-spi/0.20.1-incubating-rc2/
> >Storm
> > API:
> >
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-storm/0.20.1-incubating-rc2/
> > <
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-storm/0.20.1-incubating-rc2/
> >Simulator:
> >
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-simulator/0.20.1-incubating-rc2/
> > <
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-simulator/0.20.1-incubating-rc2/
> >The
> > artifacts are signed with PGP key 293DB72F865688D1, corresponding to
> > nw...@apache.org , that can be found in keys
> > file:https://dist.apache.org/repos/dist/release/incubator/heron/KEYS
> > Please
> > download the source package, and follow the compiling
> > guide(
> https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
> > <
> https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
> >)to
> > build and run the Heron locally. Note that currently Bazel 0.14.1 is
> > required to build this version.The vote will be open for at least 72
> hours
> > or until the necessary number of votes are reached.Please vote
> > accordingly:[ ] +1 approve[ ] +0 no opinion[ ] -1 disapprove with the
> > reasonThanks,The Apache Heron (Incubating) Team*
>
>

Re: List of Projects that went straight to Top Level Projects

[Dave Fisher]

Hi -

I took Greg’s challenge and did research on the roots. Mailing List Archives 
are important resources!

> On Apr 1, 2019, at 12:21 PM, Sam Ruby  wrote:
> 
> On Mon, Apr 1, 2019 at 2:28 PM Greg Stein  wrote:
>> 
>> On Mon, Apr 1, 2019 at 1:11 PM Julian Hyde  wrote:
>> 
>>> Most of the projects mentioned so far have been “internal”
>> 
>> 
>> Only because all the umbrella-derived projects haven't been mentioned. Most
>> of that "spin out to a TLP" was done a decade ago, so they've been omitted
>> from discussion.
>> 
>> 
>>> - code developed to help run the ASF. “External” projects also go
>>> straight-to-TLP and are more important because they have many more users
>>> and greater impact on the world.
>>> 
>> 
>> I recall only two "external" projects have gone straight-to-TLP: Serf,
>> Zest/Polygene. I'm guessing Dave, et al, will surface others, if they
>> exist. I would disagree with your latter statement; they went to TLP based
>> on oversight, rather than on userbase/impact.
>> 
>> I would suggest: the 90% of straight-to-TLP have been "internal" or
>> "spun-out".
> 
> My rough cut:
> 
> Straight to TLP:
>  Bahir, DRAT, Kibble, Orc, Serf, STeVe, Whimsy, Zest
> 
> Pre-incubator:
>  Ant,
Jakarta
> Avalon,
Jakarta
> DB,
Jakarta
> HTTP Server, Jakarta, Perl, PHP, TCL, XML
> 
> Spun out from elsewhere:
>  Archiva,
Maven ?
> Arrow,
Drill
> Avro,
Hadoop
> Axis,
Web Services
> Bookkeeper,
Zookeeper
> Camel,
? XML ?
> Commons
Jakarta
> Continuum,
Maven
> Excalibur,
Jakarta
>  Forrest,
XML
> Gump,
Jakarta
> Hadoop,
Nutch
> HBase,
Hadoop
> HiveMind,
Jakarta
> HTTPComponents,
Jakarta
> JAMES,
Jakarta
> JMeter,
Jakarta
> Karaf,
Felix
> Logging Services,
Jakarta
> Lucene,
Jakarta
> Mahout,
Lucene
> Maven,
Jakarta
> Mina,
Directory
> POI,
Jakarta
> Quetzalcoatl,
Mod_python - see mod python.org 
>  Royale,
Flex
> Santuario,
Rename of XML-Security
> Shale,
Struts
> Struts,
Jakarta
> Tiles,
Struts?
> Tomcat,
Jakarta
> Turbine,
Jakarta
> Velocity,
Jakarta
>  Web Services
Looks like it was built as an Uber project out of some of XML in Jan 2002.
> Xalan,
XML out of breakup
> Xerces,
November 1999
> XML Graphics,
XML out of breakup 
> Yetus,
Hadoop
> Zookepper
Hadoop

Regards,
Dave

> 
> Non-code PMC:
>  Attic, Community Development, Incubator, Labs, Public Relations
> 
> - Sam Ruby
> 
> -
> 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: List of Projects that went straight to Top Level Projects

[Sharan Foga]

Wow - thanks everyone for  the feedback. And Sam this is great.

Thanks
Sharan

On 2019/04/01 00:08:47, Sam Ruby  wrote: 
> In March, I wrote a script to find establishment resolutions, and to
> scan those resolutions for the word 'incubator':
> 
> https://whimsy.apache.org/incubator/graduated#summary
> 
> As always, the data is a bit dirty.  There are a number of projects
> that were created before we had establish resolutions, and some
> projects like comdev -- while technically "bypassing" the incubator --
> are not the types of projects you are looking for.
> 
> - Sam Ruby
> 
> On Sun, Mar 31, 2019 at 7:28 AM Sharan Foga  wrote:
> >
> > Hi All
> >
> > Does anyone know if there is a list of projects that bypassed incubation? 
> > For example - I know a couple of projects Royale and Kibble that went 
> > straight to TLP. Is there a list anywhere for all projects like this?
> >
> > Thanks
> > Sharan
> >
> > -
> > 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

Re: List of Projects that went straight to Top Level Projects

[Julian Hyde]

> On Apr 1, 2019, at 11:19 AM, Greg Stein  wrote:
> 
> I would disagree with your latter statement; they went to TLP based
> on oversight, rather than on userbase/impact.

I didn’t mean to suggest that we treated them differently because they had a 
large user base.

By “important” I meant “worthy of discussion in this thread”.

Julian


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

Re: List of Projects that went straight to Top Level Projects

[Lars Francke]

>
>
> Straight to TLP:
>   Bahir, DRAT, Kibble, Orc, Serf, STeVe, Whimsy, Zest
>

ORC was spun out of Hive as far as I remember.

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

[Craig Russell]

I understand the frustration here.

I'd suggest that with a large project like this [1], that has had many cases 
where the release would appear to be in violation of standards, that the 
[DISCUSS] and [VOTE] threads explicitly call out the issues, the RAT 
exclusions, and a small discussion of what "anomalies" have already been 
discussed and resolved. 

And it would be worthwhile for the Mentors to explicitly discuss in their vote 
responses that there are many issues/solutions in the release that have already 
been resolved.

Regards,

Craig

[1] the biggest one ever!

> On Apr 1, 2019, at 3:15 AM, Geertjan Wielenga 
>  wrote:
> 
> OK, that’s fair. And possibly an indicator that when a podling is large,
> and there are many moving parts, it would be best to, when needed, assume
> the podling is doing the best they can under complex circumstances, rather
> than that the podling is not following guidelines, ignoring advice, etc.
> 
> Gj
> 
> On Mon, 1 Apr 2019 at 12:09, Mark Struberg 
> wrote:
> 
>> One also has to see that NetBeans is an exceptionally big and complex
>> podling!
>> 
>> For most other projects the existing process works really fine.
>> 
>> LieGrue,
>> strub
>> 
>> 
>>> Am 01.04.2019 um 11:35 schrieb Geertjan Wielenga
>> :
>>> 
>>> On Mon, Apr 1, 2019 at 11:27 AM Mark Struberg >> 
>>> wrote:
>>> 
 We have also previously already checked those files and also have the
 sources at hand afaict.
 So they should be perfectly fine - as they have been in older NB
>> releases
 (where we had the question as well).
 
>>> 
>>> 
>>> I think this is the biggest problem with the incubator -- the fact that
>> one
>>> constantly needs to re-litigate decisions and agreements that have
>> already
>>> been made in previous releases.
>>> 
>>> Pointing to a list of issues, or a Wiki where these items are listed, is
>>> clearly not a solution -- the fact that we have been making use of Apache
>>> Rat from the very beginning and that we have a Rat exclusions file was
>> also
>>> missed, a whole thread was started to bring our intransigence to the
>>> attention of the world was started, etc etc. So, I don't see a solution
>>> here and it is the IPMC vote that -- while being immensely valuable for
>>> being the most detailed -- that invariable causes the most confusion and
>>> wasting of time in re-litigating things.
>>> 
>>> So, though I'd like to bring a solution to this, I do not have one.
>>> 
>>> Gj
>>> 
>>> 
>>> 
>>> 
 
 LieGrue,
 strub
 
 
> Am 30.03.2019 um 07:23 schrieb Wade Chandler >> :
> 
> On Fri, Mar 29, 2019, 21:43 Justin Mclean 
 wrote:
> 
>> 
>> Theres are the binary inclusions that seem to contain compiled code,
>> an
>> ASF release should not include this:
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/com-example-testmodule-cluster.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-brokendepending.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending_on_new_one_engine.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-1.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-2.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-executable-permissions.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-fragment.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent-1-1.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent.nbm
>> B
>> 
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-refresh_providers_test.nbm
>> 
> 
> To be clear, this is test data; not binary dependencies. Note the names
 of
> those files. NetBeans has a module system, and those have nbm
>> extensions.
> These nbms are made to test very specific things that can be wrong in
> modules. This would be like having tests for C/C++ linkers and object
 files
> etc where you just want to validate the linking not rebuilding object
 files
> for tests; rebuilding those every test run adds build time for no gain.
> Make sense, and Ok?

Re: List of Projects that went straight to Top Level Projects

[Sam Ruby]

On Mon, Apr 1, 2019 at 2:28 PM Greg Stein  wrote:
>
> On Mon, Apr 1, 2019 at 1:11 PM Julian Hyde  wrote:
>
> > Most of the projects mentioned so far have been “internal”
>
>
> Only because all the umbrella-derived projects haven't been mentioned. Most
> of that "spin out to a TLP" was done a decade ago, so they've been omitted
> from discussion.
>
>
> > - code developed to help run the ASF. “External” projects also go
> > straight-to-TLP and are more important because they have many more users
> > and greater impact on the world.
> >
>
> I recall only two "external" projects have gone straight-to-TLP: Serf,
> Zest/Polygene. I'm guessing Dave, et al, will surface others, if they
> exist. I would disagree with your latter statement; they went to TLP based
> on oversight, rather than on userbase/impact.
>
> I would suggest: the 90% of straight-to-TLP have been "internal" or
> "spun-out".

My rough cut:

Straight to TLP:
  Bahir, DRAT, Kibble, Orc, Serf, STeVe, Whimsy, Zest

Pre-incubator:
  Ant, Avalon, Cocoon, DB, HTTP Server, Jakarta, Perl, PHP, TCL, XML

Spun out from elsewhere:
  Archiva, Arrow, Avro, Axis, BookkeeperA, Camel, Continuum, Excalibur,
  Forrest, Gump, Hadoop, HBase, HiveMind, HTTPComponents, JAMES, JMeter,
  Karaf, Logging Services, Lucene, Mahout, Maven, Mina, POI, Quetzalcoatl,
  Royale, Santuario, Shale, Struts, Tiles, Tomcat, Turbine, Velocity,
  Web Services< Xalan, Xerces, XML Graphics, Yetus, Zookepper

Non-code PMC:
  Attic, Community Development, Incubator, Labs, Public Relations

- Sam Ruby

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

Re: [VOTE] Heron Release 0.20.1-incubating (Release Candidate 2)

[Dave Fisher]

-1 - we need to carefully discuss this on dev@heron.

I seem to be the only Heron Mentor paying attention. We need more than me!

(1) I cannot really follow this email
(2) We still need to discuss the docker hub image. (I suggest that this be 
unofficial for this round.)
(3) The binaries on repository.apache.org  are 
not on dist.apache.org .

Apologies, let’s rewind what is included for this release. It needs to be 
discussed on dev@ in advance.

Regards,
Dave

> On Apr 1, 2019, at 11:08 AM, Ning Wang  wrote:
> 
> *Hello, dear IPMC members,This is a call for a vote to release Apache Heron
> (Incubating) version 0.20.1.The Apache Heron Community has voted to make
> the Heron Release 0.20.1-incubating release. We kindly request the
> Incubator PMC members review and vote on this incubator release.The dev
> voting thread is
> here:https://lists.apache.org/thread.html/7c61de9884bda8f95b798b40ce0bb90b7c768e05f1a90d45e164a7cf@%3Cdev.heron.apache.org%3E
> Apache
> Heron(incubating) is a realtime, distributed, fault-tolerant stream
> processing engine. This release include source code, maven artifacts.
> Convenience binary packages are also included but not relevant for voting
> purposes.The tag to be voted upon:0.20.1-incubating-rc2
> (e6134da336fa290fa1b40972bc747a7507948d8a)The full list of changes and
> release notes are available
> at:https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
> Source
> files can be found in dist.apache.org 
> site:https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.1-incubating-candidate-2/
> Docker
> image is available at:https://hub.docker.com/r/apacheheron/heron/tags
> The generated packages,
> including maven artifacts, installers and docker image are available here
> on GitHub:
> https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
> Source
> SHA-512
> checksums:c47fc8c228b5543f94dcf8fb5eb0f8083e84602be4f3b5ca52402b6e3e0f893434f971c317f44c3a69e78e597b96642fd69b5bec63e9a8eb7456c816f8e118f3
> incubator-heron-0.20.1-incubating-rc2.tar.gzArtifacts are published
> to:API:
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-api/0.20.1-incubating-rc2/
> SPI:
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-spi/0.20.1-incubating-rc2/
> Storm
> API:
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-storm/0.20.1-incubating-rc2/
> Simulator:
> https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-simulator/0.20.1-incubating-rc2/
> The
> artifacts are signed with PGP key 293DB72F865688D1, corresponding to
> nw...@apache.org , that can be found in keys
> file:https://dist.apache.org/repos/dist/release/incubator/heron/KEYS
> Please
> download the source package, and follow the compiling
> guide(https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
> )to
> build and run the Heron locally. Note that currently Bazel 0.14.1 is
> required to build this version.The vote will be open for at least 72 hours
> or until the necessary number of votes are reached.Please vote
> accordingly:[ ] +1 approve[ ] +0 no opinion[ ] -1 disapprove with the
> reasonThanks,The Apache Heron (Incubating) Team*

Re: List of Projects that went straight to Top Level Projects

[Greg Stein]

On Mon, Apr 1, 2019 at 1:11 PM Julian Hyde  wrote:

> Most of the projects mentioned so far have been “internal”


Only because all the umbrella-derived projects haven't been mentioned. Most
of that "spin out to a TLP" was done a decade ago, so they've been omitted
from discussion.


> - code developed to help run the ASF. “External” projects also go
> straight-to-TLP and are more important because they have many more users
> and greater impact on the world.
>

I recall only two "external" projects have gone straight-to-TLP: Serf,
Zest/Polygene. I'm guessing Dave, et al, will surface others, if they
exist. I would disagree with your latter statement; they went to TLP based
on oversight, rather than on userbase/impact.

I would suggest: the 90% of straight-to-TLP have been "internal" or
"spun-out".

Cheers,
-g

[VOTE] Heron Release 0.20.1-incubating (Release Candidate 2)

[Ning Wang]

*Hello, dear IPMC members,This is a call for a vote to release Apache Heron
(Incubating) version 0.20.1.The Apache Heron Community has voted to make
the Heron Release 0.20.1-incubating release. We kindly request the
Incubator PMC members review and vote on this incubator release.The dev
voting thread is
here:https://lists.apache.org/thread.html/7c61de9884bda8f95b798b40ce0bb90b7c768e05f1a90d45e164a7cf@%3Cdev.heron.apache.org%3E
Apache
Heron(incubating) is a realtime, distributed, fault-tolerant stream
processing engine. This release include source code, maven artifacts.
Convenience binary packages are also included but not relevant for voting
purposes.The tag to be voted upon:0.20.1-incubating-rc2
(e6134da336fa290fa1b40972bc747a7507948d8a)The full list of changes and
release notes are available
at:https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
Source
files can be found in dist.apache.org 
site:https://dist.apache.org/repos/dist/dev/incubator/heron/heron-0.20.1-incubating-candidate-2/
Docker
image is available at:https://hub.docker.com/r/apacheheron/heron/tags
The generated packages,
including maven artifacts, installers and docker image are available here
on GitHub:
https://github.com/apache/incubator-heron/releases/tag/0.20.1-incubating-rc2
Source
SHA-512
checksums:c47fc8c228b5543f94dcf8fb5eb0f8083e84602be4f3b5ca52402b6e3e0f893434f971c317f44c3a69e78e597b96642fd69b5bec63e9a8eb7456c816f8e118f3
 incubator-heron-0.20.1-incubating-rc2.tar.gzArtifacts are published
to:API:
https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-api/0.20.1-incubating-rc2/
SPI:
https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-spi/0.20.1-incubating-rc2/
Storm
API:
https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-storm/0.20.1-incubating-rc2/
Simulator:
https://repository.apache.org/content/repositories/staging/org/apache/heron/heron-simulator/0.20.1-incubating-rc2/
The
artifacts are signed with PGP key 293DB72F865688D1, corresponding to
nw...@apache.org , that can be found in keys
file:https://dist.apache.org/repos/dist/release/incubator/heron/KEYS
Please
download the source package, and follow the compiling
guide(https://apache.github.io/incubator-heron/docs/developers/compiling/compiling/
)to
build and run the Heron locally. Note that currently Bazel 0.14.1 is
required to build this version.The vote will be open for at least 72 hours
or until the necessary number of votes are reached.Please vote
accordingly:[ ] +1 approve[ ] +0 no opinion[ ] -1 disapprove with the
reasonThanks,The Apache Heron (Incubating) Team*

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

[Dave Fisher]

Hi -

> On Apr 1, 2019, at 10:54 AM, Marcelo Vanzin  
> wrote:
> 
> On Fri, Mar 29, 2019 at 10:41 PM Felix Cheung  wrote:
>> I switched to another environment, found out I needed to manually  pip
>> install configparser  just to build (skipTest)
> 
> There are probably things that could be better documented. Or maybe
> could be handled better by the build scripts. But these should be
> reported to the project (on jira), since it seems clear that those
> working on the project are not running into these problems or have
> long forgotten about it (after they fixed their local builds).

This is a very common situation with complex builds. Just try to build 
OpenOffice ;-)

> 
>> And then without skipTest it failed even earlier on rsc  tests
> 
> Yes there are a few known flaky tests.
> 
>> Quite a number of binary resources in the src release, ttf, svg etc
>> also this looks like standard bootstrap script, does it have to be in the
>> src release (vs to include in binary release)?
>> docs/assets/themes/apache/bootstrap/css/bootstrap.css
> 
> This is the way I've seen most ASF projects handling these kinds of
> artifacts. e.g. I see multiple copies of bootstrap in the Hadoop repo.
> Same in Spark.
> 
> And you can't get rid of all binaries in a source release... e.g.
> images and fonts. Fonts could come from 3rd party places and
> downloaded when building the sources, but is that worth the extra cost
> (everyone downloading this thing from the net all the time)? Is there
> any maven plugin or something like that for aiding with this sort of
> thing?
> 
> Images will in many cases be project-specific.
> 
> Not saying that the current state is optimal but you're not really
> providing an alternative here.

Images (png, jpg, .ico, etc.) and similar types of binary only resources have 
long been acceptable although I cannot find a resource about this at the moment 
as the legal affairs committee is reorganizing documentation.

BTW - SVG like CSS is textual language. Minified Javascript should not be in 
the source ….

Any included binaries should consider the license for inclusion just like 
included source code.

And NO compiled source although a testing jar can be rationalized.

And of course these can be documented in rat-excludes and other locations.

Questions should go to legal-discuss@a.o

Regards,
Dave

> 
> -- 
> Marcelo
> 
> -
> 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: List of Projects that went straight to Top Level Projects

[Julian Hyde]

Most of the projects mentioned so far have been “internal” - code developed to 
help run the ASF. “External” projects also go straight-to-TLP and are more 
important because they have many more users and greater impact on the world.

A couple of examples I am aware of have been “refactorings”, taking code and 
members from an existing project to form a new project:
* Arrow was created from Drill in this way;
* Hive was factored out of Hadoop;
* I don’t recall whether HCatalog was created as a podling, but it was later 
absorbed into Hive in what might be considered a reverse of the straight-to-TLP 
process. 

(Please forgive me / correct me if I get the details of these projects wrong. I 
was only directly involved with Arrow.)

I do think that these projects are worth learning from. Creating a new project 
and community by “re-potting” is a powerful pattern that projects should use 
when appropriate. 

Julian


> On Apr 1, 2019, at 4:11 AM, Bertrand Delacretaz  
> wrote:
> 
> Hi,
> 
> On Sun, Mar 31, 2019 at 1:58 PM Geertjan Wielenga
>  wrote:
>> ...I don’t
>> think it’s common to skip incubation and I’m sure a lot would not be
>> learned by skipping it
> 
> The rationale for the very few projects that have gone direct to TLP
> is that there was nothing to learn.
> 
> A good example is http://steve.apache.org/ : the code already existed
> somewhere on ASF servers, was managed informally by a number of
> long-term ASF Members.
> 
> Moving to a TLP clarifies things in this case, and incubation wouldn't
> have brought any advantages.
> 
> But it's really an exceptional process applied to a handful of
> projects so far out of about 200 PMCs nowadays.
> 
> -Bertrand
> 
> -
> 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

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

[Marcelo Vanzin]

Thanks for everybody who voted on the podling and general threads.

Vote passes with the following votes (* = binding):

- Justin Mclean (*)
- Luciano Resende (*)
- Felix Cheung (*)

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

-- 
Marcelo

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

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

[Marcelo Vanzin]

On Fri, Mar 29, 2019 at 10:41 PM Felix Cheung  wrote:
> I switched to another environment, found out I needed to manually  pip
> install configparser  just to build (skipTest)

There are probably things that could be better documented. Or maybe
could be handled better by the build scripts. But these should be
reported to the project (on jira), since it seems clear that those
working on the project are not running into these problems or have
long forgotten about it (after they fixed their local builds).

> And then without skipTest it failed even earlier on rsc  tests

Yes there are a few known flaky tests.

> Quite a number of binary resources in the src release, ttf, svg etc
> also this looks like standard bootstrap script, does it have to be in the
> src release (vs to include in binary release)?
> docs/assets/themes/apache/bootstrap/css/bootstrap.css

This is the way I've seen most ASF projects handling these kinds of
artifacts. e.g. I see multiple copies of bootstrap in the Hadoop repo.
Same in Spark.

And you can't get rid of all binaries in a source release... e.g.
images and fonts. Fonts could come from 3rd party places and
downloaded when building the sources, but is that worth the extra cost
(everyone downloading this thing from the net all the time)? Is there
any maven plugin or something like that for aiding with this sort of
thing?

Images will in many cases be project-specific.

Not saying that the current state is optimal but you're not really
providing an alternative here.

-- 
Marcelo

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

Re: [VOTE][RESULT] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)

[Dave Grove]

Thanks to all who participated in this vote.

It has passed with 4 +1 (binding) votes (Matt Sicker, Justin Mclean, Krzysztof 
Sobkowiak, Bertrand Delacretaz) and no other votes.

We will proceed with the 2.0.0 release of these three components.

Thanks also to Justin and Bertrand for pointing out a gap in our project's 
scancode tooling for checking releases.  It was inappropriately accepting the 
short-form Apache license header in non-minimized JavaScript source files.  
This was not intended; we will correct in the next release.

--dave

On 2019/03/26 12:48:32, "David P Grove"  wrote: 
> 
> 
> The Apache OpenWhisk Community has voted to make the first Apache release
> of the OpenWhisk "Package Alarm", "Package Cloudant" and "Package Kafka"
> components.
> 
> The OpenWhisk dev list voting thread is here:
> https://lists.apache.org/thread.html/e0fb73d8ca0d0c584650f4f5b8b02054f5c99d64895f3e5ace352234@%3Cdev.openwhisk.apache.org%3E
> 
> We request that IPMC Members please review and vote on this incubator
> release as described below.
> 
> These three Apache OpenWhisk packages provide basic event-based programming
> capabilities to an OpenWhisk deployment.
> 
> This release comprises of source code distribution only. There are three
> components (git repos) included in this release of the OpenWhisk Packages
> Group. All release artifacts were built by PR#251 in the openwhisk-release
> repo from the following Git commit IDs:
> * openwhisk-package-alarms: dd6ab4d81c8893436e7242170d57951c089d5185
> * openwhisk-package-cloudant: ce5dac9cb0204fb2f78195d9e3f9364236613a31
> * openwhisk-package-kafka: 49820dd24170f24a37c02fae6ba7ec06e190423f
> 
> openwhisk-package-alarms (C158D76 B5D9A53A AC10AC42 4CD5060C 7A6467D5
> E9624519 117E9C8C AB171590 CCC3505D 5C7E630D C41769B4 44F85F03 BBA40A6A
> E04D2264 79FFA78B B3C5BFB8)
>   src.tar.gz:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz
>   sha512 checksum:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz
> .sha512
>   signature:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz
> .asc
> 
> openwhisk-package-cloudant (380E1BA8 EC3C72A8 09B10DCF 03BC1D2D 4BFA7E4F
> 892995EE 39D26BBE 758AFD5D FA680E81 54A9C726 A0D386C5 B447C947 70D26385
> 2A8D07BF 5848318A 42A3BBDD)
>   src.tar.gz:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz
>   sha512 checksum:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz
> .sha512
>   signature:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz
> .asc
> 
> openwhisk-package-kafka (303B8286 AA9B945D 1A740FCB 0DE908D5 A287FAF5
> C20A9DF9 4BBD2F16 C488DF4B 3E82A75B 9D071B1A E1CCDB54 7B623A36 5AC88E5D
> 9994539B 00ECEA5D A066D156)
>   src.tar.gz:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz
>   sha512 checksum:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz
> .sha512
>   signature:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-2.0.0-incubating-rc2/openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz
> .asc
> 
> All release artifacts were signed with key 72AF0CC22C4CF320.
> KEYS file is available here:
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
> 
> How to verify the artifacts can be found at:
> https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the
> +release+checklist+and+vote+on+OpenWhisk+modules+under+Apache
> 
> Please vote on releasing version 2.0.0-incubating of Apache OpenWhisk
> Package Alarm, Package Cloudant, and Package Kafka as described above.
> 
> The vote will be open for at least 72 hours.
> [ ] +1 Release Apache OpenWhisk Package Alarm, Package Cloudant, and
> Package Kafka 2.0.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release and the reason
> 
> Checklist for reference:
> [ ] Download links are valid.
> [ ] Checksums and PGP signatures are valid.
> [ ] DISCLAIMER is included.
> [ ] Source code artifacts have correct names matching the current release.
> [ ] LICENSE and NOTICE files are correct for each OpenWhisk repository.
> [ ] All files have license headers if necessary.
> [ ] No compiled archives bundled in source archive.
> 
> regards,
> 
> --dave
> 

Re: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)

[James W Dubee]

Hey Dave,

I believe Jason Peterson did an emergency patch this weekend for the alarms 
provider. We should use hash 92b0ac8b0b006ef6c9395271fd17afa6c83c14b1 instead 
for alarms for the release. Other than that +1.

Regards,
James Dubee

-"David P Grove"  wrote: -
To: Incubator 
From: "David P Grove" 
Date: 03/26/2019 08:48AM
Cc: "OpenWhisk Dev" 
Subject: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and 
Package Kafka 2.0.0 (incubating)


The Apache OpenWhisk Community has voted to make the first Apache release
of the OpenWhisk "Package Alarm", "Package Cloudant" and "Package Kafka"
components.

The OpenWhisk dev list voting thread is here:
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.apache.org_thread.html_e0fb73d8ca0d0c584650f4f5b8b02054f5c99d64895f3e5ace352234-40-253Cdev.openwhisk.apache.org-253E=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=mNYL3iRkIHSpena7hJD92ihAR7Np-_j5HhizqqbvOHE=2ZZjkjbEj4oG91mtAZpXV1T5xhbbX2qmqjBpWAlxkns=SJ6lnxDzZZnMi5vWI5ielZN5vvAigmWHArnBjMllhfU=

We request that IPMC Members please review and vote on this incubator
release as described below.

These three Apache OpenWhisk packages provide basic event-based programming
capabilities to an OpenWhisk deployment.

This release comprises of source code distribution only. There are three
components (git repos) included in this release of the OpenWhisk Packages
Group. All release artifacts were built by PR#251 in the openwhisk-release
repo from the following Git commit IDs:
* openwhisk-package-alarms: dd6ab4d81c8893436e7242170d57951c089d5185
* openwhisk-package-cloudant: ce5dac9cb0204fb2f78195d9e3f9364236613a31
* openwhisk-package-kafka: 49820dd24170f24a37c02fae6ba7ec06e190423f

openwhisk-package-alarms (C158D76 B5D9A53A AC10AC42 4CD5060C 7A6467D5
E9624519 117E9C8C AB171590 CCC3505D 5C7E630D C41769B4 44F85F03 BBA40A6A
E04D2264 79FFA78B B3C5BFB8)
src.tar.gz:
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D2.0.0-2Dincubating-2Drc2_openwhisk-2Dpackage-2Dalarms-2D2.0.0-2Dincubating-2Dsources.tar.gz=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=mNYL3iRkIHSpena7hJD92ihAR7Np-_j5HhizqqbvOHE=2ZZjkjbEj4oG91mtAZpXV1T5xhbbX2qmqjBpWAlxkns=xPS9AntqtpNp2gGKMX9zNkYsENRPJBfdmwEyhdBBQpU=
sha512 checksum:
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D2.0.0-2Dincubating-2Drc2_openwhisk-2Dpackage-2Dalarms-2D2.0.0-2Dincubating-2Dsources.tar.gz=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=mNYL3iRkIHSpena7hJD92ihAR7Np-_j5HhizqqbvOHE=2ZZjkjbEj4oG91mtAZpXV1T5xhbbX2qmqjBpWAlxkns=xPS9AntqtpNp2gGKMX9zNkYsENRPJBfdmwEyhdBBQpU=
.sha512
signature:
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D2.0.0-2Dincubating-2Drc2_openwhisk-2Dpackage-2Dalarms-2D2.0.0-2Dincubating-2Dsources.tar.gz=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=mNYL3iRkIHSpena7hJD92ihAR7Np-_j5HhizqqbvOHE=2ZZjkjbEj4oG91mtAZpXV1T5xhbbX2qmqjBpWAlxkns=xPS9AntqtpNp2gGKMX9zNkYsENRPJBfdmwEyhdBBQpU=
.asc

openwhisk-package-cloudant (380E1BA8 EC3C72A8 09B10DCF 03BC1D2D 4BFA7E4F
892995EE 39D26BBE 758AFD5D FA680E81 54A9C726 A0D386C5 B447C947 70D26385
2A8D07BF 5848318A 42A3BBDD)
src.tar.gz:
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D2.0.0-2Dincubating-2Drc2_openwhisk-2Dpackage-2Dcloudant-2D2.0.0-2Dincubating-2Dsources.tar.gz=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=mNYL3iRkIHSpena7hJD92ihAR7Np-_j5HhizqqbvOHE=2ZZjkjbEj4oG91mtAZpXV1T5xhbbX2qmqjBpWAlxkns=5eVzmTXgRQksCDi1Bv-cU_weVwEpXtw3ixSb2vpt0iE=
sha512 checksum:
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D2.0.0-2Dincubating-2Drc2_openwhisk-2Dpackage-2Dcloudant-2D2.0.0-2Dincubating-2Dsources.tar.gz=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=mNYL3iRkIHSpena7hJD92ihAR7Np-_j5HhizqqbvOHE=2ZZjkjbEj4oG91mtAZpXV1T5xhbbX2qmqjBpWAlxkns=5eVzmTXgRQksCDi1Bv-cU_weVwEpXtw3ixSb2vpt0iE=
.sha512
signature:
https://urldefense.proofpoint.com/v2/url?u=https-3A__dist.apache.org_repos_dist_dev_incubator_openwhisk_apache-2Dopenwhisk-2D2.0.0-2Dincubating-2Drc2_openwhisk-2Dpackage-2Dcloudant-2D2.0.0-2Dincubating-2Dsources.tar.gz=DwIFAg=jf_iaSHvJObTbx-siA1ZOg=mNYL3iRkIHSpena7hJD92ihAR7Np-_j5HhizqqbvOHE=2ZZjkjbEj4oG91mtAZpXV1T5xhbbX2qmqjBpWAlxkns=5eVzmTXgRQksCDi1Bv-cU_weVwEpXtw3ixSb2vpt0iE=
.asc

openwhisk-package-kafka (303B8286 AA9B945D 1A740FCB 0DE908D5 A287FAF5
C20A9DF9 4BBD2F16 C488DF4B 3E82A75B 9D071B1A E1CCDB54 7B623A36 5AC88E5D
9994539B 00ECEA5D A066D156)
src.tar.gz:

Vote started on graduation of Apache PLC4X (incubating) pooling to TLP on d...@plc4x.apache.org

[Christofer Dutz]

Hi all,

I just wanted to inform you all, that on our dev-list we have just started a 
VOTE thread for proposing Apache PLC4X (incubating) for graduation to TLP.

Here’s a link to the vote thread:
https://lists.apache.org/thread.html/9a4cf5b1ad7b59e79ae33f3d09032e7942a7191a319335303e16d286@%3Cdev.plc4x.apache.org%3E

Thanks,
Chris

[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=16806744#comment-16806744
 ] 

Bertrand Delacretaz commented on INCUBATOR-234:
---

Once we're happy with the contents of the cookbook I think the following pages 
can be removed.

They have lots more detail but I don't thinks those are useful, except for a 
few exceptions which are noted.

* http://incubator.apache.org/policy/incubation.html
* http://incubator.apache.org/policy/process.html
* http://incubator.apache.org/policy/roles_and_responsibilities.html (except 
"mentors", simplified, under "guides")
* http://incubator.apache.org/podling-story.html
* http://incubator.apache.org/guides/proposal.html (I think the cookbook, a 
template + the existing examples will do)
* http://incubator.apache.org/guides/entry.html

The idea is that the Incubator website structure would be:

* The homepage with all the basic info (the "What are the steps to becoming an 
Apache Software Foundation Top-Level project?" that's now at 
http://incubator.apache.org/cookbook, pointers to mailing lists etc)
* The cookbook as the next step, to get the overview and lots of basic 
information, at least for the "happy case" of the vast majority of podlings.
* The guides (simplified and cleaned up) for more details
* Links to other ASF general info as we have now
* A cleaned-up FAQ

So the policies, proposals, PMC guides disappear (the latter replaced by links 
to general ASF info), leaning on existing ASF documentation instead and just 
outlining the differences with podlings as done at 
http://incubator.apache.org/cookbook/#podling_top_level_project_what_are_the_differences

For now these are just my ideas, I'm just thinking outloud here. Will bring 
this to our general@list for discussion once we feel good about 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/ ,  
> |http://incubator.apache.org/cookbook/]source 
> [https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad]
> 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]
> h2. How to contribute to this effort
>  * Feedback and suggestions are welcome here.
>  * Pull requests at [https://github.com/apache/incubator] also work
>  * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
> list, [https://lists.apache.org/list.html?general@incubator.apache.org]



--
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 OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)

[Bertrand Delacretaz]

Hi,

+1 for the releases of the 3 packages listed below.

Checked signatures, digests and build with "gradle distDocker".

As things to fix for next time, which do not block this release IMO, I
see several source files using a short-form Apache license header:

  // Licensed to the Apache Software Foundation (ASF) under one or
more contributor
 // license agreements; and to You under the Apache License, Version 2.0.

Was that discussed and found ok? Sorry if I forgot that discussion, a
link to it is a fine answer. I see Justin made a similar comment.

https://www.apache.org/legal/src-headers.html does mention such a
short form header but for "minified JavaScript" which is not the case
here.

And some minor comments:

-README should include or point to build instructions, I don't think
any of them do. Ok, those instructions are mostly trivial but that
that can just be a quick note or link to the appropriate build file to
avoid duplicating information. I assume it's just "gradle distDocker"
but it's good to know what's the recommended build command when
someone starts looking at these modules.

-The READMEs should also say "Apache OpenWhisk" more visibly than just
in the incubation disclaimer. Ideally in the README's title.

Packages:

SHA512(openwhisk-package-alarms-2.0.0-incubating-sources.tar.gz)=
d7e2925016674869c502fcf7ffdc087b80b84c5d4a555a1d0409d92eefb2f82fe36f821612c6a905f899c6d6ccba201086d5e58a6ed50d6e4571e0966ab3f9b0

SHA512(openwhisk-package-cloudant-2.0.0-incubating-sources.tar.gz)=
3f1e599c595a83fcf11a49ed5d7166d44efaba042f6e1588fa9b2054bbf3363ee02e1507a93c3f6b204c65ab2f7c94fd4393e4470ffc113dfef243d3739ab4d4

SHA512(openwhisk-package-kafka-2.0.0-incubating-sources.tar.gz)=
d1dc18a0dd7b4a648baffa1d1dde0647f6c9c0b032546dd11dc2728a5ff91a224695b01ecdeb3e5c5b9f4601817506479d67412ce875e4a1df21ee39d216d433

-Bertrand

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

Re: List of Projects that went straight to Top Level Projects

[Bertrand Delacretaz]

Hi,

On Sun, Mar 31, 2019 at 1:58 PM Geertjan Wielenga
 wrote:
> ...I don’t
> think it’s common to skip incubation and I’m sure a lot would not be
> learned by skipping it

The rationale for the very few projects that have gone direct to TLP
is that there was nothing to learn.

A good example is http://steve.apache.org/ : the code already existed
somewhere on ASF servers, was managed informally by a number of
long-term ASF Members.

Moving to a TLP clarifies things in this case, and incubation wouldn't
have brought any advantages.

But it's really an exceptional process applied to a handful of
projects so far out of about 200 PMCs nowadays.

-Bertrand

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

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

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz updated INCUBATOR-234:
--
Description: 
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/ ,  
|http://incubator.apache.org/cookbook/]source 
[https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad]

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]
h2. How to contribute to this effort
 * Feedback and suggestions are welcome here.
 * Pull requests at [https://github.com/apache/incubator] also work
 * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
list, [https://lists.apache.org/list.html?general@incubator.apache.org]

  was:
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/] 

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]
h2. How to contribute to this effort
 * Feedback and suggestions are welcome here.
 * Pull requests at [https://github.com/apache/incubator] also work
 * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
list, [https://lists.apache.org/list.html?general@incubator.apache.org]


> 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/ ,  
> |http://incubator.apache.org/cookbook/]source 
> [https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad]
> 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]
> h2. How to contribute to this effort
>  * Feedback and suggestions are welcome here.
>  * Pull requests at [https://github.com/apache/incubator] also work
>  * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
> list, [https://lists.apache.org/list.html?general@incubator.apache.org]



--
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] [Updated] (INCUBATOR-234) Incubator Cookbook

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz updated INCUBATOR-234:
--
Description: 
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]
h2. How to contribute to this effort
 * Feedback and suggestions are welcome here.
 * Pull requests at [https://github.com/apache/incubator] also work
 * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
list, https://lists.apache.org/list.html?general@incubator.apache.org

  was:
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


> 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]
> h2. How to contribute to this effort
>  * Feedback and suggestions are welcome here.
>  * Pull requests at [https://github.com/apache/incubator] also work
>  * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
> list, https://lists.apache.org/list.html?general@incubator.apache.org



--
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] [Updated] (INCUBATOR-234) Incubator Cookbook

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz updated INCUBATOR-234:
--
Description: 
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/] 

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]
h2. How to contribute to this effort
 * Feedback and suggestions are welcome here.
 * Pull requests at [https://github.com/apache/incubator] also work
 * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
list, [https://lists.apache.org/list.html?general@incubator.apache.org]

  was:
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]
h2. How to contribute to this effort
 * Feedback and suggestions are welcome here.
 * Pull requests at [https://github.com/apache/incubator] also work
 * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
list, https://lists.apache.org/list.html?general@incubator.apache.org


> 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/] 
> 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]
> h2. How to contribute to this effort
>  * Feedback and suggestions are welcome here.
>  * Pull requests at [https://github.com/apache/incubator] also work
>  * Discussions on the [general@incubator.a.o|mailto:general@incubator.a.o] 
> list, [https://lists.apache.org/list.html?general@incubator.apache.org]



--
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]

[Geertjan Wielenga]

OK, that’s fair. And possibly an indicator that when a podling is large,
and there are many moving parts, it would be best to, when needed, assume
the podling is doing the best they can under complex circumstances, rather
than that the podling is not following guidelines, ignoring advice, etc.

Gj

On Mon, 1 Apr 2019 at 12:09, Mark Struberg 
wrote:

> One also has to see that NetBeans is an exceptionally big and complex
> podling!
>
> For most other projects the existing process works really fine.
>
> LieGrue,
> strub
>
>
> > Am 01.04.2019 um 11:35 schrieb Geertjan Wielenga
> :
> >
> > On Mon, Apr 1, 2019 at 11:27 AM Mark Struberg  >
> > wrote:
> >
> >> We have also previously already checked those files and also have the
> >> sources at hand afaict.
> >> So they should be perfectly fine - as they have been in older NB
> releases
> >> (where we had the question as well).
> >>
> >
> >
> > I think this is the biggest problem with the incubator -- the fact that
> one
> > constantly needs to re-litigate decisions and agreements that have
> already
> > been made in previous releases.
> >
> > Pointing to a list of issues, or a Wiki where these items are listed, is
> > clearly not a solution -- the fact that we have been making use of Apache
> > Rat from the very beginning and that we have a Rat exclusions file was
> also
> > missed, a whole thread was started to bring our intransigence to the
> > attention of the world was started, etc etc. So, I don't see a solution
> > here and it is the IPMC vote that -- while being immensely valuable for
> > being the most detailed -- that invariable causes the most confusion and
> > wasting of time in re-litigating things.
> >
> > So, though I'd like to bring a solution to this, I do not have one.
> >
> > Gj
> >
> >
> >
> >
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>> Am 30.03.2019 um 07:23 schrieb Wade Chandler  >:
> >>>
> >>> On Fri, Mar 29, 2019, 21:43 Justin Mclean 
> >> wrote:
> >>>
> 
>  Theres are the binary inclusions that seem to contain compiled code,
> an
>  ASF release should not include this:
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/com-example-testmodule-cluster.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-brokendepending.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending_on_new_one_engine.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-1.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-2.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-executable-permissions.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-fragment.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent-1-1.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent.nbm
>  B
> 
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-refresh_providers_test.nbm
> 
> >>>
> >>> To be clear, this is test data; not binary dependencies. Note the names
> >> of
> >>> those files. NetBeans has a module system, and those have nbm
> extensions.
> >>> These nbms are made to test very specific things that can be wrong in
> >>> modules. This would be like having tests for C/C++ linkers and object
> >> files
> >>> etc where you just want to validate the linking not rebuilding object
> >> files
> >>> for tests; rebuilding those every test run adds build time for no gain.
> >>> Make sense, and Ok?
> >>>
> >>> Thanks
> >>>
> >>> Wade
> >>
> >>
> >> -
> >> 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-234) Incubator Cookbook

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on INCUBATOR-234:
---

[~isa...@apache.org] I have reworked the "does my project fit" section in 
[https://github.com/apache/incubator/commit/87f25f9,] WDYT?

> 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]

One also has to see that NetBeans is an exceptionally big and complex podling!

For most other projects the existing process works really fine.

LieGrue,
strub


> Am 01.04.2019 um 11:35 schrieb Geertjan Wielenga 
> :
> 
> On Mon, Apr 1, 2019 at 11:27 AM Mark Struberg 
> wrote:
> 
>> We have also previously already checked those files and also have the
>> sources at hand afaict.
>> So they should be perfectly fine - as they have been in older NB releases
>> (where we had the question as well).
>> 
> 
> 
> I think this is the biggest problem with the incubator -- the fact that one
> constantly needs to re-litigate decisions and agreements that have already
> been made in previous releases.
> 
> Pointing to a list of issues, or a Wiki where these items are listed, is
> clearly not a solution -- the fact that we have been making use of Apache
> Rat from the very beginning and that we have a Rat exclusions file was also
> missed, a whole thread was started to bring our intransigence to the
> attention of the world was started, etc etc. So, I don't see a solution
> here and it is the IPMC vote that -- while being immensely valuable for
> being the most detailed -- that invariable causes the most confusion and
> wasting of time in re-litigating things.
> 
> So, though I'd like to bring a solution to this, I do not have one.
> 
> Gj
> 
> 
> 
> 
>> 
>> LieGrue,
>> strub
>> 
>> 
>>> Am 30.03.2019 um 07:23 schrieb Wade Chandler :
>>> 
>>> On Fri, Mar 29, 2019, 21:43 Justin Mclean 
>> wrote:
>>> 
 
 Theres are the binary inclusions that seem to contain compiled code, an
 ASF release should not include this:
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/com-example-testmodule-cluster.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-brokendepending.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending_on_new_one_engine.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-1.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-2.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-executable-permissions.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-fragment.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent-1-1.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent.nbm
 B
 
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-refresh_providers_test.nbm
 
>>> 
>>> To be clear, this is test data; not binary dependencies. Note the names
>> of
>>> those files. NetBeans has a module system, and those have nbm extensions.
>>> These nbms are made to test very specific things that can be wrong in
>>> modules. This would be like having tests for C/C++ linkers and object
>> files
>>> etc where you just want to validate the linking not rebuilding object
>> files
>>> for tests; rebuilding those every test run adds build time for no gain.
>>> Make sense, and Ok?
>>> 
>>> Thanks
>>> 
>>> Wade
>> 
>> 
>> -
>> 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: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Ovilia]

Sorry. I've fixed that now.

Zhang Wenli
http://zhangwenli.com


sebb  于2019年4月1日周一 下午4:02写道：

> On Mon, 1 Apr 2019 at 07:58, Ovilia  wrote:
> >
> > Thanks Craig.
> >
> > I've updated the download page. Please help check again.
> > Thank you!
>
> The page says "please check the md5sum and ...".
> However MD5 checksums are deprecated and anyway the podling does not use
> them.
> The text and the link need to be fixed accordingly please.
>
> Also the KEYS link must be to
> https://www.apache.org/dist/incubator/echarts/KEYS
>
> The dist.apache.org server is only intended to be used by developers
> for staging releases.
>
> > Zhang Wenli
> > http://zhangwenli.com
> >
> >
> > Craig Russell  于2019年3月30日周六 下午1:06写道：
> >
> > > The page http://echarts.apache.org/download.html is very close, but:
> > >
> > > The Source link is fine.
> > > The Signature link and SHA512 link must be changed from
> > > https://dist.apache.org/repos/dist/release/incubator/echarts/... to
> > > https://www.apache.org/dist/incubator/echarts/...
> > >
> > > The instructions in step 2 refer to downloading from Apache but these
> > > links are http links and must be https links.
> > >
> > > Hope this helps,
> > >
> > > Craig
> > >
> > >
> > > > On Mar 29, 2019, at 9:46 PM, Ovilia  wrote:
> > > >
> > > > The download link is http://echarts.apache.org/download.html
> > > >
> > > > Zhang Wenli
> > > > http://zhangwenli.com
> > > >
> > > >
> > > > Ovilia  于2019年3月30日周六 下午12:45写道：
> > > >
> > > >> I've updated ECharts download page. Hopefully, it's been fixed
> correctly
> > > >> this time.
> > > >> If so, we will send an email to  annou...@apache.org for the
> release.
> > > >>
> > > >> Zhang Wenli
> > > >> http://zhangwenli.com
> > > >>
> > > >>
> > > >> Craig Russell  于2019年3月21日周四 上午8:23写道：
> > > >>
> > > >>> Hi Su Shuang,
> > > >>>
> > > >>> You will need to modify your download page to conform to
> requirements
> > > (an
> > > >>> announcement to incubator is not moderated but an announcement to
> > > >>> annou...@apache.org will be moderated, and this announcement will
> not
> > > >>> pass).
> > > >>>
> > > >>> You should never refer in the announcement or your download page to
> > > >>> dist.apache.org. For announcement emails, link to your download
> page.
> > > >>> For download pages, link to the mirror chooser and link to the
> > > checksum and
> > > >>> signature from www.apache.org/dist/incubator/echarts. Include a
> link
> > > to
> > > >>> your project KEYS file and instructions how to verify the download.
> > > >>>
> > > >>> There are many download pages you can model, e.g.
> > > >>> https://hadoop.apache.org/releases.html
> > > >>>
> > > >>> If you need help, your mentors will be able to assist.
> > > >>>
> > > >>> Best regards
> > > >>>
> > > >>> Craig
> > > >>>
> > >  On Mar 20, 2019, at 1:24 PM, SHUANG SU 
> > > wrote:
> > > 
> > >  Hi all,
> > > 
> > >  The Apache ECharts (incubating) team is proud to announce Apache
> > > ECharts
> > >  version 4.2.1-incubating.
> > > 
> > >  ECharts is a powerful, interactive charting and visualization
> library.
> > > 
> > >  Vote thread:
> > > 
> > > >>>
> > >
> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
> > > 
> > >  Download Links:
> > > 
> https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
> > > 
> > >  Release Notes:
> > > 
> http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
> > > 
> > >  Website: http://echarts.apache.org/
> > > 
> > >  ECharts Resources:
> > >  - Issue: https://github.com/apache/incubator-echarts/issues
> > >  - Mailing list: d...@echarts.incubator.apache.org
> > > 
> > >  Thanks
> > > 
> > >  --
> > >  Su Shuang (100pah)
> > >  --
> > > >>>
> > > >>> Craig L Russell
> > > >>> c...@apache.org
> > > >>>
> > > >>>
> > > >>>
> -
> > > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > >>> For additional commands, e-mail: general-h...@incubator.apache.org
> > > >>>
> > > >>>
> > >
> > > Craig L Russell
> > > Secretary, Apache Software Foundation
> > > c...@apache.org  http://db.apache.org/jdo <
> > > http://db.apache.org/jdo>
> > >
>
> -
> 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]

[Geertjan Wielenga]

On Mon, Apr 1, 2019 at 11:27 AM Mark Struberg 
wrote:

> We have also previously already checked those files and also have the
> sources at hand afaict.
> So they should be perfectly fine - as they have been in older NB releases
> (where we had the question as well).
>


I think this is the biggest problem with the incubator -- the fact that one
constantly needs to re-litigate decisions and agreements that have already
been made in previous releases.

Pointing to a list of issues, or a Wiki where these items are listed, is
clearly not a solution -- the fact that we have been making use of Apache
Rat from the very beginning and that we have a Rat exclusions file was also
missed, a whole thread was started to bring our intransigence to the
attention of the world was started, etc etc. So, I don't see a solution
here and it is the IPMC vote that -- while being immensely valuable for
being the most detailed -- that invariable causes the most confusion and
wasting of time in re-litigating things.

So, though I'd like to bring a solution to this, I do not have one.

Gj




>
> LieGrue,
> strub
>
>
> > Am 30.03.2019 um 07:23 schrieb Wade Chandler :
> >
> > On Fri, Mar 29, 2019, 21:43 Justin Mclean 
> wrote:
> >
> >>
> >> Theres are the binary inclusions that seem to contain compiled code, an
> >> ASF release should not include this:
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/com-example-testmodule-cluster.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-brokendepending.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending_on_new_one_engine.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-1.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-2.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-executable-permissions.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-fragment.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent-1-1.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent.nbm
> >>  B
> >>
> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-refresh_providers_test.nbm
> >>
> >
> > To be clear, this is test data; not binary dependencies. Note the names
> of
> > those files. NetBeans has a module system, and those have nbm extensions.
> > These nbms are made to test very specific things that can be wrong in
> > modules. This would be like having tests for C/C++ linkers and object
> files
> > etc where you just want to validate the linking not rebuilding object
> files
> > for tests; rebuilding those every test run adds build time for no gain.
> > Make sense, and Ok?
> >
> > Thanks
> >
> > Wade
>
>
> -
> 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]

Indeed, and thanks again for jumping in and pushing the review forward!
NB is such a huge codebase that it is really hard to do a full cycle review. 
So any attempt is really appreciated!

LieGrue,
strub


> Am 31.03.2019 um 10:04 schrieb Justin Mclean :
> 
> Hi,
> 
>> It has never been a practice or assumption in Apache NetBeans that all our
>> mentors vote on all our releases. We do explicitly ask our mentors to vote
>> in the podling dev list, normally at least one (in this case Ate) does,
>> while at least two of the other three tend to vote in the IPMC thread.
> 
> Your mentors know your project well and would have know some of the quicks in 
> that release, having them vote there  probably would have saved some 
> discussion. 
> 
> The incubator is trying to encourage mentor to vote on releases before they 
> come to up for an IPMC and hopefully by that time with will already have 3 +1 
> votes, but this is a recent thing.
> 
> 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 Netbeans 11.0 (incubating) [vote candidate 4]

[Mark Struberg]

I started my review on the IPMC list but did also test-drive NB11 for a few 
days because I had functional issues (quirks with missing JavaFX on Fedora). 
Thus I only casted my +1 only after the vote got moved to general@a.o.
Trying to move faster in the future.

txs and LieGrue,
strub

> Am 31.03.2019 um 09:35 schrieb Justin Mclean :
> 
> Hi,
> 
>>> I will again raise the question of why the mentors failed to vote on the
>>> release. I'd like to make it a stronger suggestion that Mentors SHOULD vote
>>> on releases prior to sending the release vote to the IPMC.
>>> 
>> 
>> For the record, we have 4 mentors, two of which have voted +1 on this
>> release so far.
> 
> One voted on the IPMC list (right?). I think Graig was asking why they didn’t 
> vote on the podling dev list.
> 
> 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 Netbeans 11.0 (incubating) [vote candidate 4]

[Mark Struberg]

We have also previously already checked those files and also have the sources 
at hand afaict.
So they should be perfectly fine - as they have been in older NB releases 
(where we had the question as well).

LieGrue,
strub


> Am 30.03.2019 um 07:23 schrieb Wade Chandler :
> 
> On Fri, Mar 29, 2019, 21:43 Justin Mclean  wrote:
> 
>> 
>> Theres are the binary inclusions that seem to contain compiled code, an
>> ASF release should not include this:
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/com-example-testmodule-cluster.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-brokendepending.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-depending_on_new_one_engine.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-1.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine-1-2.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-engine.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-executable-permissions.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-fragment.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent-1-1.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-independent.nbm
>>  B
>> ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/org-yourorghere-refresh_providers_test.nbm
>> 
> 
> To be clear, this is test data; not binary dependencies. Note the names of
> those files. NetBeans has a module system, and those have nbm extensions.
> These nbms are made to test very specific things that can be wrong in
> modules. This would be like having tests for C/C++ linkers and object files
> etc where you just want to validate the linking not rebuilding object files
> for tests; rebuilding those every test run adds build time for no gain.
> Make sense, and Ok?
> 
> Thanks
> 
> Wade


-
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=16806538#comment-16806538
 ] 

Bertrand Delacretaz commented on INCUBATOR-234:
---

In [https://github.com/apache/incubator/commit/20c6621] I have moved back to a 
single page for the cookbook, 
[https://github.com/apache/incubator/blob/master/pages/cookbook/index.ad]

This gives us a table of contents + section links for free.

bq. Release Distribution Policy is an important part to discuss within 
releases. 

The "Incubator Releases" section links to 
http://www.apache.org/legal/release-policy.html, do we need more than that?

bq. How should exceptions to the normal course be handled in the cookbook?

If we really really have to I'd say small notes at the end of each section? But 
in general I'd prefer the cookbook to describe the happy case, with details in 
the (simplified) http://incubator.apache.org/guides/ . So maybe the notes can 
just hints at possible differences and point to the guides for details?

> 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: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Bertrand Delacretaz]

Hi,

On Mon, Apr 1, 2019 at 5:30 AM Craig Russell  wrote:
>
> ...This is a proposal to recommend that all Mentors SHOULD vote on podling 
> releases
> prior to sending the release for a vote to the IPMC

There's already something about this in the (work in progress)
http://incubator.apache.org/cookbook/ under "podling releases":

> If three mentors have voted this means the "three +1 votes" requirement is 
> already fulfilled
> when that second vote starts, which can speed up things

If you think this can be improved, pull requests, comments here or at
https://issues.apache.org/jira/browse/INCUBATOR-234 are welcome.

-Bertrand

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

Re: Voting on releases with serious unaddressed issues

[Geertjan Wielenga]

On Mon, Apr 1, 2019 at 10:26 AM Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Sat, Mar 30, 2019 at 8:01 PM Geertjan Wielenga
>  wrote:
> >...what comes closest to what
> > you're looking for is the Rat exclusions file...
>
> >
> https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclusions.txt
> ...
>
> And note that that file is mentioned in the
> https://github.com/apache/incubator-netbeans README which says
> "NetBeans license violation checks are managed via the
> rat-exclusions.txt file" with a link.
>


Indeed, I didn't want to put too fine a point on it, but a lot of this
whole discussion could have been avoided simply by reading the initial
thread in the IPMC vote thread, where, for example, we explicitly provided
a link to our Ant Rat results file, which would have avoided the "NetBeans
should really consider to use Ant Rat" and "NetBeans really should explain
how it deviates from the norm" type of discussion -- because, again, we
provided all that info directly in the initial vote mail.

Gj




>
> I think although there's a lot of exclusions, NetBeans has done a
> great job in documenting them and gradually improve the situation on
> what's a huge codebase.
>
> -Bertrand (NetBeans incubation mentor)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Voting on releases with serious unaddressed issues

[Bertrand Delacretaz]

Hi,

On Sat, Mar 30, 2019 at 3:34 AM Justin Mclean  wrote:
> ...What do other IPMC members think?...

I'm coming late to this discussion but I think it would have been
better to point to specific issues so people can reply in a more
concrete way.

Generally, I think it can be ok for podling releases to be
"imperfect", provided tickets are created to manage what needs to
change.

Best might be to create a ticket at
https://issues.apache.org/jira/projects/INCUBATOR for each podling
release, from which sub-tasks or linked tickets can be created for
those things that need to be fixed later. This makes it easy to look
at the history of previous releases and verify that those things are
improved.

-Bertrand

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

Re: Voting on releases with serious unaddressed issues

[Bertrand Delacretaz]

Hi,

On Sat, Mar 30, 2019 at 8:01 PM Geertjan Wielenga
 wrote:
>...what comes closest to what
> you're looking for is the Rat exclusions file...

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

And note that that file is mentioned in the
https://github.com/apache/incubator-netbeans README which says
"NetBeans license violation checks are managed via the
rat-exclusions.txt file" with a link.

I think although there's a lot of exclusions, NetBeans has done a
great job in documenting them and gradually improve the situation on
what's a huge codebase.

-Bertrand (NetBeans incubation mentor)

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

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[sebb]

On Mon, 1 Apr 2019 at 07:58, Ovilia  wrote:
>
> Thanks Craig.
>
> I've updated the download page. Please help check again.
> Thank you!

The page says "please check the md5sum and ...".
However MD5 checksums are deprecated and anyway the podling does not use them.
The text and the link need to be fixed accordingly please.

Also the KEYS link must be to
https://www.apache.org/dist/incubator/echarts/KEYS

The dist.apache.org server is only intended to be used by developers
for staging releases.

> Zhang Wenli
> http://zhangwenli.com
>
>
> Craig Russell  于2019年3月30日周六 下午1:06写道：
>
> > The page http://echarts.apache.org/download.html is very close, but:
> >
> > The Source link is fine.
> > The Signature link and SHA512 link must be changed from
> > https://dist.apache.org/repos/dist/release/incubator/echarts/... to
> > https://www.apache.org/dist/incubator/echarts/...
> >
> > The instructions in step 2 refer to downloading from Apache but these
> > links are http links and must be https links.
> >
> > Hope this helps,
> >
> > Craig
> >
> >
> > > On Mar 29, 2019, at 9:46 PM, Ovilia  wrote:
> > >
> > > The download link is http://echarts.apache.org/download.html
> > >
> > > Zhang Wenli
> > > http://zhangwenli.com
> > >
> > >
> > > Ovilia  于2019年3月30日周六 下午12:45写道：
> > >
> > >> I've updated ECharts download page. Hopefully, it's been fixed correctly
> > >> this time.
> > >> If so, we will send an email to  annou...@apache.org for the release.
> > >>
> > >> Zhang Wenli
> > >> http://zhangwenli.com
> > >>
> > >>
> > >> Craig Russell  于2019年3月21日周四 上午8:23写道：
> > >>
> > >>> Hi Su Shuang,
> > >>>
> > >>> You will need to modify your download page to conform to requirements
> > (an
> > >>> announcement to incubator is not moderated but an announcement to
> > >>> annou...@apache.org will be moderated, and this announcement will not
> > >>> pass).
> > >>>
> > >>> You should never refer in the announcement or your download page to
> > >>> dist.apache.org. For announcement emails, link to your download page.
> > >>> For download pages, link to the mirror chooser and link to the
> > checksum and
> > >>> signature from www.apache.org/dist/incubator/echarts. Include a link
> > to
> > >>> your project KEYS file and instructions how to verify the download.
> > >>>
> > >>> There are many download pages you can model, e.g.
> > >>> https://hadoop.apache.org/releases.html
> > >>>
> > >>> If you need help, your mentors will be able to assist.
> > >>>
> > >>> Best regards
> > >>>
> > >>> Craig
> > >>>
> >  On Mar 20, 2019, at 1:24 PM, SHUANG SU 
> > wrote:
> > 
> >  Hi all,
> > 
> >  The Apache ECharts (incubating) team is proud to announce Apache
> > ECharts
> >  version 4.2.1-incubating.
> > 
> >  ECharts is a powerful, interactive charting and visualization library.
> > 
> >  Vote thread:
> > 
> > >>>
> > https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
> > 
> >  Download Links:
> >  https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
> > 
> >  Release Notes:
> >  http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
> > 
> >  Website: http://echarts.apache.org/
> > 
> >  ECharts Resources:
> >  - Issue: https://github.com/apache/incubator-echarts/issues
> >  - Mailing list: d...@echarts.incubator.apache.org
> > 
> >  Thanks
> > 
> >  --
> >  Su Shuang (100pah)
> >  --
> > >>>
> > >>> Craig L Russell
> > >>> c...@apache.org
> > >>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >>> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>>
> > >>>
> >
> > Craig L Russell
> > Secretary, Apache Software Foundation
> > c...@apache.org  http://db.apache.org/jdo <
> > http://db.apache.org/jdo>
> >

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

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[sebb]

On Mon, 1 Apr 2019 at 05:15, Ross Gardler  wrote:
>
> Just like so many things, this is how it used to be. In fact, back in the day 
> the only time the IPMC was asked to vote was when there were not enough 
> mentor votes.
>
> If you look at all the podlinga I've mentored I have only ever asked for an 
> IPMC vote on two occasions (that I recall). One because I had absent mentors 
> (the project never graduated due to lack of success as a community) and one 
> because it was a very large and complex code base and we asked for extra eyes 
> on the first release.
>
> Every other time the community worked with mentors. Once we had the votes we 
> notified the IPMC that the vote had passed and moved on.
>
> Requiring an IPMC vote is akin to the board voting on all TLP releases. It 
> should be stopped. The IPMC are facilitators not gate keepers.

I'm not sure that is a correct analogy.

IMO the Incubator is the PMC for all its podlings.

I think it's more akin to Commons where each component tends to be
worked on by a few developers, but the whole PMC participates in
votes.

> Individual IPMC members can join the podling communities if they wish to 
> participate. Why are podlings and mentors answering to the IPMC by default?
>
> I know the standard answer is because mentors sometimes get too busy. Sure. 
> If it happens every release is a problem and having to ask for an IPMC vote 
> highlights the problem.
>
> I realize this proposal does not go this far, I'm +0 for the proposal as a 
> step in the right direction, but it doesn't go far enough in my opinion.
>
> Ross
>
> Get Outlook for Android
>
> 
> From: Craig Russell 
> Sent: Sunday, March 31, 2019 8:30:35 PM
> To: Incubator
> Subject: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking 
> IPMC to vote
>
> This is a proposal to recommend that all Mentors SHOULD vote on podling 
> releases prior to sending the release for a vote to the IPMC.
>
> This is not a MUST, since there are many good reasons why a mentor might be 
> unable to perform the checks needed to vote. We are volunteers after all.
>
> But if this proposal is adopted, it will minimize the occurrences of a 
> podling desperately asking for someone, anyone, on the IPMC to please vote.
>
> It should also minimize the number of podling releases that are shot down in 
> the full IPMC vote because of something that a Mentor is likely to catch.
>
> Thanks for your consideration,
>
> Craig
>
> Craig L Russell
> c...@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

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

[Ross Gardler]

72 hours is a guide. As long as your project community is agreeable you can say 
"72hrs or 3 +1".



Get Outlook for Android


From: Adrian Cole 
Sent: Sunday, March 31, 2019 9:26:08 PM
To: general@incubator.apache.org
Subject: Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking 
IPMC to vote

I have a related question. In Zipkin (incubating) last release of one of
our projects, we had 3 IPMC +1 votes prior to the formal verification vote.
Then we basically just waited 72hrs anyway with no additional votes but it
didn't matter as we had what we needed (another came later but still) [1]

If a project already has 3 IPMC members active verifying and voting.. it
might feel a bit tedious to delay a release an additional 3+ days
especially if there is no additional feedback.


Not sure the answer here, but I hope the situation is relevant to the
thread. For example, should same rules apply when there are no additional
IPMC votes needed from what is carried over from the podling vote?

-A

[1]
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread.html%2F6e26ccaecba70a5cde1f808d82499701562f370441067b96ca65f09a%40%253Cgeneral.incubator.apache.org%253Edata=02%7C01%7C%7Cf3f98ab49c294fdee58408d6b65a22eb%7C84df9e7fe9f640afb435%7C1%7C0%7C636896895573897795sdata=oQg4R6ms2IRkfoGdVAf54vUrhXLaq9DIbmk%2F4SzwTvE%3Dreserved=0

On Mon, Apr 1, 2019, 11:15 AM Ross Gardler  wrote:

> Just like so many things, this is how it used to be. In fact, back in the
> day the only time the IPMC was asked to vote was when there were not enough
> mentor votes.
>
> If you look at all the podlinga I've mentored I have only ever asked for
> an IPMC vote on two occasions (that I recall). One because I had absent
> mentors (the project never graduated due to lack of success as a community)
> and one because it was a very large and complex code base and we asked for
> extra eyes on the first release.
>
> Every other time the community worked with mentors. Once we had the votes
> we notified the IPMC that the vote had passed and moved on.
>
> Requiring an IPMC vote is akin to the board voting on all TLP releases. It
> should be stopped. The IPMC are facilitators not gate keepers.
>
> Individual IPMC members can join the podling communities if they wish to
> participate. Why are podlings and mentors answering to the IPMC by default?
>
> I know the standard answer is because mentors sometimes get too busy.
> Sure. If it happens every release is a problem and having to ask for an
> IPMC vote highlights the problem.
>
> I realize this proposal does not go this far, I'm +0 for the proposal as a
> step in the right direction, but it doesn't go far enough in my opinion.
>
> Ross
>
> Get Outlook for 
> Android
>
> 
> From: Craig Russell 
> Sent: Sunday, March 31, 2019 8:30:35 PM
> To: Incubator
> Subject: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking
> IPMC to vote
>
> This is a proposal to recommend that all Mentors SHOULD vote on podling
> releases prior to sending the release for a vote to the IPMC.
>
> This is not a MUST, since there are many good reasons why a mentor might
> be unable to perform the checks needed to vote. We are volunteers after all.
>
> But if this proposal is adopted, it will minimize the occurrences of a
> podling desperately asking for someone, anyone, on the IPMC to please vote.
>
> It should also minimize the number of podling releases that are shot down
> in the full IPMC vote because of something that a Mentor is likely to catch.
>
> Thanks for your consideration,
>
> Craig
>
> Craig L Russell
> c...@apache.org
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

[Ovilia]

Thanks Craig.

I've updated the download page. Please help check again.
Thank you!

Zhang Wenli
http://zhangwenli.com


Craig Russell  于2019年3月30日周六 下午1:06写道：

> The page http://echarts.apache.org/download.html is very close, but:
>
> The Source link is fine.
> The Signature link and SHA512 link must be changed from
> https://dist.apache.org/repos/dist/release/incubator/echarts/... to
> https://www.apache.org/dist/incubator/echarts/...
>
> The instructions in step 2 refer to downloading from Apache but these
> links are http links and must be https links.
>
> Hope this helps,
>
> Craig
>
>
> > On Mar 29, 2019, at 9:46 PM, Ovilia  wrote:
> >
> > The download link is http://echarts.apache.org/download.html
> >
> > Zhang Wenli
> > http://zhangwenli.com
> >
> >
> > Ovilia  于2019年3月30日周六 下午12:45写道：
> >
> >> I've updated ECharts download page. Hopefully, it's been fixed correctly
> >> this time.
> >> If so, we will send an email to  annou...@apache.org for the release.
> >>
> >> Zhang Wenli
> >> http://zhangwenli.com
> >>
> >>
> >> Craig Russell  于2019年3月21日周四 上午8:23写道：
> >>
> >>> Hi Su Shuang,
> >>>
> >>> You will need to modify your download page to conform to requirements
> (an
> >>> announcement to incubator is not moderated but an announcement to
> >>> annou...@apache.org will be moderated, and this announcement will not
> >>> pass).
> >>>
> >>> You should never refer in the announcement or your download page to
> >>> dist.apache.org. For announcement emails, link to your download page.
> >>> For download pages, link to the mirror chooser and link to the
> checksum and
> >>> signature from www.apache.org/dist/incubator/echarts. Include a link
> to
> >>> your project KEYS file and instructions how to verify the download.
> >>>
> >>> There are many download pages you can model, e.g.
> >>> https://hadoop.apache.org/releases.html
> >>>
> >>> If you need help, your mentors will be able to assist.
> >>>
> >>> Best regards
> >>>
> >>> Craig
> >>>
>  On Mar 20, 2019, at 1:24 PM, SHUANG SU 
> wrote:
> 
>  Hi all,
> 
>  The Apache ECharts (incubating) team is proud to announce Apache
> ECharts
>  version 4.2.1-incubating.
> 
>  ECharts is a powerful, interactive charting and visualization library.
> 
>  Vote thread:
> 
> >>>
> https://lists.apache.org/thread.html/48c6ef114ad39aadb826c06011622ea2834dd1fe5c867980a9ebe411@%3Cgeneral.incubator.apache.org%3E
> 
>  Download Links:
>  https://dist.apache.org/repos/dist/release/incubator/echarts/4.2.1/
> 
>  Release Notes:
>  http://www.apache.org/dist/incubator/echarts/4.2.1/RELEASE_NOTE.txt
> 
>  Website: http://echarts.apache.org/
> 
>  ECharts Resources:
>  - Issue: https://github.com/apache/incubator-echarts/issues
>  - Mailing list: d...@echarts.incubator.apache.org
> 
>  Thanks
> 
>  --
>  Su Shuang (100pah)
>  --
> >>>
> >>> Craig L Russell
> >>> c...@apache.org
> >>>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org  http://db.apache.org/jdo <
> http://db.apache.org/jdo>
>