> In order to give visibility to our community, I propose to have a regular > pace in Arrow Java releases
I think a best effort regular release is good (at the minimum keeping dependencies current is worth it, looking at the number of recent dependabot PRs) and with the new, actual versioning it communicates the project status well too. Am Mo., 24. Feb. 2025 um 11:46 Uhr schrieb David Li <lidav...@apache.org>: > > This sounds good to me. We may want to start adding other subprojects there > as well? (Nanoarrow, Go, Rust, Julia, ADBC, etc.) > > On Mon, Feb 24, 2025, at 19:02, Jean-Baptiste Onofré wrote: > > Hi folks, > > > > Following the first 18.2.0 release on arrow-java repository, I would > > like to start a discussion about having regular pace on Arrow Java > > releases. > > > > In order to give visibility to our community, I propose to have a > > regular pace in Arrow Java releases: at least one release per quarter. > > > > I propose the following: > > 1. On https://arrow.apache.org/release/ I propose to add a schedule > > table for monorepo and java with the next release data and link to > > corresponding GH issues/milestone (a bit similar to the schedule table > > here https://karaf.apache.org/download.html). > > 2. We clearly add a note that the release date is "at best effort": > > the date and release content can totally change (depending on > > priorities, resources/contributions, ...). > > 3. We keep only the latest releases on this page and introduce an > > archive page (https://arrow.apache.org/archives/) where we will have > > all releases. > > > > Thoughts ? > > > > Regards > > JB
