Yes, this was the proposal for 2.0. The topic was discussed last year in this thread - https://lists.apache.org/thread/8382s6v1x61scn3hvscyrhknfcww9g2t. There didn’t seem to be much disagreement, just questions.
Ralph > On Feb 6, 2023, at 12:13 AM, Bessenyei Balázs Donát <bes...@apache.org> wrote: > > I vaguely remember this topic from before and I think there was some > proposal regarding releases. Where did we end up on that? > > > Donat > > On Fri, Feb 3, 2023 at 6:54 AM Ralph Goers <ralph.go...@dslextreme.com > <mailto:ralph.go...@dslextreme.com>> wrote: >> >> These have been failing for quite a while now. Last I checked they were >> running out of disk space for logs. I see that the version of CodeQL is also >> out of support. >> >> This has me back bringing up my intention to split Flume into multiple >> project repos. We have a few modules that really can’t be supported so we >> should move them out of the main build. By splitting up the project we will >> also make the build faster and the logs smaller. >> >> Any objections to doing this? >> >> Ralph >> >> >>> On Feb 2, 2023, at 5:33 PM, Ralph Goers <notificati...@github.com> wrote: >>> >>> >>> >>> [apache/flume] CodeQL workflow run >>> >>> >>> >>> CodeQL: Some jobs were not successful >>> >>> View workflow run <https://github.com/apache/flume/actions/runs/4079911629> >>> >>> >>> CodeQL / Analyze (java) >>> Failed in 4 minutes and 1 second >>> 4 <https://github.com/apache/flume/actions/runs/4079911629> >>> >>> CodeQL / Analyze (python) >>> Succeeded in 3 minutes and 31 seconds >>> 4 <https://github.com/apache/flume/actions/runs/4079911629> >>> >>> >>> >>> — >>> You are receiving this because you are subscribed to this thread. >>> Manage your GitHub Actions notifications >>> <https://github.com/settings/notifications> >>> >>> GitHub, Inc. ・88 Colin P Kelly Jr Street ・San Francisco, CA 94107
