September 2024 - wildfly-dev - Jboss List Archives

by Brian Stansberry

We've got a lot ofJIRAs with 'Critical' priority that have been inactive for a long time. I think we should define 'Critical' as roughly "important enough that we need to work on it soon." At some point if something goes unaddressed long enough that's a sign that it's not important enough to be called critical. I propose doing the following: for any Critical WFLY or WFCORE that was opened > 12 months ago and hasn't shown signs of activity since the WF 32 release, I'll leave a comment saying I plan to downgrade it to Major unless the assignee says they plan to deal with it for the WF 34 cycle. And then a couple weeks later downgrade issues. Similarly, for issues with Fix Version 33.0.0.Final that have been rolling from release to release since WF 31 or earlier, when I release 33 I intend to remove the Fix Version instead of rolling it to 34. WDYT? Best regards, -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His

2 months, 3 weeks

3
12
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

2 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

2 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - elytron-web:master

by thofman＠redhat.com

2 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

2 months, 3 weeks

1
0
0 / 0

Feature Team Formation - [Community] [WFCORE-6830] New attributes on the HTTP Management Interface to configure resource constraints.

by Darran Lofthouse

Hello everyone, I am looking for some volunteers who may be available to help me complete the feature team for this proposal: https://github.com/wildfly/wildfly-proposals/pull/595 As described in the proposal the underlying implementation already exists in WildFly Core and is configured using system properties, this enhancement is to add new attributes to the HTTP management interface at the community stability level. As this is about adding attributes to the management interface for existing functionality it feels like SME wise this may be more about the management interface management model but as a community level feature this also needs a third party perspective. Please let me know if you have any questions or if you are volunteering to join the feature team. -- Darran Lofthouse Red Hat <https://www.redhat.com/> darran.lofthouse(a)jboss.com <https://www.redhat.com/>

2 months, 3 weeks

2
1
0 / 0

Promotion from wildfly-extras?

by Brian Stansberry

The discussion Flavia started about the process around the proposed wildfly-ai-feature-pack[1] got me thinking a bit about how we are using wildfly-extras. The basic concept when we started that was it would be used for: 1) Projects that are incubating. 2) Some vague idea around the notion of things that are out of the mainstream for the overall WildFly project. Perhaps something meant for more specialized use, etc. But now we have some things in there that are not incubating and are very mainstream. In particular, WildFly Glow now maintains knowledge of a set of feature packs it uses when making suggestions, and that includes feature packs housed in wildfly-extras. Is it time to move some things to the main 'wildfly' organization, particularly these feature packs Glow uses? Going forward should that be a criteria for inclusion in Glow recommendations? (At least that we have decided something is ready to be moved. The actual move is just a detail.) I don't know if cleaning this up would provide any greater freedom to experiment with things in wildfly-extras without following the feature dev process. Probably not, at least not for things that the WildFly project in general will be promoting. [1] https://wildfly.zulipchat.com/#narrow/stream/174184-wildfly-developers/to... Best regards, -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His

3 months

1
0
0 / 0

Possible component upgrades report - wildfly-elytron:1.x

by thofman＠redhat.com

3 months

1
0
0 / 0

Possible component upgrades report - elytron-web:master

by thofman＠redhat.com

3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev September 2024