-
1. Re: What is the official procedure to introduce some improvements and/or patches to EAP version
wdfink Jul 1, 2013 11:13 AM (in response to kristjan273)1 of 1 people found this helpfulEAP 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.
-
2. Re: What is the official procedure to introduce some improvements and/or patches to EAP version
kristjan273 Jul 1, 2013 6:06 PM (in response to wdfink)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?
-
3. Re: What is the official procedure to introduce some improvements and/or patches to EAP version
jdoyle Jul 8, 2013 4:28 PM (in response to kristjan273)Sorry, we don't publish a public roadmap for EAP.
-
4. Re: What is the official procedure to introduce some improvements and/or patches to EAP version
henk53 Jul 8, 2013 6:53 PM (in response to kristjan273)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.