What is the official procedure to introduce some improvements and/or patches to EAP version

[kristjan273]

I would ask for some clarification on EAP version as we are deciding to move from community version.

I have built 7.2 latest available tag with some patches from wildfly trunk (eq. AS7-6465 ) and some version upgrades on used libs (eq. infinispan, jgroups). So two questions:

- is it possible to patch also EAP source and use it with subscribed support

- or EAP is actually closed source and there is some(none?) procedure to have some changes applied

tnx in advance

[wdfink]

EAP version is a special version based on AS/WildFly. This version is internally tested and might slightly differ to the community version. But you can still download the sources from the download area.

Improvements will be included in the next EAP version, as it need to be tested and approved.

For patches/bugfixes you can request a OneOff patch for your special issue via the CustomerSupportPortal, or download it in the CSP if it is available.

Remember only that patches are approved and supported, if you change the EAP installation (i.e. replace a subsystem library with a community version) you might be unsupported in that special area.

Also you can request a RFE to include enhancements new features etc. after they are aceppted you will get a notice when it will be available.

[kristjan273]

Thank you for the info.

Can you also tell me if there is 'roadmap' with some ETA dates? I am kind of crawling the bugzilla.redhat.com (and I miss JIRA a lot ) but I am unable to find that piece of information?

[jdoyle]

Sorry, we don't publish a public roadmap for EAP.

[henk53]

Aleš Bregar wrote:

Can you also tell me if there is 'roadmap' with some ETA dates? I am kind of crawling the bugzilla.redhat.com (and I miss JIRA a lot ) but I am unable to find that piece of information?

There were also JIRA issues created and maintained for the things that go into the EAP releases, see e.g. the fixed for EAP 6.0

For the upcoming JBoss EAP 6.2 there were 2 issues listed, but they have been migrated to that Red Hat bugzilla. For some time there were both the JIRA issues and the Bugzilla bugs, but on the main JIRA project page for JBoss EAP it now says that it has moved fully: https://issues.jboss.org/browse/JBPAPP6

It's a bit sad IMHO that this has been done. Bugzilla is infinitely harder to navigate than JIRA, and there are tons of issues being created everyday for JBoss AS/Wildfly in JIRA that just as much apply to JBoss EAP. Personally I wonder if this doesn't create an internal tracking nightmare. Do you guys at JBoss really like migrating issues from and to jira/bugzilla all the time, or is it just some unfortunate thing that has to be done? I can't imagine this dual tracking system improves productivity in any way...

EDIT:

Something I didn't noticed before, but looking at e.g. https://issues.jboss.org/browse/JBPAPP6-1281 it looks like there's an integration into place where existing tickets in JIRA are being updated with the changes made in bugzilla.