I'd like to plan and start working on a 2.0 release of commons-logging
with the specific goal of resolving the large  number of out of date,
unsupported, old libraries that this project pulls into so many
dependency trees. There's been some discussion of a 2.0 release in
JIra at https://issues.apache.org/jira/projects/LOGGING/issues/LOGGING-187
but I'd lik to bring this to a wider audience. Specifically my
thoughts are:

1. 2.0 will be technically API incompatible since it will remove all
traces of EOL libraries like log4j 1.x and avalon.
2. It will otherwise be a drop-in replacement for anyone not using
these old libraries. Specifically:
  * Other deprecated methods are not removed.
  * The package name does not change.
  * The group ID and artifact ID do not change.
  * Minimum Java version remains 1.8
3. It can include any recent, API compatible bug fixes and new
features that are available at HEAD, but these are not blockers.

While there are other more incompatible changes that could be made in
a major version bump, I think it's really important to produce a
drop-in replacement that is friendlier to security scanners and
dependency analyzers. I do not want to discourage people from
upgrading for any reason other than they're still using EOL libraries
like log4j 1.x.

1.3.0 was recently released and seems up to date with the last several
years of changes and bugs, so it feels like a good time to make the
break. Anyone who isn't ready to give up their decade+ old loggers can
stay on this release for a while.  However if there's a strong need to
maintain a 1.x branch that could be done too.  Or we could start 2.x
as a separate branch.

If this achieves rough consensus, I can start sending PRs. However,
the final release would require a commons committer or perhaps PMC
member to take over.

Thoughts?

--
Elliotte Rusty Harold
elh...@ibiblio.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to