+1 (binding)
So far I've checked:
* signatures and digests (md5 checksums can be removed)
* source releases file layouts
* matched git tags and commit ids
* incubator suffix and disclaimer
* LICENSE & NOTICE files look good
* no binary files in the source release
* clean build (osx 10.12.6)
I'd
Hi,
Yep sorry my fault, I can see that they should be run manually the last
Wednesday of the month.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
Hi,
There been some discussion on bylaws/guidelines recently and it was suggest
that the IPMC document a default set for projects to use. So I’ve come up with
a default set of guidelines [1] using links to existing content when I could
find it. I tried to make it as minimal as possible.
Hi Hanks，
I just checked the release vote mail, it's just for rc3 not for the rc4.
Can you update the link for voted mail?
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Sep 7, 2018 at 5:51 PM Hanks Zhang wrote:
>
> Dear IPMC members,
>
> This is a call for the vote to release
HI,
> I'm a bit curious about why this was sent, so I'll bite.
Because a new podling didn’t report monthly for the first 3 months as they are
required to.
> I'm a mentor on a brand new podling. The report template should have been
> generated on 8/29, the day before this podling was accepted
I am probably on a similar situation with a new podling that I delayed the
setup a bit due to conferences. We will start reporting next month.
On Sun, Sep 9, 2018 at 8:20 PM John D. Ament wrote:
> I'm a bit curious about why this was sent, so I'll bite.
>
> I'm a mentor on a brand new podling.
HI,
> I've noticed in the past few months, the incubator report timeline emails
> have stopped.
I’m not sure they were automated.
I’ve posted the draft for this month here which includes the dates due, but in
future I include the dates in the email to this list so people know without
Hi Justin
Good checklist, like it.
--
Sheng Wu
Apache SkyWalking
-- Original --
From: "justin";
Date: Mon, Sep 10, 2018 08:31 AM
To: "general";
Subject: Incubator release checklist
HI,
As part of the workshop I ran recently I
I'm a bit curious about why this was sent, so I'll bite.
I'm a mentor on a brand new podling. The report template should have been
generated on 8/29, the day before this podling was accepted into the
incubator. Yet for some reason, they had a report due. I'm not actually
sure why this was the
Hi,
I've noticed in the past few months, the incubator report timeline emails
have stopped. I had previously used this as a reminder as a mentor to
ensure my podlings were reporting (since in all honesty, I'm not subscribed
to all the dev lists).
Is there a reason this was dropped? I see that
Hi,
> Great, some of these are accomplished by one line commands, maybe would be
> good to add those into the checklist as well.
Mostly, but It's going to vary from project to project depending on on the
build process and technology and a lot of it is manual observation. We could
possibly
On Sun, Sep 9, 2018 at 5:31 PM Justin Mclean
wrote:
> HI,
>
> As part of the workshop I ran recently I had people look at a real release
> and go though a checklist before voting on it, it my be of some help other
> people checking releases. I’ve just added a version of it to the incubator
>
Yeah, I'm totally agree with that.
>From my experience, I really learn a lot by checking the mail thread
discussion and verifying the kit myself with the help of checklist.
Maybe we can encourage the people to participate the vote in the
general@incubator to get the field experience.
Willem Jiang
Hi,
> I think an online version would be really helpful.
> As for the self-paced version, I think just making the recording available
> later should be enough.
The reason I suggested a self paced one it that includes a number of
activities, checking a real release, voting on committers and teh
Hi Justin,
I think an online version would be really helpful.
As for the self-paced version, I think just making the recording available
later should be enough.
Cheers,
Yaniv
On Mon, 10 Sep 2018 at 10:30 am, Justin Mclean
wrote:
> Hi,
>
> A few month back I ran an incubator workshop at FOSS
HI,
As part of the workshop I ran recently I had people look at a real release and
go though a checklist before voting on it, it my be of some help other people
checking releases. I’ve just added a version of it to the incubator wiki. [1]
Feedback welcome.
Thanks,
Justin
1.
Hi,
A few month back I ran an incubator workshop at FOSS backstage that covered
making and voting on releases and voting on committers into the projects. It
had several exercises
Would anyone be interested in either a:
1) Online self-paced version
2) Online live version (i.e. me going through
That's why I meant when I said finding the build instructions was
trivial enough that I thought it should not block a release.
The README contains a clear link to the Documentation (which is a link
to a local file), and that file is a very comprehensive index with
direct links to architecture,
Justin,
Can you please remove Josh Elser from the list of inactive mentors for Rya?
He only missed the last report and he is always available when we have
questions.
Thank you,
Adina
On Sat, Sep 8, 2018 at 8:52 PM, Justin Mclean
wrote:
> Hi,
>
> There been several discussions over several
Hi,
> I honestly don't have the time to mentor them in an official capacity - if
> I'm listed as anything but champion, then yes, remove me as a mentor. I'll
> continue in a low-capacity to provide help when I can, but I have other
> priorities first and foremost :)
Done and sorted.
Thanks,
On 09/09/2018 11:33 AM, Justin Mclean wrote:
HI,
There seems to be a bit of confusion here. I am not a mentor for Annotator, yet
I am listed as one.
You listed as one here. [1]
It get it’s info (I believe) from the podling.xml files which has this in it
for Annotator:
HI,
> There seems to be a bit of confusion here. I am not a mentor for Annotator,
> yet I am listed as one.
You listed as one here. [1]
It get it’s info (I believe) from the podling.xml files which has this in it
for Annotator:
Nick Kew
Brian McCallister
There seems to be a bit of confusion here. I am not a mentor for
Annotator, yet I am listed as one. I did champion it (and offer
advice/help on occasion), but AIUI the champion's duties officially stop
once the project has entered incubation and gotten set up. If this is
not the case, then our
Hi,
> Perhaps add some recognition in the text of the email that there may
> be activity that we are unaware of? (Unlikely, but it seems rude to
> presume.)
I guess it’s possible you can mentor by just watching and only directing were
needed, so if everything going well there may be no need for
Hi,
> Justin, given that the next release will provide this information so clearly
> from the base directory, knowing that the next release will be in order, are
> you ok with letting this release pass through?
That is not up to me, that is up for other IPMC members to vote +1 on it.
Thanks,
Sorry, I just got some time back to this thread.
I just went through the dev discussion of the dubbo and found out
dubbo community are planning the next release cut by discussion the
bug fix list first. I'm sure we could do it better in the next
release.
Here are my +1 for this vote.
I can build
> First of all, there is a direct link to that build page, in README of
> master and 5.x branches. See
> https://github.com/apache/incubator-skywalking#compiling-project
> We have both links to document and compiling guide.
This is excellent in my opinion.
>From the terminal I can read the
27 matches
Mail list logo
