Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1008494 - WildFly 8
Summary: WildFly 8
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Goldmann
QA Contact:
URL:
Whiteboard:
Depends On: 983981 992169 995045
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-16 13:28 UTC by Jaroslav Reznik
Modified: 2013-10-11 09:20 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-11 09:20:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Reznik 2013-09-16 13:28:16 UTC
This is a tracking bug for Change: WildFly 8
For more details, see: https://fedoraproject.org/wiki/Changes/WildFly8

WildFly 8 is the next version of the application server previously known as JBoss Application Server. With the version 8 it makes it possible to run your Java EE 7 applications and much more!

Comment 1 Jaroslav Reznik 2013-10-11 08:45:11 UTC
This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].

All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.

As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be 
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).

[1] https://fedoraproject.org/wiki/Releases/20/Schedule

Comment 2 Marek Goldmann 2013-10-11 09:20:12 UTC
WildFly 8 is now available in Fedora 20.


Note You need to log in before you can comment on or make changes to this bug.