+1
Environment: macOS 10.13.4
* asc, sha1, sha512 are good for both src and binary distributions
* binary distribution
- run standalone
- be able to produce and consume messages
- run functions
* src distribution
- be able to compile and run same set of tests on compiled binar
Hi Dave,
the main problem in building the jar as part of build is that we need to
have the Jar built by Maven before the test of that module are executed,
though the Jar itself doesn't have to be in the classpath, otherwise the
test verification is not useful. The test itself was loading a jar and
Hi -
Perhaps I missed the discussion about the Jar file. It looks like the decision
was made to eliminate the test.
I think that a better approach would be to actually compile it as part of the
build. This would allow the test to also serve as a sort of “Hello World” for
Pulsar functions.
Is
Since there have been no further updates on this thread, I think we should
be good to cut the 1.19.0-incubating release.
The last big change that got merged was about the non-persistent topics.
I have one more PR that I'd like to include:
https://github.com/apache/incubator-pulsar/pull/514
(to ha
On Mon, Jul 24, 2017 at 3:20 PM, Dave Fisher wrote:
> In item #3 of the release process two additional checks are needed to help
> with voting.
>
> (a) The output for the RAT report needs to be examined to make sure that
> all of the source has the proper headers. That any excluded files are
> pr
Technically while in the Incubator it is the release votes from IPMC members
that are binding. If 3 of the 4 Mentors vote +1 on the Pulsar Dev list then the
Incubator Vote becomes a formality.
Regards,
Dave
Sent from my iPhone
> On Jul 25, 2017, at 9:26 AM, Matteo Merli wrote:
>
> Yes, as fa
Yes, as far as I understand, first the release needs to be voted in the
Pulsar dev ML. The Pulsar PPMC votes would be binding there (basically all
committers at this point), though anyone else is welcome to verify the
release and vote as well.
Once the Pulsar PPMC approves, then we need to vote ag
Just to confirm, do we have to run two separated votes on step 7 and 8?
Should we run them step by step?
Masakazu
On Tue, Jul 25, 2017 at 8:45 AM, Matteo Merli wrote:
> Ok, my question was also on the line: "is anyone ok in doing a release now"
> ? :)
>
> > Instruction seems to be detailed. Tho
Ok, my question was also on the line: "is anyone ok in doing a release now"
? :)
> Instruction seems to be detailed. Though I will only be able to add
> meaningful comment when I attempt these(volunteer for a release
> manager) :)
Sure, the wiki is a living document. Anyone should feel free to up
Instruction seems to be detailed. Though I will only be able to add
meaningful comment when I attempt these(volunteer for a release
manager) :)
Slightly off topic question: Are we not using Jenkins for the build?
Andrews.
On Mon, Jul 24, 2017 at 3:20 PM, Dave Fisher wrote:
>
>> On Jul 24, 2017,
> On Jul 24, 2017, at 3:09 PM, Matteo Merli wrote:
>
> I have created a wiki page with the WIP instructions for the release
>
> https://github.com/apache/incubator-pulsar/wiki/Release-process
>
> I also have created an INFRA ticket to create the Nexus project so that we
> can publish maven art
I have created a wiki page with the WIP instructions for the release
https://github.com/apache/incubator-pulsar/wiki/Release-process
I also have created an INFRA ticket to create the Nexus project so that we
can publish maven artifacts.
https://issues.apache.org/jira/browse/INFRA-14694
Any comm
Thanks Dave, I think I'll try with some of my colleagues here. I'll let you
know if I can make it.
--
Matteo Merli
On Mon, Jul 24, 2017 at 1:06 PM, Dave Fisher wrote:
>
> > On Jul 24, 2017, at 12:33 PM, Matteo Merli
> wrote:
> >
> > Bay area. Who can I get to sign it? Can any other Apache c
> On Jul 24, 2017, at 12:33 PM, Matteo Merli wrote:
>
> Bay area. Who can I get to sign it? Can any other Apache committer (or PMC
> from other projects) do it?
Yes, if they have participated in a key signing.
I am in the North Bay myself and recently met someone to sign their key. We
could m
Bay area. Who can I get to sign it? Can any other Apache committer (or PMC
from other projects) do it?
--
Matteo Merli
On Mon, Jul 24, 2017 at 12:27 PM, Dave Fisher wrote:
>
> > On Jul 24, 2017, at 12:23 PM, Matteo Merli wrote:
> >
> > On Mon, Jul 24, 2017 at 11:39 AM, Dave Fisher
> wrote:
>
> On Jul 24, 2017, at 12:23 PM, Matteo Merli wrote:
>
> On Mon, Jul 24, 2017 at 11:39 AM, Dave Fisher wrote:
>>
>>> Does for podlings work in the same way as for TLPs? Should we design a
>>> release manager?
>>
>> Yes. I see you created a KEYS file. If someone else is Release Manager
>> then
On Mon, Jul 24, 2017 at 11:39 AM, Dave Fisher wrote:
>
> > Does for podlings work in the same way as for TLPs? Should we design a
> > release manager?
>
> Yes. I see you created a KEYS file. If someone else is Release Manager
> then they can add their key as well.
>
> BTW - Is your Key Signed an
Hi -
> On Jul 21, 2017, at 4:23 PM, Matteo Merli wrote:
>
> (Starting a new thread to detach from the general website discussion)
>
> I think that it would be good to try to release a new Pulsar version ASAP,
> following the Apache release process and requirements.
>
> That would take the proj
(Starting a new thread to detach from the general website discussion)
I think that it would be good to try to release a new Pulsar version ASAP,
following the Apache release process and requirements.
That would take the project out of the current limbo where we are in the
incubator, but we can on
19 matches
Mail list logo
