[
https://issues.jboss.org/browse/JBIDE-20960?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-20960:
------------------------------------
{quote}
(2015-10-15 16:26:26) gastaldi: nickboldt, for JBIDE-20960 issues, it would be nice to
have the "Due Date" also set
(2015-10-15 16:26:33) jbossbot: jira [JBIDE-20960] For JBIDE 4.3.1.Beta1: Prepare for
future Beta1 [Forge] [Open (Unresolved) Sub-task, Blocker, George Gastaldi]
https://issues.jboss.org/browse/JBIDE-20960
(2015-10-15 16:26:49) gastaldi: so we can know for how long we can postpone it :)
(2015-10-15 16:27:15) gastaldi: jk, this is useful so we can prioritize over other
issues
(2015-10-15 16:27:59) gastaldi left the room (quit: Client Quit).{quote}
So far I see no commits in
https://github.com/jbosstools/jbosstools-forge/commits/jbosstools-4.3.x so there's no
urgency to apply the PR, unless you KNOW you plan to do work in 4.3.x branch.
If you have maintenance plans &/or outstanding bugs to fix, then the due date is ASAP
so that your builds in 4.3.x are using the correct version of parent pom and are correctly
upversioned.
For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Forge]
-------------------------------------------------------
Key: JBIDE-20960
URL:
https://issues.jboss.org/browse/JBIDE-20960
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: forge
Reporter: Nick Boldt
Assignee: George Gastaldi
Priority: Blocker
Labels: task
Fix For: 4.3.1.Beta1
For JBIDE 4.3.1.Beta1 [Forge]: Please perform the following tasks:
If you expect to be doing 4.3.x maintenance work in your component:
1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins
have been [properly
upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to
4.3.1 (if planning minor changes).
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version
-DnewVersion=4.3.1-SNAPSHOT
{code}
1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg.,
4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your
*{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is
just a reminder.)
2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent
pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta1-SNAPSHOT</version>
</parent>
{code}
2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server)
please ensure you have bumped that file too, and that it refers to the correct parent pom
version you used above.
3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your
tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
{code}
mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
{code}
4. Close (do not resolve) this JIRA when done.
If, on the other hand, you do NOT expect to be doing maintenance in your component,
please let Nick know via @-mention in this JIRA so he can pull a stable release of your
component to use in future 4.3.x builds INSTEAD of including new CI builds.
[Search for all task
JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...],
or [Search for Forge task
JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)