Re: [RESULT][VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-06-10 Thread Adam Bordelon
FTFY: Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/1.3.0

On Wed, Jun 7, 2017 at 3:03 AM, Michael Park  wrote:

> Hi all,
>
> The vote for Mesos 1.3.0 (rc3) has passed with the
> following votes.
>
> +1 (Binding)
> --
> Vinod Kone
> Benjamin Mahler
> Yan Xu
>
> +1 (Non-binding)
> --
> N/A
>
> There were no 0 or -1 votes.
>
> Please find the release at:
> /1.3.0
>
> It is recommended to use a mirror to download the release:
> http://www.apache.org/dyn/closer.cgi
>
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
> lain;f=CHANGELOG;hb=1.3.0
>
> The mesos-1.3.0.jar has been released to:
> https://repository.apache.org
>
> The website (http://mesos.apache.org) will be updated shortly to reflect
> this release.
>
> Thanks,
>
> MPark & Neil
>


[RESULT][VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-06-07 Thread Michael Park
Hi all,

The vote for Mesos 1.3.0 (rc3) has passed with the
following votes.

+1 (Binding)
--
Vinod Kone
Benjamin Mahler
Yan Xu

+1 (Non-binding)
--
N/A

There were no 0 or -1 votes.

Please find the release at:
/1.3.0

It is recommended to use a mirror to download the release:
http://www.apache.org/dyn/closer.cgi

The CHANGELOG for the release is available at:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.3.0

The mesos-1.3.0.jar has been released to:
https://repository.apache.org

The website (http://mesos.apache.org) will be updated shortly to reflect
this release.

Thanks,

MPark & Neil


Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-06-02 Thread Benjamin Mahler
Thanks Yan!

On Fri, Jun 2, 2017 at 10:45 AM, Yan Xu  wrote:

> +1 (binding)
>
> Ran it in a test cluster.
>
> ---
> Jiang Yan Xu  | @xujyan 
>
> On Thu, Jun 1, 2017 at 2:34 PM, Benjamin Mahler 
> wrote:
>
>> +1 (binding)
>>
>> Looks like ExamplesTest.DynamicReservationFramework is flaky,
>> unfortunately
>> wasn't able to get the logs for a failed run.
>>
>> On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler 
>> wrote:
>>
>> > Not a blocker, but noticed the parallel test runner isn't bundled in the
>> > release, if you configure with '--enable-parallel-test-execution':
>> >
>> > /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
>> > --sequential=*ROOT_* ./stout-tests
>> > /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-
>> runner.py:
>> > No such file or directory
>> >
>> > On Wed, May 31, 2017 at 1:48 PM, Vinod Kone 
>> wrote:
>> >
>> >> Thanks for the triage.
>> >>
>> >> +1 (binding)
>> >>
>> >> On Wed, May 31, 2017 at 1:33 PM, Neil Conway 
>> >> wrote:
>> >>
>> >>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway 
>> >>> wrote:
>> >>> > Attached is the test log for this failure. From a quick look, seems
>> as
>> >>> > though the agent starts to launch the task, including forking the
>> >>> > child process, but no subsequent task status updates or error
>> messages
>> >>> > are observed. Gaston, have you seen this before?
>> >>> >
>> >>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
>> >>> this.
>> >>>
>> >>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>> >>> enough information in the logs to understand what is going on here,
>> >>> although it certainly seems weird that apparently the executor doesn't
>> >>> start.
>> >>>
>> >>> I think this doesn't justify blocking the release, but we should watch
>> >>> to see if the problem recurs.
>> >>>
>> >>> Neil
>> >>>
>> >>
>> >>
>> >
>>
>
>


Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-06-02 Thread Yan Xu
+1 (binding)

Ran it in a test cluster.

---
Jiang Yan Xu  | @xujyan 

On Thu, Jun 1, 2017 at 2:34 PM, Benjamin Mahler  wrote:

> +1 (binding)
>
> Looks like ExamplesTest.DynamicReservationFramework is flaky,
> unfortunately
> wasn't able to get the logs for a failed run.
>
> On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler 
> wrote:
>
> > Not a blocker, but noticed the parallel test runner isn't bundled in the
> > release, if you configure with '--enable-parallel-test-execution':
> >
> > /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
> > --sequential=*ROOT_* ./stout-tests
> > /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-
> gtest-runner.py:
> > No such file or directory
> >
> > On Wed, May 31, 2017 at 1:48 PM, Vinod Kone 
> wrote:
> >
> >> Thanks for the triage.
> >>
> >> +1 (binding)
> >>
> >> On Wed, May 31, 2017 at 1:33 PM, Neil Conway 
> >> wrote:
> >>
> >>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway 
> >>> wrote:
> >>> > Attached is the test log for this failure. From a quick look, seems
> as
> >>> > though the agent starts to launch the task, including forking the
> >>> > child process, but no subsequent task status updates or error
> messages
> >>> > are observed. Gaston, have you seen this before?
> >>> >
> >>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
> >>> this.
> >>>
> >>> I wasn't able to repro this failure. Per Gaston's email, there isn't
> >>> enough information in the logs to understand what is going on here,
> >>> although it certainly seems weird that apparently the executor doesn't
> >>> start.
> >>>
> >>> I think this doesn't justify blocking the release, but we should watch
> >>> to see if the problem recurs.
> >>>
> >>> Neil
> >>>
> >>
> >>
> >
>


Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-06-01 Thread Benjamin Mahler
+1 (binding)

Looks like ExamplesTest.DynamicReservationFramework is flaky, unfortunately
wasn't able to get the logs for a failed run.

On Thu, Jun 1, 2017 at 2:03 PM, Benjamin Mahler  wrote:

> Not a blocker, but noticed the parallel test runner isn't bundled in the
> release, if you configure with '--enable-parallel-test-execution':
>
> /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
> --sequential=*ROOT_* ./stout-tests
> /bin/sh: /Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py:
> No such file or directory
>
> On Wed, May 31, 2017 at 1:48 PM, Vinod Kone  wrote:
>
>> Thanks for the triage.
>>
>> +1 (binding)
>>
>> On Wed, May 31, 2017 at 1:33 PM, Neil Conway 
>> wrote:
>>
>>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway 
>>> wrote:
>>> > Attached is the test log for this failure. From a quick look, seems as
>>> > though the agent starts to launch the task, including forking the
>>> > child process, but no subsequent task status updates or error messages
>>> > are observed. Gaston, have you seen this before?
>>> >
>>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track
>>> this.
>>>
>>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>>> enough information in the logs to understand what is going on here,
>>> although it certainly seems weird that apparently the executor doesn't
>>> start.
>>>
>>> I think this doesn't justify blocking the release, but we should watch
>>> to see if the problem recurs.
>>>
>>> Neil
>>>
>>
>>
>


Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-06-01 Thread Benjamin Mahler
Not a blocker, but noticed the parallel test runner isn't bundled in the
release, if you configure with '--enable-parallel-test-execution':

/Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py
--sequential=*ROOT_* ./stout-tests
/bin/sh:
/Users/bmahler/Downloads/mesos-1.3.0/support/mesos-gtest-runner.py: No such
file or directory

On Wed, May 31, 2017 at 1:48 PM, Vinod Kone  wrote:

> Thanks for the triage.
>
> +1 (binding)
>
> On Wed, May 31, 2017 at 1:33 PM, Neil Conway 
> wrote:
>
>> On Tue, May 30, 2017 at 3:43 PM, Neil Conway 
>> wrote:
>> > Attached is the test log for this failure. From a quick look, seems as
>> > though the agent starts to launch the task, including forking the
>> > child process, but no subsequent task status updates or error messages
>> > are observed. Gaston, have you seen this before?
>> >
>> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>>
>> I wasn't able to repro this failure. Per Gaston's email, there isn't
>> enough information in the logs to understand what is going on here,
>> although it certainly seems weird that apparently the executor doesn't
>> start.
>>
>> I think this doesn't justify blocking the release, but we should watch
>> to see if the problem recurs.
>>
>> Neil
>>
>
>


Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-31 Thread Vinod Kone
Thanks for the triage.

+1 (binding)

On Wed, May 31, 2017 at 1:33 PM, Neil Conway  wrote:

> On Tue, May 30, 2017 at 3:43 PM, Neil Conway 
> wrote:
> > Attached is the test log for this failure. From a quick look, seems as
> > though the agent starts to launch the task, including forking the
> > child process, but no subsequent task status updates or error messages
> > are observed. Gaston, have you seen this before?
> >
> > I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>
> I wasn't able to repro this failure. Per Gaston's email, there isn't
> enough information in the logs to understand what is going on here,
> although it certainly seems weird that apparently the executor doesn't
> start.
>
> I think this doesn't justify blocking the release, but we should watch
> to see if the problem recurs.
>
> Neil
>


Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-31 Thread Neil Conway
On Tue, May 30, 2017 at 3:43 PM, Neil Conway  wrote:
> Attached is the test log for this failure. From a quick look, seems as
> though the agent starts to launch the task, including forking the
> child process, but no subsequent task status updates or error messages
> are observed. Gaston, have you seen this before?
>
> I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.

I wasn't able to repro this failure. Per Gaston's email, there isn't
enough information in the logs to understand what is going on here,
although it certainly seems weird that apparently the executor doesn't
start.

I think this doesn't justify blocking the release, but we should watch
to see if the problem recurs.

Neil


Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-31 Thread Neil Conway
On Tue, May 30, 2017 at 2:36 PM, Vinod Kone  wrote:
> Failed test: OneWayPartitionTest.MasterToSlave
> 

I was able to reproduce this locally, and confirmed that it is a flaky
test. Fix here:

https://reviews.apache.org/r/59685/

I don't think this requires spinning a new 1.3.0 RC.

Neil


Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-30 Thread Gastón Kleiman
On Tue, May 30, 2017 at 3:43 PM, Neil Conway  wrote:

> On Tue, May 30, 2017 at 2:36 PM, Vinod Kone  wrote:
> > Ran on ASF CI.
> >
> > Found following issues.
> >
> > Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
> >  Release/36/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=centos:7,label_exp=(docker%7C%7CHadoop)
> &&(!ubuntu-us1)&&(!ubuntu-eu2)/console>
>
> Attached is the test log for this failure. From a quick look, seems as
> though the agent starts to launch the task, including forking the
> child process, but no subsequent task status updates or error messages
> are observed. Gaston, have you seen this before?
>
> I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.
>

Nope, I haven't seen this before.

It looks like the executor wasn't launched or something went wrong at a
very early stage of the executor's launch.

This is what the logs from a successful run look like:

I0530 20:19:52.679759 11282 launcher.cpp:140] Forked child with pid '11304'
>> for container '703bded9-43de-4950-986f-0eaec7bbe664'
>
> I0530 20:19:52.692080 11268 fetcher.cpp:324] Starting to fetch URIs for
>> container: 703bded9-43de-4950-986f-0eaec7bbe664, directory:
>> /tmp/CommandExecutorCheckTest_CommandCheckDeliveredAndReconciled_fqE44y/slaves/7c74b451-3e64-4c95-8570-ad3b5b60962b-S0/frameworks/7c74b451-3e64-4c95-8570-ad3b5b60962b-/executors/55b387b7-c1f1-47d5-9f19-2d676cd4ef2e/runs/703bded9-43de-4950-986f-0eaec7bbe664
>
> I0530 20:19:53.517201 11268 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:53.517283 11268 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:53.517318 11268 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:53.517367 11268 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 654478ns
>
> I0530 20:19:54.518506 11277 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:54.518584 11277 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:54.518616 11277 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:54.518662 11277 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 568919ns
>
> I0530 20:19:55.520282 11276 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:55.520364 11276 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:55.520409 11276 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:55.520463 11276 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 621097ns
>
> I0530 20:19:56.521884 11271 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:56.521966 11271 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:56.522001 11271 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:56.522047 11271 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 597601ns
>
> I0530 20:19:57.523320 11267 hierarchical.cpp:2095] Filtered offer with
>> cpus(*):1.9; mem(*):992; disk(*):992; ports(*):[31000-32000] on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0 for role * of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-
>
> I0530 20:19:57.523398 11267 hierarchical.cpp:1861] No allocations performed
>
> I0530 20:19:57.523432 11267 hierarchical.cpp:1951] No inverse offers to
>> send out!
>
> I0530 20:19:57.523478 11267 hierarchical.cpp:1445] Performed allocation
>> for 1 agents in 573802ns
>
> I0530 20:19:57.641808 11358 exec.cpp:162] Version: 1.4.0
>
> I0530 20:19:57.648437 11268 slave.cpp:3809] Got registration for executor
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b- from executor(1)@
>> 192.99.40.208:43797
>
> I0530 20:19:57.650589 11279 slave.cpp:2526] Sending queued task
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' to executor
>> '55b387b7-c1f1-47d5-9f19-2d676cd4ef2e' of framework
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b- at executor(1)@
>> 192.99.40.208:43797
>
> I0530 20:19:57.650804 11356 exec.cpp:237] Executor registered on agent
>> 7c74b451-3e64-4c95-8570-ad3b5b60962b-S0
>
> Received SUBSCRIBED event
>
> Subscribed execu

Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-30 Thread Neil Conway
On Tue, May 30, 2017 at 2:36 PM, Vinod Kone  wrote:
> Ran on ASF CI.
>
> Found following issues.
>
> Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
> 

