[JBoss JIRA] (JBIDE-18156) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Hibernate]
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18156:
--------------------------------------
Summary: For JBIDE 4.2.0.CR1: Code Freeze + Branch [Hibernate]
Key: JBIDE-18156
URL: https://issues.jboss.org/browse/JBIDE-18156
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: hibernate
Reporter: Mickael Istria
Priority: Blocker
For JBIDE 4.2.0.CR1 [Hibernate]: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18154) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central Discovery]
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18154:
--------------------------------------
Summary: For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central Discovery]
Key: JBIDE-18154
URL: https://issues.jboss.org/browse/JBIDE-18154
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: discovery
Reporter: Mickael Istria
Priority: Blocker
For JBIDE 4.2.0.CR1 [Central Discovery]: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18157) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Base]
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18157:
--------------------------------------
Summary: For JBIDE 4.2.0.CR1: Code Freeze + Branch [Base]
Key: JBIDE-18157
URL: https://issues.jboss.org/browse/JBIDE-18157
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core, usage
Reporter: Mickael Istria
Priority: Blocker
For JBIDE 4.2.0.CR1 [Base]: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18159) For JBIDE 4.2.0.CR1: Code Freeze + Branch [JavaEE]
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18159:
--------------------------------------
Summary: For JBIDE 4.2.0.CR1: Code Freeze + Branch [JavaEE]
Key: JBIDE-18159
URL: https://issues.jboss.org/browse/JBIDE-18159
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsf, cdi-extensions, seam2, cdi
Reporter: Mickael Istria
Priority: Blocker
For JBIDE 4.2.0.CR1 [JavaEE]: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18158) For JBIDE 4.2.0.CR1: Code Freeze + Branch [OpenShift]
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18158:
--------------------------------------
Summary: For JBIDE 4.2.0.CR1: Code Freeze + Branch [OpenShift]
Key: JBIDE-18158
URL: https://issues.jboss.org/browse/JBIDE-18158
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Reporter: Mickael Istria
Priority: Blocker
For JBIDE 4.2.0.CR1 [OpenShift]: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18150) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Aerogear]
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18150:
--------------------------------------
Summary: For JBIDE 4.2.0.CR1: Code Freeze + Branch [Aerogear]
Key: JBIDE-18150
URL: https://issues.jboss.org/browse/JBIDE-18150
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid
Reporter: Mickael Istria
Priority: Blocker
For JBIDE 4.2.0.CR1 [Aerogear]: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18151) For JBIDE 4.2.0.CR1: Code Freeze + Branch [JST]
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18151:
--------------------------------------
Summary: For JBIDE 4.2.0.CR1: Code Freeze + Branch [JST]
Key: JBIDE-18151
URL: https://issues.jboss.org/browse/JBIDE-18151
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Mickael Istria
Priority: Blocker
For JBIDE 4.2.0.CR1 [JST]: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18152) For JBIDE 4.2.0.CR1: Code Freeze + Branch [VPE]
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18152:
--------------------------------------
Summary: For JBIDE 4.2.0.CR1: Code Freeze + Branch [VPE]
Key: JBIDE-18152
URL: https://issues.jboss.org/browse/JBIDE-18152
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Mickael Istria
Priority: Blocker
For JBIDE 4.2.0.CR1 [VPE]: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3127) For JBDS 8.0.0.CR1: Code Freeze + Branch
by Mickael Istria (JIRA)
Mickael Istria created JBDS-3127:
------------------------------------
Summary: For JBDS 8.0.0.CR1: Code Freeze + Branch
Key: JBDS-3127
URL: https://issues.jboss.org/browse/JBDS-3127
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: installer
Reporter: Mickael Istria
Priority: Blocker
Fix For: 8.0.0.CR1
For JBDS 8.0.0.CR1: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18149) For JBIDE 4.2.0.CR1: Code Freeze + Branch
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-18149:
--------------------------------------
Summary: For JBIDE 4.2.0.CR1: Code Freeze + Branch
Key: JBIDE-18149
URL: https://issues.jboss.org/browse/JBIDE-18149
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Mickael Istria
Priority: Blocker
Fix For: 4.2.0.CR1
For JBIDE 4.2.0.CR1: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
[Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
*NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
{code}
mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
or
mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
{code}
git fetch origin master
git checkout FETCH_HEAD
git checkout -b jbosstools-4.2.x
git push origin jbosstools-4.2.x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.CR2-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
* *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
See also: JBDS-3127
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months