Hi,
Devstudio QE and Fuse Tooling QE is done with testing.
JBoss Tools 4.15.0.AM <http://0.am/>
1
is ready to be released.
We have found new critical issue for Fuse Tooling:
https://issues.redhat.com/browse/FUSETOOLS-3333. This issue will be fixed
in nightly build and it is not blocking the release of AM1(simple
workaround will be to install fixed Fuse tooling).
Other critical issues are in the sign-off. These issues do not block the
AM1 release, however as we move towards next …
[View More]milestones they will be
considered as blockers.
The sign-off document is here:https://mojo.redhat.com/docs/DOC-1218978
The master branch is no longer frozen.
Thanks,
Josef.
--
Josef Kopriva
Senior Quality Engineer
Red Hat <https://www.redhat.com/>
Purkynova 111
612 00 Brno IM: jkopriva
<https://www.redhat.com/>
[View Less]
As the current sprint 'devex #181 Mar 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.15.0.Final + 12.15.0.GA),
to a future .x release, or LATER.
All unresolved issues for 4.15.0.AM1 + 12.15.0.AM1:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
All *YOUR* unresolved issues for 4.15.0.AM1 + 12.15.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 #182 Apr 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]
Hello,
It's a reminder that JBossTools 4.15.0.AM1 / CodeReady Studio 12.15.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/>
Here is a proposal for change(s) to the JBoss Tools / Red Hat CodeReady Studio / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.15.0.AM1
devstudio 12.15.0.AM1
jbt/ds TPs 4.15.0.AM1-SNAPSHOT
central TPs 4.15.0.AM1-SNAPSHOT
Detail / Summary:
updated:
testng 7.1.1.202003100345
lsp4e 0.14.0
reddeer 2.9.0
docker 4.6.0.202003102154
webtools R-3.17.0-20200306035042
jetty 9.4.27.v20200227
cdt 9.11 ( TM/RSE split )
tm 4.5.200.201901312252
buildship 3.1.3.v20191118-1057
m2e 1.…
[View More]15.0.20200310-1746
cameltooling 1.0.0.202003121347
jgit 5.6.0.201912101111-r
orbit R20200224183213
simrel 20200318-1000-Simrel.2020-03
Related JIRA(s):
https://issues.redhat.com/browse/JBIDE-27089
Pull Request(s):
(already merged - see related JIRA(s))
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.15.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.15.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
[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.15.0.AM1
devstudio 12.15.0.AM1
jbt/ds TPs 4.15.0.AM1-SNAPSHOT
central TPs 4.15.0.AM1-SNAPSHOT
Detail / Summary:
updated:
testng 7.1.1.202003100345
lsp4e 0.14.0
reddeer 2.9.0
docker 4.6.0.202003102154
webtools R-3.17.0-20200306035042
jetty 9.4.27.v20200227
cdt 9.11 ( TM/RSE split )
tm 4.5.200.201901312252
buildship 3.1.3.v20191118-1057
m2e 1.…
[View More]15.0.20200310-1746
cameltooling 1.0.0.202003121347
jgit 5.6.0.201912101111-r
orbit R20200224183213
simrel 20200318-1000-Simrel.2020-03
Related JIRA(s):
https://issues.redhat.com/browse/JBIDE-27089
Pull Request(s):
https://github.com/jbosstools/jbosstools-target-platforms/pull/350
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.15.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.15.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
[View Less]