Wilfred Spiegelenburg created YUNIKORN-662:
--
Summary: Remove landmark directories from web and shim
Key: YUNIKORN-662
URL: https://issues.apache.org/jira/browse/YUNIKORN-662
Project: Apache
>
> How do you know if it is the version for planning or if that has been
> really
> fixed already?
>
That is JIRA Status + Fix version. If an issue is fixed and the Fix Version
is 0.10, then this issue is fixed in 0.10.
If you have a bug that needs to be backported to a previous
> release or
The problem with using one field for planning and showing where it is
committed is that you get into trouble when you have multiple releases. How
do you know if it is the version for planning or if that has been really
fixed already? If you have a bug that needs to be backported to a previous
[
https://issues.apache.org/jira/browse/YUNIKORN-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-660.
Fix Version/s: 0.11
Resolution: Fixed
cleaned up release area.
Hi Wilfred
If you look at the JIRA document:
https://www.atlassian.com/agile/tutorials/versions.
*Fix version* is the version where you plan on releasing a feature or
bugfix to customers. This field is used for release planning, monitoring
progress and velocity, and is used widely in reporting.
[
https://issues.apache.org/jira/browse/YUNIKORN-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-372.
---
Resolution: Won't Fix
As I remember correctly I opened this one when I was working on the
[
https://issues.apache.org/jira/browse/YUNIKORN-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton reopened YUNIKORN-660:
---
> Remove old releases from release area
> -
>
>
[
https://issues.apache.org/jira/browse/YUNIKORN-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kinga Marton resolved YUNIKORN-660.
---
Fix Version/s: 0.11
Resolution: Fixed
> Remove old releases from release area
>
kingamarton closed pull request #35:
URL: https://github.com/apache/incubator-yunikorn-release/pull/35
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about
Hi Everyone!
I think the safest way for now is to go with 0.11 for the next release.
Right now I think we have a stable and tested version of YuniKorn, but also
have some bigger things ongoing, as were there were mentioned before, such
as the REST API changes, and interface changes. I would
Hi all,
There are multiple fields that can be set with versions in jira. Two are
used in YuniKorn:
* Fix version/s
* Target Version
The Target Version is not shown by default on the pages but should be used
to mark a jira to be targeted for a specific release. Currently that is
0.11. The
[
https://issues.apache.org/jira/browse/YUNIKORN-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-655.
Target Version: 0.11
Resolution: Fixed
release manager added for
[
https://issues.apache.org/jira/browse/YUNIKORN-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ting Yao,Huang closed YUNIKORN-653.
---
Resolution: Duplicate
> Include node sorting policy in cluster REST API
>
13 matches
Mail list logo