+1

On 11/12/20, 11:34 AM, "Owen Nichols" <onich...@vmware.com> wrote:

    +1 Sounds good to me, thanks @Dick for stepping up!

    Let's also start posting Geode release artifacts to GitHub too (as many 
other projects already do).  I've backfilled the last couple releases, check it 
out here: 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Freleases&amp;data=04%7C01%7Cagingade%40vmware.com%7C73a0747375654576a38008d88741ea94%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637408064466196245%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=b73FbcZs9fubwppKVdkDPxb5JrRz98Eu4W9m2OeZoME%3D&amp;reserved=0

    On 11/12/20, 11:01 AM, "Dick Cavender" <di...@vmware.com> wrote:

        It's been two months since the 1.13.0 release and there have been 28 
important fixes on support/1.13 that the community would benefit from. Based on 
this I'd like to propose release of Apache Geode 1.13.1 based on the current 
support/1.13 branch. I'll volunteer to be the release manager for 1.13.1 so 
look forward to an RC1 soon.

        -Dick



Reply via email to