As the current sprint 'devex #185 June 2020' 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.16.0.Final + 12.16.0.GA),
to a future .x release, or LATER.
All unresolved issues for 4.16.0.AM1 + 12.16.0.AM1:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
All *YOUR* unresolved issues for 4.16.0.AM1 + 12.16.0.AM1:
https:…
[View More]//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 #186 July 2020'.
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)
[View Less]
Here is a proposal for change(s) to the JBoss Tools / Red Hat CodeReady Studio / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.16.0.AM1
devstudio 12.16.0.AM1
jbt/ds TPs 4.16.0.AM1-SNAPSHOT
central TPs 4.16.0.AM1-SNAPSHOT
Detail / Summary:
Updated following dependencies:
reddeer 3.0.0
docker 4.7.0.202006092019
jgit 5.8.0.202006091008-r
simrel 20200617-1000-Simrel.2020-06
m2e 1.16.0.20200610-1735
orbit R20200529191137
Related JIRA(s):
https://issues.redhat.com/browse/…
[View More]JBIDE-27290
Pull Request(s):
https://github.com/jbosstools/jbosstools-target-platforms/pull/358https://github.com/jbosstools/jbosstools-build-ci/pull/188
p2diff Report(s):
attached to JIRA
----------
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.16.0.AM1-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.16.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
[View Less]
Hello,
It's a reminder that JBossTools 4.16.0.AM1 / CodeReady Studio 12.16.0.AM1
release in the way.
The TP will been frozen tomorrow Tuesday, EOD UTC and all repos will
be frozen Wednesday EOD UTC.
If you have pending PRs, please check them and make sure they are merged
before the code freeze.
Thank you,
Regards,
--
Stéphane Bouchet
Senior Software Engineer, R&D
Red Hat <https://www.redhat.com/>
<https://www.redhat.com/>