+1 to Bart’s suggestion. Other projects map out a release schedule and release manager for each release. (See e.g. a recent discussion in Calcite [1].)
Having multiple release managers is essential to make the process robust (e.g. if the usual release manager is unavailable at short notice for a security release, or if they inadvertently use an environment only available on their machine). Julian [1] https://lists.apache.org/thread/j847g5q8l2fq90xzr93bx69csj0srmsw > On Mar 19, 2025, at 1:25 AM, Bart Maertens <bartm...@apache.org> wrote: > > Hi Hans, > > Good idea! > Two small sidenotes: > 1) A release in early August might be a bit tricky with the summer holidays > for a mostly European project team. > 2) Since you're the only person who has created Apache Hop releases so far > (big thanks for that!), we should consider delegating the release process > to other PMC members. > > Bart > > On Wed, Mar 19, 2025 at 8:37 AM Francois Papon <fpa...@apache.org> wrote: > >> Hi, >> >> It's a very good thing to propose a release schedule and quarterly make >> sense to be easily doable. >> >> +1 >> >> regards, >> >> François >> >> Le 18/03/2025 à 17:03, Hans Van Akelyen a écrit : >>> Hi All, >>> >>> We seem to have never really discussed a release schedule and have been >> "winging it" a bit. >>> For the past years we have done somewhat of a bi-monthly release >> schedule but maybe we should vote a fixed yearly schedule. >>> Advantage will be that our releases are more predictable and planned for >> everyone. >>> >>> My proposal would be to go to quarterly releases but shift them 1 month >> on the actual quarter to stay away from the holidays. >>> so my schedule proposal would be: >>> >>> • cutoff 31/01, release early February >>> • cutoff 30/04, release early May >>> • cutoff 31/07, release early August >>> • cutoff 31/10, release early November >>> >>> For the current release I would keep the existing schedule (cutoff >> 31/03) and then switch to the proposed dates. >>> >>> Let me know what you think, >>> >>> Cheers, >>> Hans >>> >>
