I think we can really see some process improvements as well! I've
been taking a look at github actions or bots that could perform
cherry-picks (if conflict-free, of course) or back-porting PRs, and
I've found a few interesting projects *close* to it, like
https://github.com/gorillio/github-action-
On fr 22 sep. 2023 18:40, Ryan Skraba wrote:
> Back to this topic :D After a couple of extra releases on the
> branch-1.11, how do we feel about supporting two major releases? Have
> committers found it a pain in the butt to cherry-pick?
>
Not a pain, but my process is not as clean as merging
od idea to include -- if we can't
> > > > meet that goal, there's probably a pretty good reason (like a
> > > > hopelessly broken major release that should be abandoned).
> > > >
> > > > I'll give this a bit more time to think about a
gt; >
> > > All my best, Ryan
> > >
> > >
> > > [1]: https://issues.apache.org/jira/browse/AVRO-2687 "Semantic
> > versioning"
> > > [2]: https://lists.apache.org/thread/6ppm20v5602w9nqz0nk5qz7mxnnt2tsw
> > > "[DISCUSS
che.org/thread/6ppm20v5602w9nqz0nk5qz7mxnnt2tsw
> > "[DISCUSS] version numbers and where changes should land"
> > [3]: https://lists.apache.org/thread/2rfnszd4dk36jxynpj382b1717gbyv1y
> > "Release language modules separately"
> > [4]: https://lists.apache.org/
[2]: https://lists.apache.org/thread/6ppm20v5602w9nqz0nk5qz7mxnnt2tsw
> > "[DISCUSS] version numbers and where changes should land"
> > [3]: https://lists.apache.org/thread/2rfnszd4dk36jxynpj382b1717gbyv1y
> > "Release language modules separately"
> > [4]: https:
1y
> "Release language modules separately"
> [4]: https://lists.apache.org/thread/rybf7vb514mtkr7swfld7b06g1kb2r3t
> "[DISCUSS] Releases, versioning and lifecycle"
> [5]: https://lists.apache.org/thread/wq2k9lrz6g79j83t2ojwpvsh4zor4qfg
> "[[DISCUSS] Releas
j382b1717gbyv1y
"Release language modules separately"
[4]: https://lists.apache.org/thread/rybf7vb514mtkr7swfld7b06g1kb2r3t
"[DISCUSS] Releases, versioning and lifecycle"
[5]: https://lists.apache.org/thread/wq2k9lrz6g79j83t2ojwpvsh4zor4qfg
"[[DISCUSS] Release maintenan
I like Christophe's proposal !
On Tue, Jul 18, 2023 at 11:52 AM Christophe Le Saëc
wrote:
> Hello
> I find this proposal relevant.
>
> to clarify :
>
> > From 1.12.0 on, I'd like to propose maintaining *two* major versions
> > (i.e. 1.12.x and 1.11.x). That would allow us to deprecate and modif
Hello
I find this proposal relevant.
to clarify :
> From 1.12.0 on, I'd like to propose maintaining *two* major versions
> (i.e. 1.12.x and 1.11.x). That would allow us to deprecate and modify
> APIs and give developers one whole major release to switch.
this means to maintain 3 branches (1.13.
Hello! There's a number of outstanding questions and discussions
about releases, maintenance, lifecycle :D I thought it might be
productive to make a goal to work towards.
Specifically, I couldn't point to a policy about this question being
asked on the user@ mailing list: when do we stop mainta
11 matches
Mail list logo
