January 2024 - wildfly-dev - Jboss List Archives

by Brian Stansberry

I'm pleased to announce that WildFly 31.0.0.Final is now available at https://www.wildfly.org/downloads/. There's a lot to be happy about in what we've accomplished in the 31 cycle; I suspect my announcement post at https://www.wildfly.org/news/2024/01/25/WildFly31-Released/ is my longest ever. I think it's great how much we've gotten done outside of the main server code base. Big thanks in particular to: Eduardo Martins -- for driving the huge quickstarts enhancements efforts, and a bunch of other QS improvements. Paul Ferraro -- for the stability level work, and the new WildFly Core 'subsystem' and 'service' modules. Jean Francois Denise and Kabir Khan -- for WildFly Glow. Harald Pehl, Jeff Mesnil, Farah Juma, Ashwin Mehendale, Prarthona Paul, Wolfgang Knauf for the work on Getting Started and the user guides. And to all of you for the many other improvements I'm not mentioning here -- and for making WildFly such a vibrant project. Best regards, Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His

3 months, 2 weeks

2
1
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

3 months, 2 weeks

1
0
0 / 0

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

by thofman＠redhat.com

3 months, 2 weeks

1
0
0 / 0

Possible component upgrades report - elytron-web:master

by thofman＠redhat.com

3 months, 2 weeks

1
0
0 / 0

Possible component upgrades report - wildfly-core:main

by thofman＠redhat.com

3 months, 2 weeks

1
0
0 / 0

Triage of 'Critical' WFLY and WFCORE issues

by Brian Stansberry

Can we do some housekeeping of the open 'Critical' issues in WFCORE and WFLY? 1) Can the assignees and relevant component leads go through them and change the priority for any that aren't truly critical? 2) Simultaneously, we can have a discussion here of what we want 'Critical' to mean going forward. My 2 cents is it needs to have more of a meaning of 'Priority' (which is what the field is), i.e. it gives a clue as to what needs to be worked on next. And less of a meaning of 'subjective importance'. My sense is right now we have a lot of things where 'Critical' means someone thought it was 'Important' but there is no corresponding priority to get it done. At some point that calls into question whether it's truly critical. For 1) above I'm not asking that we have a big discussion and then people can review issues. I'm looking for a quick triage to clean up things where the experts decided 'nah, that's not really critical.' Just try and get rid of some noise so it's easier for new Critical items to stand out. Also, in a preview of coming attractions, I expect later this quarter we'll kick off a more general JIRA housekeeping initiative. This is something that Alessio Soldano suggested last year, and it's sorely needed, but I didn't have time to get anything going. But it's a New Year, and my New Year's Resolution is to tidy this up. Best regards, Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His

3 months, 2 weeks

2
2
0 / 0

Possible component upgrades report - wildfly:main

by thofman＠redhat.com

3 months, 3 weeks

1
0
0 / 0

WildFly GitHub Bot - automatic JIRA issue linking

by Martin Stefanko

Hi all, I want to bring to your attention that we will be deploying a new feature [0] soon that will automate the JIRA issue linking based on the content of your PRs. You can see it in action in the linked video [1]. The PR is still open [2], so if you have any questions or ideas, there is still time to adjust this. P.S. Don't worry about the alien voice in the video of the feature author Rastislav Budinsky, who, except for being an intern in SET, is also a part-time alien, it seems. I told him to land on the ground first before he records screenshare next time :D. Cheers, Martin Stefanko Principal Software Engineer Middleware Runtimes Sustaining Engineering Team Red Hat [0] https://github.com/wildfly/wildfly-github-bot/issues/72 [1] https://drive.google.com/file/d/18EyuJrPhRJoxtMvKe2k1-TiBef3Hi0L1/view?us... [2] https://github.com/wildfly/wildfly-github-bot/pull/108

3 months, 3 weeks

3
2
0 / 0

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

by thofman＠redhat.com

3 months, 3 weeks

1
0
0 / 0

Possible component upgrades report - elytron-web:master

by thofman＠redhat.com

3 months, 3 weeks

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

wildfly-dev January 2024