& Till
> On Oct 12, 2016, at 2:11 PM, Alex Rukletsov wrote:
>
> Folks,
>
> we have 23 unresolved tickets targeted for Mesos 1.1.0 release, including 7
> blockers and 3 epics (MESOS-5344, MESOS-3421, MESOS-2449), which turns 23
> into 55. Obviously, we can’t make a
& Till
> On Oct 12, 2016, at 2:11 PM, Alex Rukletsov wrote:
>
> Folks,
>
> we have 23 unresolved tickets targeted for Mesos 1.1.0 release, including 7
> blockers and 3 epics (MESOS-5344, MESOS-3421, MESOS-2449), which turns 23
> into 55. Obviously, we can’t make a
Folks,
we have 23 unresolved tickets targeted for Mesos 1.1.0 release, including 7
blockers and 3 epics (MESOS-5344, MESOS-3421, MESOS-2449), which turns 23
into 55. Obviously, we can’t make a cut today.
Shepherds please either commit your blockers by Thu EOD PST or declare them
as non-blockers
Folks,
in preparation for Mesos 1.1.0 release we would like to ask people who have
worked on features in 1.1.0 to either:
* update the CHANGELOG and declare the feature implemented or experimental,
make sure documentation is updated as well;
* postpone to 1.2 and update the related epic
I think you need to clean up the JIRA a bit.
1) Make sure unresolved tickets do not have fix version (1.1.0) set.
2) Move "Fix version 1.1.0" to "Target version 1.1.0".
2) might obviate the need for 1).
On Fri, Oct 7, 2016 at 7:24 AM, Till Toenshoff wrote:
> Hi everyone!
>
> its us who will
Hi everyone!
its us who will be the Release Managers for 1.1.0 - Alex and Till!
We are planning to cut the next release (1.1.0) within three workdays - that
would be Wednesday next week. So, if you have any patches that need to get into
1.1.0 make sure that either is already in the master bran
We are planning to release it in a week or so.
Till has agreed to be the release manager for the release and will be
supported by AlexR.
@Till: Can you create a release dashboard and reply to this thread?
