Moving WildFly Elytron to Java 17
by Darran Lofthouse
Now that WildFly Core is built for Java 17 I would like to move WildFly
Elytron to Java 17 as well from our next releases for WildFly (2.7.x +).
Would this cause any issues for other projects that depend on WildFly
Elytron?
It should not affect Undertow as we use the Elytron Web project for
integration, maybe JBoss Remoting but also others with an Elytron
dependency so let me know if this would be an issue for your project.
--
Darran Lofthouse
Red Hat <https://www.redhat.com/>
darran.lofthouse(a)jboss.com
<https://www.redhat.com/>
2 months
[proposal] Generate "javadoc-like" documentation for feature packs
by Jeff Mesnil
Hi,
I’ve created a proposal[1] to generate a documentation archive when a feature pack is created (similar to the javadoc archive that is generated when a Java jar is built by Maven)
I’m looking for a feature team to work on this proposal.
Jean-Francois and Emmanuel already provided some PoC around this idea so I nominated you as SMEs :)
But I’d need another outside perspective to fully form the team.
This RFE does not impact the runtime so stability level is not directly applicable but I aim to do something equivalent to the quality expected by the “community” stability level.
Best regards,
Jeff
[1] https://github.com/wildfly/wildfly-proposals/pull/739
--
Jeff Mesnil
Engineer @ Red Hat
http://jmesnil.net/
3 months, 1 week
WildFly 38 schedule
by Brian Stansberry
Following are the planned dates for the WildFly 38 Beta and Final releases.
Please note that these are a week later than we'd originally discussed.
WildFly 38 Beta
PRs due -- Wed Sep 24
Tag and deploy -- Wed Oct 1
Publish release -- Thu Oct 2
WildFly 38 Final
PRs due -- Wed Oct 8
Tag and deploy -- Wed Oct 15
Publish release -- Thu Oct 16
Note that the PR deadline for things going into 38 Beta via WildFly Core
will be particularly strictly enforced this time, as the team producing the
Beta needs to get things done quickly.
As I mentioned before these are a week later than we initially thought.
Adapting project to the new JBoss Nexus environment, plus plenty of well
deserved vacation time for many, meant the original schedule was too tight,
so we'd rather better serve our users by taking a bit more time.
Best regards,
--
Brian Stansberry
WildFly Project Lead
He/Him/His
3 months, 2 weeks
Agenda for the upcoming WildFly community call
by Jean-Frederic Mesnil
Hi,
Next Thursday, we have our 2nd WildFly community call and I’m looking for topics.
I’ve started to fill the agenda at https://docs.google.com/document/d/1kjaMGFGtL3MPY58UCJMojLlTzl335DUm1L-P9...
As it coincides with the release of WildFly 38 Beta, it’d be a great opportunity to showcase new features coming to WildFly.
If you have a feature that lands in WildFly 38, can I ask you to add an item in the agenda. You can also present/demo it :)
More generally, I’m looking for topics for future meetings. This meeting is an opportunity to reach out to our users and present what we are doing and what is in our pipeline.
Don’t hesitate to add future topics to the “Meeting Suggestions” tab[1]
[1] https://docs.google.com/document/d/1kjaMGFGtL3MPY58UCJMojLlTzl335DUm1L-P9...
--
Jeff Mesnil
Software Engineer
Red Hat JBoss EAP
http://jmesnil.net/
IBM
Unless otherwise stated above:
Compagnie IBM France
Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 664 614 175,50 €
SIRET : 552 118 465 03644 - Code NAF 6203Z
3 months, 3 weeks
Additional mergers for the wildfly/wildfly GitHub repo
by Brian Stansberry
I'm proposing we significantly expand the set of people who have write
permissions to the wildfly/wildfly GitHub repo. The following folks are all
experienced WildFly developers who act as a component lead for components
in the WFLY JIRA project, but they don't have write permissions to the main
server code repository:
Tomasz Adamski
Jean Francois Denise
Emmanuel Hugonnet
Rado Husar
Tom Jenkinson
Jason Lee
Scott Marlow
Eduardo Martins
Brad Maxwell
Matěj Novotny
Richard Opalka
Harald Pehl
Flavia Rainone
Marco Sappe Griot
I think they should all have write perms.
WDYT about this? Please feel free to let me know either here or privately.
I'd like to leave the topic open for discussion for a week and then, if
there is consensus around it, move forward.
Historically, we've had a pretty small set of people with write permissions
to this repository. That made sense in the early days of AS 7 and WildFly
when the scope and structure of the project were changing rapidly. And it
made sense in the years after 2018 when we started releasing quarterly,
which was new, and we added some pretty opaque and hard to understand
processes around feature development.
But those days are long behind us and TBH I think adding more mergers is
long overdue. It's been on my todo list for too long; my apologies for
that! I think these folks have the experience and judgement needed to know
whether pressing the green button is ok or whether it's better to stop and
ask questions or defer to others.
Note: I'm not proposing changing the set of people who rotate in the role
of release coordinator for micro releases. IOW, having write perms to the
repo doesn't mean you have to act as an RC sometimes. Changing the RC
rotation would be a separate discussion.
Best regards,
--
Brian Stansberry
WildFly Project Lead
He/Him/His
3 months, 3 weeks
