ACTION REQUIRED: JBoss Tools + Developer Studio triage time
by jmaury@redhat.com
As the current sprint 'devex #163 March 2019' draws to a close, it is time
to review your unresolved issues!
Some may be done (or will be done soon), but the JIRA(s) need resolution.
Others may need to be pushed to the next milestone (4.12.0.AM1 + 12.12.0.AM1),
to a future .x release, or LATER.
All unresolved issues for 4.11.0.Final + 12.11.0.GA:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
All *YOUR* unresolved issues for 4.11.0.Final + 12.11.0.GA:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
Once created, you can also begin scheduling your work for the upcoming
sprint, 'devex #164 April 2019'.
Triage tips:
* blocker/critical issues: make these your priority work for the next sprint:
move to next version & assign to the next sprint
* other issues that WILL be done in the next sprint:
move to next version & assign to the forthcoming sprint, but lower down
* non-blocker & non-critical issues not for the next sprint:
move to .x (or LATER)
5 years, 8 months
Proposed 4.11.0.Final-SNAPSHOT target platform change(s): m2e; 1.11.0.20190220-2119
by jmaury@redhat.com
Here is a proposal for change(s) to the JBoss Tools / Red Hat Developer Studio / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.11.0.Final
devstudio 12.11.0.GA
jbt/ds TPs 4.11.0.Final-SNAPSHOT
central TPs 4.11.0.Final-SNAPSHOT
Detail / Summary:
m2e;1.11.0.20190220-2119
Related JIRA(s):
https://issues.jboss.org/browse/JBIDE-26565
Pull Request(s):
(already merged - see related JIRA(s))
p2diff Report(s):
(will attach to JIRA when available)
----------
Please review the above changes, as they have been applied and are building today.
Once the target platform is built, jobs and parent pom will be updated to point
TARGET_PLATFORM_VERSION_MAX at the new version, 4.11.0.Final-SNAPSHOT.
You can use the following to build & test the target platforms locally against
your component(s).
Build target-platform:
cd /path/to/jbosstools-target-platforms
git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD
# or, using hub for git
git checkout <pull-request-URL>
mvn clean install -f jbosstools/multiple/pom.xml
Then, to test the new multiple target platform against your component's build:
cd /path/to/your/jbosstools-component
mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
5 years, 8 months
Proposed 4.11.0.Final-SNAPSHOT target platform change(s): docker; 4.2.0.201903191440
by jmaury@redhat.com
Here is a proposal for change(s) to the JBoss Tools / Red Hat Developer Studio / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.11.0.Final
devstudio 12.11.0.GA
jbt/ds TPs 4.11.0.Final-SNAPSHOT
central TPs 4.11.0.Final-SNAPSHOT
Detail / Summary:
docker;4.2.0.201903191440
Related JIRA(s):
https://issues.jboss.org/browse/JBIDE-26565
Pull Request(s):
(already merged - see related JIRA(s))
p2diff Report(s):
(will attach to JIRA when available)
----------
Please review the above changes, as they have been applied and are building today.
Once the target platform is built, jobs and parent pom will be updated to point
TARGET_PLATFORM_VERSION_MAX at the new version, 4.11.0.Final-SNAPSHOT.
You can use the following to build & test the target platforms locally against
your component(s).
Build target-platform:
cd /path/to/jbosstools-target-platforms
git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD
# or, using hub for git
git checkout <pull-request-URL>
mvn clean install -f jbosstools/multiple/pom.xml
Then, to test the new multiple target platform against your component's build:
cd /path/to/your/jbosstools-component
mvn clean verify -Dtpc.version=4.11.0.Final-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
5 years, 8 months