Hi Robert Thank you for following up.
We are planning on releasing first release candidate for v2.2 in the next couple of weeks. Best regards, Ashutosh Mestry . Software Engineer ________________________________ From: Robert Yokota <[email protected]> Sent: Tuesday, July 20, 2021 10:13:41 AM To: [email protected] <[email protected]> Subject: Re: Next release - 2.2 or 3.0? Hi, Any update on the 2.2 release? Thanks, Robert On Sat, Jun 12, 2021 at 11:27 AM Madhan Neethiraj <[email protected]> wrote: > Adam, > > 2.2 release will be from branch-2.0. So, any fix/improvement targeted for > 2.2 release must land in branch-2.0. > > That said, all commits generally land in master branch, and then they are > cherry-picked into other relevant branches - like branch-2.0. If it is not > a clean cherry-pick, then the author will need to create branch-specific > patches. > > Hope this helps. > > Madhan > > > On 6/10/21, 8:42 AM, "Adam Bellemare" <[email protected]> wrote: > > Hi Ashutosh > > Thanks for the fast reply! It does provide some clarity. > > I am looking at the branch-2.0, and there are enough differences > between it > and trunk that the PR I am proposing doesn't patch nicely. I am fine > with > making a patch for branch-2.0 if that's where the next release is > coming > from. Alternately, if all releases always come from master branch, > then I > can go spend some time on improving a few parts of the documentation > instead :). > > Please advise accordingly! > > On Thu, Jun 10, 2021 at 11:39 AM Ashutosh Mestry > <[email protected]> wrote: > > > Hi Adam > > > > Thanks for following up. > > > > About releases: We discussed a rough plan in our team meeting last > night. > > We are planning a release in the coming weeks. We will keep the > mailing > > list posted with details. > > > > About your PR: We will be running the patch through our internal > tests to > > ensure that our performance baseline in unaffected. I looked at the > > implementation briefly and it seems to be fine. Right now, I don’t > have any > > comments. Once committed, we will try to get it in the upcoming > outgoing > > release. > > > > Hope this helps! > > > > Best regards, > > > > ~ ashutosh > > Ashutosh Mestry<mailto:[email protected]> . Staff Software > Engineer . > > Cloudera, Inc. > > > > > > From: Adam Bellemare <[email protected]> > > Date: Thursday, June 10, 2021 at 8:13 AM > > To: [email protected] <[email protected]> > > Subject: Next release - 2.2 or 3.0? > > Hi > > > > I'm looking to have my PR (https://github.com/apache/atlas/pull/139) > > released in the next official release. Are there any plans for if > that is > > 2.2 or 3.0? > > > > I take it that I should be committing to branch-2.0 for the next 2.2 > > release, correct? > > > > Thanks > > Adam > > > > >
