[ 
https://issues.apache.org/jira/browse/OAK-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532413#comment-14532413
 ] 

Thomas Mueller edited comment on OAK-2846 at 5/7/15 10:34 AM:
--------------------------------------------------------------

I created a label called {{considerFor1.2}} for issues that I think should be 
considered for 1.2. I didn't commit them in the 1.0 branch yet, so the above 
query wouldn't work for that. The query for the label is:

https://issues.apache.org/jira/issues/?filter=-1&jql=project%20%3D%20OAK%20AND%20labels%20%3D%20considerFor1.2


was (Author: tmueller):
I created a label for issues that I think should be considered for 1.2. I 
didn't commit them in the 1.0 branch yet, so the above query wouldn't work for 
that:

https://issues.apache.org/jira/issues/?filter=-1&jql=project%20%3D%20OAK%20AND%20labels%20%3D%20considerFor1.2

> Merge missing fixes to 1.2 branch which were made to 1.0 branch
> ---------------------------------------------------------------
>
>                 Key: OAK-2846
>                 URL: https://issues.apache.org/jira/browse/OAK-2846
>             Project: Jackrabbit Oak
>          Issue Type: Task
>            Reporter: Chetan Mehrotra
>            Priority: Blocker
>             Fix For: 1.2.4
>
>
> Currently as only very critical fixes are being merged to 1.2 branch for 
> 1.2.3 release. Due to this some fixes merged to 1.0 branch have not been 
> merged to 1.2 branch.
> This task is meant to ensure that all such fixes are merged to 1.2 branch 
> before 1.2.4 release is made.
> Following query list down such issues 
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=project%20%3D%20%22Jackrabbit%20Oak%22%20and%20status%20%3D%20Resolved%20and%20fixVersion%20%3D%201.0.14%20and%20fixVersion%20!%3D%201.2.3&runQuery=true



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to