Re: [VOTE] Release Apache Mesos 1.5.0 (rc2)

[Jie Yu]

+1

Verified in our internal CI that `sudo make check` passed in CentOS 6,
CentOS7, Debian 8, Ubuntu 14.04, Ubuntu 16.04 (both w/ or w/o SSL enabled).


On Thu, Feb 1, 2018 at 5:36 PM, Gilbert Song  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.5.0.
>
> 1.5.0 includes the following:
> 
> 
>   * Support Container Storage Interface (CSI).
>   * Agent reconfiguration policy.
>   * Auto GC docker images in Mesos Containerizer.
>   * Standalone containers.
>   * Support gRPC client.
>   * Non-leading VOTING replica catch-up.
>
>
> 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.5.0-rc2
> 
> 
>
> The candidate for Mesos 1.5.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.5.0-rc2/mesos-1.5.0.tar.gz
>
> The tag to be voted on is 1.5.0-rc2:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.5.0-rc2
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.5.0-rc2/mesos
> -1.5.0.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.5.0-rc2/mesos
> -1.5.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 in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1222
>
> Please vote on releasing this package as Apache Mesos 1.5.0!
>
> The vote is open until Tue Feb  6 17:35:16 PST 2018 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.5.0
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Jie and Gilbert
>

Access changes to Mesosphere CI Infrastructure

[Judith Malnick]

Hi Everyone,

Mesosphere is refactoring the user interface for our CI infrastructure, and
in the meantime, we need to temporarily close off public access to CI build
logs and the ability for community contributors to trigger builds. DC/OS
and Marathon contributors might see changes to their permissions. Mesos
contributors should be unaffected.

You will still be able to see high-level CI status in GitHub, and engage
with committers on pull requests and through all the normal communication
channels (Slack, email, Jira, etc.). If you need additional detail about
your CI results, don't hesitate to ask a Mesosphere shepherd for more
complete logs. If you aren't sure who to contact or are having trouble
getting access to the information you need, please email me or reach out on
Slack  (@judith.mesosphere); I'm glad to connect you
with someone who can help.

Building the new public CI interface is expected to take at least a few
months. You will probably need to request an account to access your full CI
logs in the new system. We will send out updates as we make progress, but
in the meantime, please don't hesitate to ask if you have any questions.

All the best!

Judith


-- 
Judith Malnick
Community Manager
310-709-1517

RE: Soliciting Hackathon Ideas

[Bruce Campbell]

Mesos modules for windows?

-Original Message-
From: Andrew Schwartzmeyer [mailto:and...@schwartzmeyer.com] 
Sent: Friday, February 2, 2018 12:47 PM
To: dev@mesos.apache.org
Subject: Soliciting Hackathon Ideas

Hello all,

Next month I'll be attending HackIllinois 
(https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhackillinois.org%2F=02%7C01%7CBruce.Campbell%40microsoft.com%7C2c276fad49384eef40d708d56a7e2ee7%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C1%7C636532012546050886=q8wilsWFhPRONE3pKp2ypuY6iiDwY0fyGzubzqapnm0%3D=0)
 as an open-source mentor. It's a huge student-run hackathon at the University 
of Illinois at Urbana-Champaign, running from February 23rd to the 25th. 
Students from a multitude of schools will be attending (they even bus them in). 
The hackathon has an open-source focus, and while there will be many projects 
for the students to work on, I want to make sure Mesos gets some attention too.

I am asking you all for open issues and new ideas for small, beginner-friendly 
projects that could fit a two-day Hackathon project. 
For Mesos, I'm looking through our open issues labeled "easyfix", "beginner", 
or "newbie", which actually returns 74 results! If you have anything in 
particular that you think would be a good fit, please let me know. I'd like to 
go with a list of vetted issues so I don't accidentally start some students in 
on a giant can of worms. Our excellent new Beginner Contributor Guide will be a 
huge help too.

Thanks,

Andy

P.S. If any of you also want to attend, let me know, and I'll get you in touch 
with their director.

Soliciting Hackathon Ideas

[Andrew Schwartzmeyer]

Hello all,

Next month I'll be attending HackIllinois (https://hackillinois.org/) as 
an open-source mentor. It's a huge student-run hackathon at the 
University of Illinois at Urbana-Champaign, running from February 23rd 
to the 25th. Students from a multitude of schools will be attending 
(they even bus them in). The hackathon has an open-source focus, and 
while there will be many projects for the students to work on, I want to 
make sure Mesos gets some attention too.


I am asking you all for open issues and new ideas for small, 
beginner-friendly projects that could fit a two-day Hackathon project. 
For Mesos, I'm looking through our open issues labeled "easyfix", 
"beginner", or "newbie", which actually returns 74 results! If you have 
anything in particular that you think would be a good fit, please let me 
know. I'd like to go with a list of vetted issues so I don't 
accidentally start some students in on a giant can of worms. Our 
excellent new Beginner Contributor Guide will be a huge help too.


Thanks,

Andy

P.S. If any of you also want to attend, let me know, and I'll get you in 
touch with their director.

Re: No more Issue update emails

[Vinod Kone]

Yes, most updates to ticket metadata (assignee, comments etc have special
rules). Watchers will still get those updates.

See our notification scheme here:
https://issues.apache.org/jira/plugins/servlet/project-config/MESOS/notifications

On Thu, Feb 1, 2018 at 3:16 PM, Benjamin Mahler  wrote:

> This includes any updates to description, priority, target versions? If I
> watch a ticket will I still get update emails?
>
> On Thu, Feb 1, 2018 at 12:29 PM Vinod Kone  wrote:
>
> > Hi folks,
> >
> > Just a heads up that I've had our JIRA notification scheme changed so
> that
> > the issues@ list is no longer emailed when an issue is updated. So no
> more
> > emails for story point changes or sprint changes! Hopefully you will
> > appreciate the reduction in email to the list.
> >
> > Thanks,
> > Vinod
> >
>

Re: Boost version upgrade

[Benno Evers]

Just a quick follow-up, the version was bumped to 1.65 in 469363d.

On Tue, Jan 9, 2018 at 6:51 PM, Vinod Kone  wrote:

> If it’s backwards compatible then let’s go for it.
>
> @vinodkone
>
> > On Jan 9, 2018, at 9:21 AM, Benno Evers  wrote:
> >
> > Hi folks,
> >
> > for those of you who were looking at our build infrastructure recently,
> you
> > may have noticed that the unfortunate combination of the default
> `-Werror`
> > flag and the bundled boost version that contains code which generates a
> > warning regarding unused local typedefs has, over the last year, spawned
> > several workarounds including a hardcoded `-Wno-unused-local-typedefs`
> > flag, the abuse of the `-isystem` flag to disable warnings in third-party
> > dependencies and finally the `--disable-werror` option to not set
> `-Werror`
> > by default.
> >
> > To finally get rid of the warning, we were considering upgrading the
> > bundled boost version to Boost 1.65 in this review chain:
> > https://reviews.apache.org/r/62161/
> >
> > As far as I'm aware, this change should be fully backwards-compatible for
> > people who are building against a non-bundled version of boost.
> >
> > Would there be any objections or concerns from the community about this?
> >
> > Best regards,
> > --
> > Benno Evers
> > Software Engineer, Mesosphere
>



-- 
Benno Evers
Software Engineer, Mesosphere