yes. fixed!

On Thu, Feb 4, 2016 at 10:51 AM, David Forsythe <dforsy...@gmail.com> wrote:

> Hi Vinod,
>
> Would it be right to assume these tickets should also probably have their
> fix version updated?
>
> https://issues.apache.org/jira/browse/MESOS-4211
> https://issues.apache.org/jira/browse/MESOS-4212
> https://issues.apache.org/jira/browse/MESOS-4251
> https://issues.apache.org/jira/browse/MESOS-4252
>
>
>
> On Thu, Feb 4, 2016 at 10:34 AM Vinod Kone <vinodk...@apache.org> wrote:
>
> > Looks like this didn't show up in the CHANGELOG because the "Fix version"
> > was not set on the ticket.
> >
> > Typically the release manager(s) ensures all fixed tickets have a Fix
> > version <http://mesos.apache.org/documentation/latest/release-guide/>
> > before cutting the release, but looks like this fell through the cracks
> :(
> >
> > I will fix it for now.
> >
> >
> > On Thu, Feb 4, 2016 at 10:16 AM, haosdent <haosd...@gmail.com> wrote:
> >
> > > Hi, David. I could saw you commit in 0.27
> > >
> > >
> >
> https://github.com/apache/mesos/blob/0.27.0/3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> > > Why you said it is missing?
> > >
> > > On Fri, Feb 5, 2016 at 2:11 AM, David Forsythe <dforsy...@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > A few changes for FreeBSD support landed in this release (at least
> > > > partially), but they don't seem to have made it into CHANGELOG. More
> > > > concerning is that a file in stout seems to be missing[1].
> > > >
> > > > For CHANGELOG, I assume I did something wrong in JIRA (example
> ticket:
> > > [2]
> > > > -- if something is wrong there, please let me know), but I'm not sure
> > > what
> > > > do about getting new files included. What can I do to make sure that
> > > > included changes are complete in future releases?
> > > >
> > > > Thanks!
> > > >
> > > > [1] 3rdparty/libprocess/3rdparty/stout/include/stout/os/freebsd.hpp
> > > > [2] https://issues.apache.org/jira/browse/MESOS-1563
> > > >
> > >
> > >
> > >
> > > --
> > > Best Regards,
> > > Haosdent Huang
> > >
> >
>

Reply via email to