[
https://issues.apache.org/jira/browse/MESOS-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Mathiske updated MESOS-3758:
----------------------------------
Shepherd: Joris Van Remoortere
> 0.26.0 Release
> --------------
>
> Key: MESOS-3758
> URL: https://issues.apache.org/jira/browse/MESOS-3758
> Project: Mesos
> Issue Type: Task
> Reporter: Bernd Mathiske
> Assignee: Till Toenshoff
> Labels: mesosphere, release
>
> Manage the release of Apache Mesos version 0.26.0.
> The Mesos 0.26.0 release will aim at being timely and at improving
> robustness. It will not be gated by new features. However, there may be
> blockers when it comes to bugs or incompleteness of existing features.
> Once these blockers are resolved, we will start deferring unresolved issues
> by Priority and Status until we are ready to make the first cut.
> Here is how you can stay informed and help out.
> h3. Users
> - Note the "is blocked by" links in this ticket for major targeted features.
> - Check out the 0.26.0
> [dashboard|https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12327111]
> for status indicators.
> - See the in-progress [Release
> Notes|https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333528&styleName=Html&projectId=12311242&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C675829c365428965ebec16702c62d3637db57d84%7Clin]
> to see what's committed so far.
> - Add comments to issues describing your problems or use cases.
> h3. Issue Reporters
> - Set Target Version to 0.26.0, if appropriate.
> - Set Priority for fixing in 0.26.0.
> - Ask around on IRC or dev@ for a Shepherd!
> h3. Developers
> - Newbies: Check out [Accepted, Unassigned, 'newbie'] issues.
> - Looking for something meatier to work on? [Accepted, Unassigned for 0.26]
> - For Shepherdless issues, find a Shepherd before diving too deep!!
> - Update Target Version and Priority, as needed.
> - Discuss your intended design on the JIRA, perhaps sharing a design doc.
> - Update the Status to "In Progress" and "Reviewable" as you go.
> - Assign yourself if you are working on it. Un-assign yourself in case you
> stop before finishing.
> h3. Committers
> - Accept and Shepherd all relevant [Shepherdless issues].
> - Update Target Version and Priority, as needed.
> - Add 'newbie' label to any easy ones.
> h3. Important JIRA fields
> - Target Version: Set to 0.26.0 if you want the issue to be addressed in 0.26.
> - Priority: Indicates how important it is for the issue to be fixed in the
> next release (0.26.0 in this case). If you want to update a Priority, please
> add a comment explaining your reason, and only change the Priority up/down
> one level.
> - Blocked-by Links: major features and critical tickets can be linked as
> blockers to this ticket to give a high-level overview of what we plan to land
> in 0.26. Non-critical issues should just set the "Target Version".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
