Thanks for working on this.
Chris gave some guidelines [2] for the release process.
Maybe the plc4x check-list [1] is helpful?
[1] https://plc4x.apache.org/developers/release/release.html
[2]
The release itself should be the normal Maven release process … you can see in
the plc4x release
Okay, some updates on my progress with BlazeDS.
- I made the necessary changes to remove the vulnerable xalan dependency.
- I looked at the proxy module issue, where we need to replace the obsolete
commons-httpclient 3.x with its successor, httpcomponents-httpclient 4.x. It
seems to be
You may want to take the chance to rename the master branch to "main" or
"production" because "...master, is offensive to some people..." [1]
Olaf
[1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/
-Ursprüngliche Nachricht-
Von: Josh Tynjala
Gesendet: Montag, 9. Januar
I ended up creating an Infra ticket for this:
https://issues.apache.org/jira/browse/INFRA-24073
- Josh
On 2023/01/06 20:09:15 Josh Tynjala wrote:
> I see that Royale's repos are defaulting to the develop on Github, but
> Flex's repos are defaulting to master. I'd like to change Flex's repos to
