[jbosstools-issues] [JBoss JIRA] (JBIDE-15527) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Thu Sep 26 13:54:02 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-15527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Boldt updated JBIDE-15527:
-------------------------------
Description:
For JBIDE 4.1.1.Alpha2: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
*{color:orange}If the above target platform does not yet exist, try 4.31.0.Alpha2-SNAPSHOT or 4.31.0.Alpha1.{color}*
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%227.1.0.Alpha2%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.1.1.Alpha2%22%29%29+AND+labels+%3D+task]
See also: JBDS-2773
was:
For JBIDE 4.1.1.Alpha2: Please perform the following tasks:
0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
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:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.31.0.Alpha2
{code}
4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
{code}
git checkout jbosstools-4.1.x
git pull origin jbosstools-4.1.x
git checkout -b jbosstools-4.1.1.Alpha2x
git push origin jbosstools-4.1.1.Alpha2x
{code}
5. Close (not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%227.1.0.Alpha2%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.1.1.Alpha2%22%29%29+AND+labels+%3D+task]
See also: JBDS-2773
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch
> --------------------------------------------
>
> Key: JBIDE-15527
> URL: https://issues.jboss.org/browse/JBIDE-15527
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
> 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:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.31.0.Alpha2
> {code}
> *{color:orange}If the above target platform does not yet exist, try 4.31.0.Alpha2-SNAPSHOT or 4.31.0.Alpha1.{color}*
> 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
> {code}
> git checkout jbosstools-4.1.x
> git pull origin jbosstools-4.1.x
> git checkout -b jbosstools-4.1.1.Alpha2x
> git push origin jbosstools-4.1.1.Alpha2x
> {code}
> 5. Close (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%227.1.0.Alpha2%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.1.1.Alpha2%22%29%29+AND+labels+%3D+task]
> See also: JBDS-2773
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list