Very useful.
On Tue, Jun 4, 2019 at 9:22 PM Adrian Cole wrote:
> Hi, all.
>
> Through Zipkin's incubation, I noticed that knowledge of state of the
> art is not equally distributed. Some voting approaches already in use
> aren't known. Also what you can use to automate isn't known. As
> podlin
+1 (binding)
Looks ok for me
[x ] Download links are valid.
[x ] Checksums and PGP signatures are valid.
[x ] DISCLAIMER is included.
[x ] Source code artifacts have correct names matching the current
release.
[x ] LICENSE and NOTICE files are correct for each OpenWhisk repository.
[
Thanks Adrian, this is all good to know.
> On Jun 4, 2019, at 9:21 PM, Adrian Cole wrote:
>
> Hi, all.
>
> Through Zipkin's incubation, I noticed that knowledge of state of the
> art is not equally distributed. Some voting approaches already in use
> aren't known. Also what you can use to autom
Hi, all.
Through Zipkin's incubation, I noticed that knowledge of state of the
art is not equally distributed. Some voting approaches already in use
aren't known. Also what you can use to automate isn't known. As
podlings don't always know the right questions to ask, it might be
beneficial for fut
Hi,
Thanks Sam for the advice.
> Been lurking. Before I proceed, I will note that you have two members
> of the board and one infrastructure representative participating.
> Each has either explicitly or implicitly supported the idea of the
> incubator setting direction for podlings.
Set directi
On Sat, Jun 1, 2019 at 7:50 PM Justin Mclean wrote:
>
> Hi,
>
> > Point me to where you are not allowed to make non-official podling releases
> > that conform to Incubator policy.
>
> I find that hard to parse and perhaps you meant don’t conform to incubator
> policy? But either way it’s not incu
On Tue, Jun 4, 2019 at 7:12 PM Adrian Cole wrote:
>...
> https://github.com/apache/incubator-zipkin/issues/2544
That is pretty damned awesome.
> > As others have mentioned, such release bugs would be labelled as blocking
> > for graduation. Ideally the bug ticket numbers would be listed in a
> > disclaimer file within the release.
>
> Interesting idea, that list would need to be kept up to date in there. It
> might be easier to just tag
Hi,
> Perhaps one approach is to maintain a list of "release issues" which are
> deemed "minor offences". As long as there are bugs raised against such
> "release issues", then no further permission would be required. Anything
> outside the "minor offences" would require explicit permission.
+1
Hi,
> I would like to have the write access to the cwiki for uploading the report
> for singa.
You should already have access just log in with your ASF username and password.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsu
This email is to notify general@i.a.o that a graduation community
[VOTE] is in progress for Apache OpenWhisk (incubating).
-r
-- Forwarded message -
From: Rodric Rabbah
Date: Tue, Jun 4, 2019 at 5:25 PM
Subject: [VOTE] Apache OpenWhisk graduation to Top Level Project
To:
Hi al
Hi,
I would like to have the write access to the cwiki for uploading the report
for singa.
My apache ID wangwei; My wiki account is wangwei.cs
Thanks.
Regards,
Wei
On Thu, May 30, 2019 at 7:24 PM Justin Mclean wrote:
> Hi,
>
> > I would like access to the wiki, I will help maintain the Milgaro
Hello Community,
The Apache OpenWhisk (incubating) team is pleased to announce the source
release of 13 language runtimes version 1.13.0. These language runtimes
allow Apache OpenWhisk (incubating) to run serverless function in
JavaScript, Python, Go, Ruby, Dotnet, Swift, PHP, Java, and Docker
co
Perhaps one approach is to maintain a list of "release issues" which are
deemed "minor offences". As long as there are bugs raised against such
"release issues", then no further permission would be required. Anything
outside the "minor offences" would require explicit permission.
As others have me
Hi,
> Historically, demonstrably, we have applied a different policy to "podling
> releases" that is a bit more lenient. Once the podling graduates, it must
> conform to the formal Apache release guidelines.
1. There is no seperate incubator release policy for podling/IPMC releases,
well no form
Hi,
>> That is demonstrably not true, as (historically) the Incubator has made
>> releases with GPL'd code in them (eg. Hibernate).
>
> I don’t understand the choice of words :(
That’s because while it was a software a release is was not an Apache releases.
The word release has several differen
On Tue, Jun 4, 2019 at 12:08 AM Hen wrote:
> On Sun, Jun 2, 2019 at 11:53 Greg Stein wrote:
> > On Sun, Jun 2, 2019 at 1:22 PM Hen wrote:
> > >...
> > > * Incubating releases are Apache releases.
> >
> > That is demonstrably not true, as (historically) the Incubator has made
> > releases with G
17 matches
Mail list logo
