12:05 p.m.
On Wed, Mar 2, 2022 at 5:08 PM Brian Stansberry <brian.stansberry(a)redhat.com>
wrote:
On Wed, Mar 2, 2022 at 10:50 AM Brian Stansberry <
brian.stansberry(a)redhat.com> wrote:
> As of last week there were no milestone releases for the EE 10 specs
> listed at [1] available in maven central. It's not clear when public
> releases of some of these specs might be possible. I've directly addressed
> the WFLY component leads for the JIRA components that integrate those
> because I'd like to get answers to 3 questions:
>
> 1) Would near term (say next couple weeks) production of a -jbossorg
> variant of a milestone of a spec be useful to you? E.g. unblock other
> work. Probably this could be done by forking the official spec branch into
> our existing JBoss fork repos and publishing a -jbossorg variant of
> an existing tag.
>
It might be worth thinking about how this will look and the flows in git
for this.
We probably need to keep the option open that the module we are forking is
not final so subject to change so we may need subsequent jbossorg releases.
Where we fork a maven project it sounds like it will be two steps to tag,
the first being the migration to add jboss-parent as the parent so we
inherit the configuration to publish to nexus. Secondly would be the
version change to add the jbossorg suffix.
Where we need to sync from upstream maybe it would be sufficient to use
"git merge" to pull in the upstream changes, add another commit for our
next jbossorg version and tag again?
Or we could create a new branch each time we need to tag, fork from
upstream, apply the two changes, tag.
> 2) If not useful near term, an info on when the lack of a public API
> milestone would be a problem for you EE 10 work would be useful.
>
> 3) If useful, could you help?
>
> I'll create a google sheet to record input.
>
https://docs.google.com/spreadsheets/d/1ql5hpsqs5ZjawErhyVQX8idigFfm0uZZx...
Anyone can read that; if you want to write to it please send me your
google account privately. Or you can give input via this thread and I'll
add it.
>
> Note that I'm not talking about using these releases for the long term;
> it's just about avoiding needing to use staging repos for WF 27 development
> while we wait for releases in maven central. Obviously there is a
> cost/benefit tradeoff here, hence the request for input.
>
> [1]
>
> Authentication
>
> Concurrency
>
> Connectors
>
> Enterprise Java Beans (no biggie; just a micro)
>
> JSON Binding
>
> JSON Processing
>
> Messaging
>
> RESTFul Webservices
>
> Server Pages
>
> Servlet
>
> Standard Tag Library
>
> Websocket
>
> Best regards,
> Brian
>
--
Brian Stansberry
Principal Architect, Red Hat JBoss EAP
He/Him/His
_______________________________________________
wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s