Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-19608

For JBIDE 4.3.0.Alpha2: Code Freeze + Branch

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Blocker
    • 4.3.0.Alpha2
    • None
    • build
    • Sprint #2 April 2015

    Description

      For JBIDE 4.3.0.Alpha2: Please perform the following tasks:

      0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), Reject this JIRA.

      Otherwise:

      0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2

      Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2

      1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.

      NOTE: If you already did this for your master branch, you do not need to do so again. Please also ensure that the version of your code in the master branch is greater than your code in the 4.2.x branch. 

      mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT

      2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT; 

        <parent>
    <groupId>org.jboss.tools</groupId>
    <artifactId>parent</artifactId>
    <version>4.3.0.Alpha2-SNAPSHOT</version>
  </parent>

      3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;

      mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT  # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2           # (if the TP is already released)

      4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch; 

      git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x

      5. Close (do not resolve) this JIRA when done.

      Search for all task JIRA

      See also: JBDS-3412

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users JBDS-3285 Easy Import of non-eclipse projects

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3354 Seam 2 is still included in JBDS 9 Alpha1 installed from jar

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-19473 Central can't load Discovery catalog

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-19627 OpenShift features disable workspace selection

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3411 have installer build actually use M6 p2 product build

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBDS-3208 reorg/refactor directories for consistency across JBT/JBDS

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-17686 get TCF and RSE terminals to coexist without bad UX of multiple terminals

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          There are no Sub-Tasks for this issue.

          Activity

            People

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: