Looks like a critical enough bug that I will cancel this vote and spin up
another RC for vote.


On Thu, Oct 20, 2016 at 8:59 AM, Jie Yu <yujie....@gmail.com> wrote:

> +0
>
> If possible, would love to get this into 1.0.2:
> https://issues.apache.org/jira/browse/MESOS-6420
>
> This just got fixed by Santhosh.
>
> - Jie
>
> On Tue, Oct 18, 2016 at 2:51 PM, Vinod Kone <vinodk...@apache.org> wrote:
>
>> Hi all,
>>
>>
>> Please vote on releasing the following candidate as Apache Mesos 1.0.2.
>>
>>
>> 1.0.2 includes the following:
>>
>> ------------------------------------------------------------
>> --------------------
>>
>> ** Bug
>>
>>
>>     * [MESOS-5613] - mesos-local fails to start if MESOS_WORK_DIR isn't
>> set.
>>
>>     * [MESOS-6013] - Use readdir instead of readdir_r.
>>
>>
>>     * [MESOS-6026] - Tasks mistakenly marked as FAILED due to race b/w
>> <feff>⁠sendExecutorTerminatedStatusUpdate()<feff>⁠ and <feff>
>> ⁠_statusUpdate()<feff>⁠
>>
>>     * [MESOS-6074] - Master check failure if the metrics endpoint is
>> polled
>> soon after it starts
>>
>>     * [MESOS-6100] - Make fails compiling 1.0.1
>>
>>
>>     * [MESOS-6104] - Potential FD double close in libevent's
>> implementation
>> of `sendfile`.
>>
>>     * [MESOS-6118] - Agent would crash with docker container tasks due to
>> host mount table read.
>>
>>     * [MESOS-6122] - Mesos slave throws systemd errors even when passed a
>> flag to disable systemd
>>
>>     * [MESOS-6152] - Resource leak in libevent_ssl_socket.cpp.
>>
>>
>>     * [MESOS-6216] - LibeventSSLSocketImpl::create is not safe to call
>> concurrently with os::getenv
>>
>>     * [MESOS-6233] - Master CHECK fails during recovery while relinking to
>> other masters
>>
>>     * [MESOS-6234] - Potential socket leak during Zookeeper network
>> changes
>>
>>
>>     * [MESOS-6245] - Driver based schedulers performing explicit
>> acknowledgements cannot acknowledge updates from HTTP based executors.
>>
>>     * [MESOS-6246] - Libprocess links will not generate an ExitedEvent if
>> the socket creation fails
>>
>>     * [MESOS-6269] - CNI isolator doesn't activate loopback interface
>>
>>
>>     * [MESOS-6274] - Agent should not allow HTTP executors to re-subscribe
>> before containerizer recovery is done.
>>
>>     * [MESOS-6324] - CNI should not use `ifconfig` in executors
>> `pre_exec_command`
>>
>>     * [MESOS-6391] - Command task's sandbox should not be owned by root if
>> it uses container image.
>>
>>     * [MESOS-6393] - Deprecated SSL_ environment variables are non
>> functional already.
>>
>>
>>
>>
>> ** Improvement
>>
>>
>>     * [MESOS-6075] - Avoid libprocess functions in `mesos-containerizer
>> launch`.
>>
>>     * [MESOS-6299] - Master doesn't remove task from pending when it is
>> invalid
>>
>>
>>
>>
>> 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.0.2-rc1
>>
>> ------------------------------------------------------------
>> --------------------
>>
>>
>> The candidate for Mesos 1.0.2 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/1.0.2-rc1/mesos-1.0.2.tar.gz
>>
>>
>> The tag to be voted on is 1.0.2-rc1:
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.2-rc1
>>
>>
>> The MD5 checksum of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/1.0.2-rc1/mesos
>> -1.0.2.tar.gz.md5
>>
>>
>> The signature of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/1.0.2-rc1/mesos
>> -1.0.2.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-1160
>>
>>
>> Please vote on releasing this package as Apache Mesos 1.0.2!
>>
>>
>> The vote is open until Fri Oct 21 14:49:04 PDT 2016 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>>
>> [ ] +1 Release this package as Apache Mesos 1.0.2
>>
>> [ ] -1 Do not release this package because ...
>>
>>
>> Thanks,
>>
>
>

Reply via email to