Attached is the test log for this failure. From a quick look, seems as
though the agent starts to launch the task, including forking the
child process, but no subsequent task status updates or error messages
are observed. Gaston, have you seen this before?

I filed https://issues.apache.org/jira/browse/MESOS-7589 to track this.

> Failed test: OneWayPartitionTest.MasterToSlave
> 

Looking into this now.

Neil
[ RUN  ] CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled
I0525 16:55:27.473031  2250 cluster.cpp:162] Creating default 'local' authorizer
I0525 16:55:27.475637  2280 master.cpp:436] Master 
b97c30ee-bdab-4879-ba55-5d32f822c038 (305d67e5598a) started on 172.17.0.2:40622
I0525 16:55:27.475666  2280 master.cpp:438] Flags at startup: --acls="" 
--agent_ping_timeout="15secs" --agent_reregister_timeout="10mins" 
--allocation_interval="1secs" --allocator="HierarchicalDRF" 
--authenticate_agents="true" --authenticate_frameworks="true" 
--authenticate_http_frameworks="true" --authenticate_http_readonly="true" 
--authenticate_http_readwrite="true" --authenticators="crammd5" 
--authorizers="local" --credentials="/tmp/UqWhgS/credentials" 
--framework_sorter="drf" --help="false" --hostname_lookup="true" 
--http_authenticators="basic" --http_framework_authenticators="basic" 
--initialize_driver_logging="true" --log_auto_initialize="true" 
--logbufsecs="0" --logging_level="INFO" --max_agent_ping_timeouts="5" 
--max_completed_frameworks="50" --max_completed_tasks_per_framework="1000" 
--max_unreachable_tasks_per_framework="1000" --port="5050" --quiet="false" 
--recovery_agent_removal_limit="100%" --registry="in_memory" 
--registry_fetch_timeout="1mins" --registry_gc_interval="15mins" 
--registry_max_agent_age="2weeks" --registry_max_agent_count="102400" 
--registry_store_timeout="100secs" --registry_strict="false" 
--root_submissions="true" --user_sorter="drf" --version="false" 
--webui_dir="/mesos/mesos-1.3.0/_inst/share/mesos/webui" 
--work_dir="/tmp/UqWhgS/master" --zk_session_timeout="10secs"
I0525 16:55:27.475993  2280 master.cpp:488] Master only allowing authenticated 
frameworks to register
I0525 16:55:27.476006  2280 master.cpp:502] Master only allowing authenticated 
agents to register
I0525 16:55:27.476013  2280 master.cpp:515] Master only allowing authenticated 
HTTP frameworks to register
I0525 16:55:27.476022  2280 credentials.hpp:37] Loading credentials for 
authentication from '/tmp/UqWhgS/credentials'
I0525 16:55:27.476297  2280 master.cpp:560] Using default 'crammd5' 
authenticator
I0525 16:55:27.476441  2280 http.cpp:975] Creating default 'basic' HTTP 
authenticator for realm 'mesos-master-readonly'
I0525 16:55:27.476702  2280 http.cpp:975] Creating default 'basic' HTTP 
authenticator for realm 'mesos-master-readwrite'
I0525 16:55:27.476845  2280 http.cpp:975] Creating default 'basic' HTTP 
authenticator for realm 'mesos-master-scheduler'
I0525 16:55:27.476972  2280 master.cpp:640] Authorization enabled
I0525 16:55:27.477180  2272 whitelist_watcher.cpp:77] No whitelist given
I0525 16:55:27.477191  2270 hierarchical.cpp:158] Initialized hierarchical 
allocator process
I0525 16:55:27.480708  2284 master.cpp:2161] Elected as the leading master!
I0525 16:55:27.480739  2284 master.cpp:1700] Recovering from registrar
I0525 16:55:27.480864  2285 registrar.cpp:345] Recovering registrar
I0525 16:55:27.481547  2285 registrar.cpp:389] Successfully fetched the 
registry (0B) in 645888ns
I0525 16:55:27.481663  2285 registrar.cpp:493] Applied 1 operations in 22833ns; 
attempting to update the registry
I0525 16:55:27.482271  2285 registrar.cpp:550] Successfully updated the 
registry in 556032ns
I0525 16:55:27.482409  2285 registrar.cpp:422] Successfully recovered registrar
I0525 16:55:27.482946  2277 hierarchical.cpp:185] Skipping recovery of 
hierarchical allocator: nothing to recover
I0525 16:55:27.482945  2286 master.cpp:1799] Recovered 0 agents from the 
registry (129B); allowing 10mins for agents to re-register
I0525 16:55:27.487871  2250 containerizer.cpp:221] Using isolation: 
posix/cpu,posix/mem,filesystem/posix,network/cni
W0525 16:55:27.488440  2250 backend.cpp:76] Failed to create 'aufs' backend: 
AufsBackend requires root privileges
W0525 16:55:27.488562  225

Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-30 Thread Vinod Kone
Ran on ASF CI.

