[
https://issues.apache.org/jira/browse/MESOS-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562878#comment-15562878
]
Alex Clemmer commented on MESOS-3633:
-------------------------------------
The short answer is that these tickets were kind of ill-specified "placeholder"
tickets, meant to dog-ear the work we had to do to get to Windows MVP. By that
measure, this mission is accomplished well enough and the ticket can likely be
closed, unless there's an issue that I've forgotten about. ([~dpravat] can
probably confirm this.)
That said, in case an intrepid user Googles and ends up on this page, it is
worth noting that this is not to say that we are now absolved of known issues
with the Mesos path API. We have a collection of known issues, and we've broken
them into separate tickets so that we can organize work. Particularly, some of
the tests don't pass[1] (there are, for example, assumptions that `/` is the
path delimiter, which is no longer true), and the 255-character-path-length
restriction that some of the Win32 APIs inherited from DOS cause issues with
prod boxes, e.g. [2]. In total I estimate at least a couple weeks of effort,
and perhaps closer to a month, to fully fix all these issues, which involves
changing APIs throughout the codebase.
[1] https://issues.apache.org/jira/browse/MESOS-3442
[2] https://issues.apache.org/jira/browse/MESOS-5849
> Port stout/path.hpp to Windows
> ------------------------------
>
> Key: MESOS-3633
> URL: https://issues.apache.org/jira/browse/MESOS-3633
> Project: Mesos
> Issue Type: Task
> Components: stout
> Reporter: Alex Clemmer
> Assignee: Alex Clemmer
> Fix For: 0.27.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