Found following issues.

Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled



Failed test: OneWayPartitionTest.MasterToSlave


Can you confirm if these are known or new issues?

Thanks,

On Thu, May 25, 2017 at 2:20 AM, Michael Park  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.3.0.
>
>
> 1.3.0 includes the following:
> 
> 
>   - Multi-role framework support
>   - Executor authentication support
>   - Allow frameworks to modify their roles.
>
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
> lain;f=CHANGELOG;hb=1.3.0-rc3
> 
> 
>
> The candidate for Mesos 1.3.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz
>
> The tag to be voted on is 1.3.0-rc3:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.0-rc3
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos
> -1.3.0.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos
> -1.3.0.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1198
>
> Please vote on releasing this package as Apache Mesos 1.3.0!
>
> The vote is open until Tue May 30 11:59:59 PDT 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.3.0
> [ ] -1 Do not release this package because ...
>
> Thanks,
>
> MPark & Neil
>


[VOTE] Release Apache Mesos 1.3.0 (rc3)

2017-05-25 Thread Michael Park
Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.3.0.


1.3.0 includes the following:

  - Multi-role framework support
  - Executor authentication support
  - Allow frameworks to modify their roles.

The CHANGELOG for the release is available at:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.3.0-rc3


The candidate for Mesos 1.3.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz

The tag to be voted on is 1.3.0-rc3:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.0-rc3

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz.asc

The PGP key used to sign the release is here:
https://dist.apache.org/repos/dist/release/mesos/KEYS

The JAR is up in Maven in a staging repository here:
https://repository.apache.org/content/repositories/orgapachemesos-1198

Please vote on releasing this package as Apache Mesos 1.3.0!

The vote is open until Tue May 30 11:59:59 PDT 2017 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.3.0
[ ] -1 Do not release this package because ...

Thanks,

MPark & Neil