Hi everyone, I was revisiting the good practices of releases and want to align with you if it is the same thing Apache recommends because looking at the Apache Release pages focuses on the artifacts uploaded on the Apache websites.
[image: image.png] The idea is the *release/release-tag* uses the *development *branch to select the PRs or commits to create the release and merge it into the *main* . If we use this good practice, we need to avoid merging things on *main* branch and only merge PRs into *develop*. (Sorry if it is a noob comment! This is the first time I have done an RM, but I am enjoying it a lot :) ) If everyone agrees on it, I can add this a note on the Contributing docs or create a CONTRIBUTE.MD file with clear instructions. Plus, I need the write access to the repo to create the release tag. Could someone help me with this? Then @Zoi will take care of the Apache side Let me know what you think! Glaucia Em ter., 30 de mai. de 2023 às 21:17, Gláucia Esppenchutz < [email protected]> escreveu: > Hi everyone! > I had some personal matters to solve last weekend and at the beginning of > this week and couldn't do anything about the release. > I will work on it today. > > @Zoi Kaoudi <[email protected]> do you have any time this Thursday or > Friday? sorry for the short notice! > > Glaucia > > Em qua., 24 de mai. de 2023 às 09:40, Gláucia Esppenchutz < > [email protected]> escreveu: > >> hi team, >> >> @Zoi Kaoudi <[email protected]> Perfect! :) >> >> Em ter., 23 de mai. de 2023 às 14:04, Zoi Kaoudi <[email protected]> >> escreveu: >> >>> Hi Glaucia, >>> sure we can arrange a call next week if you want. I could do next >>> Wednesday. >>> >>> >>> For the release please remove also the PR #315.In other words, we >>> exclude PR #315 and #311. >>> >>> And for the version we agree to choose 1.0. >>> If someone has an objection please let us know. >>> >>> Best >>> -- >>> Zoi >>> >>> Στις Δευτέρα 22 Μαΐου 2023 στις 03:44:44 μ.μ. CEST, ο χρήστης >>> Gláucia Esppenchutz <[email protected]> έγραψε: >>> >>> Hi team, >>> >>> Nice! I will work on the Github part and let @Zoi Kaoudi >>> <[email protected]> aware >>> when I start and finish it. >>> @Zoi, we can arrange a call and do it together for the next step >>> (uploading the artifacts to Apache) if you want :) >>> >>> >>> >>> Em qui., 18 de mai. de 2023 às 19:55, jorge Arnulfo Quiané Ruiz < >>> [email protected]> escreveu: >>> >>> > This is great! Thank glaucia and zoi. >>> > >>> > The plan sounds great. For the versioning, I am for 1.0 as we already a >>> > stable api and the sql is adding up. IMHO we are ready to go for 1.0… >>> we >>> > should increase our test coverage but as there is no standard to decide >>> > when we go for 1.0 and the rule of thumb is to have 1.0 whenever you >>> have >>> > the core api, I believe we deserve the 1.0 >>> > >>> > So +1 for 1.0 >>> > >>> > — >>> > Jorge >>> > >>> > On Wed, 17 May 2023 at 1:23 PM Alexander Alten <[email protected]> >>> wrote: >>> > >>> > > Heya, >>> > > >>> > > Inline :) >>> > > >>> > > Thank you, >>> > > —Alex >>> > > >>> > > > On 17. May 2023, at 13:01, Gláucia Esppenchutz <[email protected] >>> > >>> > > wrote: >>> > > > >>> > > > Hi team, >>> > > > >>> > > > Me and Zoi had a meeting today to plan the next release, and since >>> it >>> > is >>> > > > the first time we both do this for Apache some questions poped. >>> > > > Just to ensure we are on the same page, here are the steps we are >>> > > planning >>> > > > to do and the related questions: >>> > > > >>> > > > - Create the release branch on github (release/v0.6.X) >>> > > > >>> > > > - Q: what would be the next tag? We saw the last created was >>> > > v.0.6.1-alpha, >>> > > > then would the release be v0.6.2 or v0.7 based on the semantic >>> > > versioning? >>> > > > - Semantic versioning for reference: >>> > > >>> > >>> https://www.google.com/url?q=https://semver.org/&source=gmail-imap&ust=1684926082000000&usg=AOvVaw1Xj_KjOYFjip98yUdl35QG >>> > > > >>> > > > >>> > > >>> > > Let’s vote on that, I propose 0.7 or even 1.0 since we have SQL >>> enabled, >>> > > which brings us much closer to a cross-platform data processing >>> engine. >>> > > >>> > > > - Remove the PR #311 using the rebase command and cherr picking >>> > > > >>> > > > - Generate the github artifacts >>> > > > - Should it be signed using any encrypting method? >>> > > > >>> > > > >>> > > > - Ensuring the disclaimers are there >>> > > > >>> > > > - >>> > > >>> > >>> https://www.google.com/url?q=https://incubator.apache.org/guides/releasemanagement.html&source=gmail-imap&ust=1684926082000000&usg=AOvVaw0BQTld3_xJC3jzUyAzSiPq >>> > > > >>> > > > >>> > > > - Signing release for apache artifacts upload: >>> > > > >>> > > > - include the INCUBATOR on the name >>> > > > - We need to add a signature to the artifact ( >>> > > > >>> > > >>> > >>> https://www.google.com/url?q=https://www.apache.org/legal/release-policy.html&source=gmail-imap&ust=1684926082000000&usg=AOvVaw0Wwntq-9H-pbicy1zJmszQ >>> > ). >>> > > Can it be me doing or >>> > > > only a apache member? >>> > > > - Q: Signing the artifact using the MD5 or SSHA cryptography ? Saw >>> some >>> > > > instructions here: >>> > > >>> > >>> https://www.google.com/url?q=https://infra.apache.org/release-publishing.html%23valid&source=gmail-imap&ust=1684926082000000&usg=AOvVaw3CxxXNaHJ1lNVIq2cT9fSd >>> > > > >>> > > > >>> > > >>> > > SHA should be used, MD5 is deprecated: Signing Releases - Apache >>> > > Infrastructure Website < >>> > > https://infra.apache.org/release-signing.html#basic-facts> >>> > > > - Uploading the artifacts on: >>> > > > >>> > > > - apache >>> > > > - maven >>> > > > - archive the previous release >>> > > > - >>> > > >>> > >>> https://www.google.com/url?q=https://infra.apache.org/release-publishing.html%23distribution&source=gmail-imap&ust=1684926082000000&usg=AOvVaw2ziQf7J8xL82vbhhBJRW9o >>> > > > >>> > > > >>> > > > >>> > > > Once we cover all this, we will proceed with the release :) >>> > > > I can do all the part of github and generating the artifacts, but >>> Zoi >>> > > will >>> > > > be the one to upload it to apache. >>> > > > >>> > > > Cheers,! >>> > > > >>> > > > >>> > > > Em qui., 11 de mai. de 2023 às 11:02, Gláucia Esppenchutz < >>> > > > [email protected] <mailto:[email protected]>> escreveu: >>> > > > >>> > > >> Hi Zoid! >>> > > >> >>> > > >> Sounds perfect to me. Since we are almost at the end of the week >>> and >>> > > >> tomorrow I will be on full meetings, what about next Monday? Let >>> me >>> > know >>> > > >> your timezone so we schedule the call :) >>> > > >> >>> > > >> Cheers! >>> > > >> >>> > > >> Em qui., 11 de mai. de 2023 às 07:23, Zoi Kaoudi >>> > > <[email protected]> >>> > > >> escreveu: >>> > > >> >>> > > >>> I can work closely with Glaucia to make the release.@Glaucia: >>> how >>> > does >>> > > >>> this sound? Shall we briefly meet to arrange the next steps for >>> the >>> > > release? >>> > > >>> Best >>> > > >>> -- >>> > > >>> Zoi >>> > > >>> >>> > > >>> Στις Τετάρτη 10 Μαΐου 2023 στις 03:32:50 μ.μ. CEST, ο χρήστης >>> > > >>> Alexander Alten <[email protected]> έγραψε: >>> > > >>> >>> > > >>> I read in the incubator site that the RM not necessary needs to >>> be a >>> > > >>> committer, at least it’s not clearly stated. But Calvin is right, >>> > > >>> permissions could be problem. But what if Glaucia builds the >>> release >>> > > and a >>> > > >>> PPMC releases it? The RM is the person who overlook the release >>> and >>> > > makes >>> > > >>> sure that everything is right. Or am I’m wrong here? >>> > > >>> >>> > > >>> —Alex >>> > > >>> >>> > > >>>> On 10. May 2023, at 14:41, Jorge Arnulfo Quiané Ruiz < >>> > > >>> [email protected]> wrote: >>> > > >>>> >>> > > >>>> I am for the latter so that we can improve and further test the >>> > > >>> monitoring feature >>> > > >>>> >>> > > >>>> — >>> > > >>>> Jorge >>> > > >>>> >>> > > >>>>> On 10 May 2023, at 13.25, Zoi Kaoudi <[email protected] >>> > > >>> <mailto:[email protected]>> wrote: >>> > > >>>>> >>> > > >>>>> I guess we do not need an official voting for Glaucia being an >>> RM. >>> > If >>> > > >>> someone knows/believes otherwise, please let us know. >>> > > >>>>> >>> > > >>>>> Just one question for the release: Do we release the latest >>> version >>> > > we >>> > > >>> have in the repo that includes the commit with the monitoring >>> part or >>> > > we >>> > > >>> better skip this one to have more commits on monitoring and >>> include >>> > > them in >>> > > >>> a future release?I am in favor of the latter. >>> > > >>>>> Best >>> > > >>>>> -- >>> > > >>>>> Zoi >>> > > >>>>> >>> > > >>>>> Στις Τρίτη 9 Μαΐου 2023 στις 09:24:58 μ.μ. CEST, ο χρήστης >>> Gláucia >>> > > >>> Esppenchutz <[email protected]> έγραψε: >>> > > >>>>> >>> > > >>>>> Hi team, >>> > > >>>>> >>> > > >>>>> Sure. >>> > > >>>>> Should we make a official voting if I can be the RM? >>> > > >>>>> Otherwise, I can do it tomorrow and we have two business days >>> to >>> > > >>> observe >>> > > >>>>> the application. >>> > > >>>>> >>> > > >>>>> Em ter., 9/05/2023 às 19:45, jorge Arnulfo Quiané Ruiz < >>> > > >>> [email protected]> >>> > > >>>>> escreveu: >>> > > >>>>> >>> > > >>>>>> +1 for a release asap, including PR #318 :p >>> > > >>>>>> >>> > > >>>>>> On Tue, 9 May 2023 at 8:43 PM Kristian Reitzel < >>> > > [email protected]> >>> > > >>>>>> wrote: >>> > > >>>>>> >>> > > >>>>>>> Remember PR #318 which is related to the SQL Api :-) >>> > > >>>>>>> >>> > > >>>>>>> Best, >>> > > >>>>>>> Kristian >>> > > >>>>>>> ________________________________ >>> > > >>>>>>> Fra: Alexander Alten-Lorenz <[email protected]> >>> > > >>>>>>> Sendt: Tuesday, May 9, 2023 7:38:44 PM >>> > > >>>>>>> Til: [email protected] <[email protected]> >>> > > >>>>>>> Emne: Re: next release >>> > > >>>>>>> >>> > > >>>>>>> +1, Zoi, do you mind to start an official vote? >>> > > >>>>>>> >>> > > >>>>>>> Sent from my iPhone >>> > > >>>>>>> >>> > > >>>>>>>> On 9. May 2023, at 19:34, Kaustubh Beedkar < >>> [email protected]> >>> > > >>> wrote: >>> > > >>>>>>>> >>> > > >>>>>>>> +1 >>> > > >>>>>>>> Let me know too, how I can chip in. >>> > > >>>>>>>> >>> > > >>>>>>>> Best, >>> > > >>>>>>>> Kaustubh >>> > > >>>>>>>> >>> > > >>>>>>>>> On Tue, May 9, 2023 at 10:53 PM Zoi Kaoudi >>> > > >>> <[email protected]> >>> > > >>>>>>> wrote: >>> > > >>>>>>>>> >>> > > >>>>>>>>> Hello Wayang people, >>> > > >>>>>>>>> we should start the process for the release and include >>> the SQL >>> > > api >>> > > >>>>>>> part. >>> > > >>>>>>>>> @Glaucia: can you start the process? >>> > > >>>>>>>>> Let me know how I can help. >>> > > >>>>>>>>> Any comments/objections more than welcome :) >>> > > >>>>>>>>> >>> > > >>>>>>>>> Best-- >>> > > >>>>>>>>> Zoi >>> > > >>>>>>> >>> > > >>>>>>> -- >>> > > >>>>>>> databloom AI, Inc. >>> > > >>>>>>> >>> > > >>>>>>> 3401 N. MIAMI AVE. STE 230 >>> > > >>>>>>> 33127 Miami, Florida >>> > > >>>>>>> United States >>> > > >>>>>>> >>> > > >>>>>>> >>> > > >>>>>>> -- Please consider the environment before printing this >>> > > >>>>>>> email -- >>> > > >>>>>>> >>> > > >>>>>>> >>> > > >>>>>>> >>> > > >>>>>>> Disclaimer: >>> > > >>>>>>> The content of this message is confidential. If you >>> > > >>>>>>> have received it by mistake, please inform us by an email >>> reply >>> > and >>> > > >>> then >>> > > >>>>>>> delete the message. It is forbidden to copy, forward, or in >>> any >>> > way >>> > > >>>>>> reveal >>> > > >>>>>>> the contents of this message to anyone. The integrity and >>> > security >>> > > of >>> > > >>>>>> this >>> > > >>>>>>> email cannot be guaranteed over the Internet. Therefore, the >>> > sender >>> > > >>> will >>> > > >>>>>>> not be held liable for any damage caused by the message. >>> > > >>>>>>> >>> > > >>>>>>> >>> > > >>>>>> >>> > > >>>>> -- >>> > > >>>>> Gláucia Esppenchutz >>> > > >>>>> >>> > > >>>>> ----------------------------------------------------- >>> > > >>>>> Twitter: @lyuric19 >>> > > >>>>> Linkedin: >>> > > >>> >>> > > >>> > >>> https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://br.linkedin.com/pub/gl%2525C3%2525A1ucia-esppenchutz/47/81a/312%26source%3Dgmail-imap%26ust%3D1684327371000000%26usg%3DAOvVaw2Etx2nFQBkksHgtamkhGQR&source=gmail-imap&ust=1684926082000000&usg=AOvVaw1Cq7YPdm_jXRy7Rr4LKCqE >>> > > >>> >>> > > >>> >>> > > >>> -- >>> > > >>> databloom AI, Inc. >>> > > >>> >>> > > >>> 3401 N. MIAMI AVE. STE 230 >>> > > >>> 33127 Miami, Florida >>> > > >>> United States >>> > > >>> >>> > > >>> >>> > > >>> -- Please consider the environment before printing this >>> > > >>> email -- >>> > > >>> >>> > > >>> >>> > > >>> >>> > > >>> Disclaimer: >>> > > >>> The content of this message is confidential. If you >>> > > >>> have received it by mistake, please inform us by an email reply >>> and >>> > > then >>> > > >>> delete the message. It is forbidden to copy, forward, or in any >>> way >>> > > >>> reveal >>> > > >>> the contents of this message to anyone. The integrity and >>> security of >>> > > >>> this >>> > > >>> email cannot be guaranteed over the Internet. Therefore, the >>> sender >>> > > will >>> > > >>> not be held liable for any damage caused by the message. >>> > > >>> >>> > > >>> >>> > > >> >>> > > >> >>> > > >> >>> > > >> -- >>> > > >> Gláucia Esppenchutz >>> > > >> >>> > > >> ----------------------------------------------------- >>> > > >> Twitter: @lyuric19 >>> > > >> Linkedin: >>> > > >>> > >>> https://www.google.com/url?q=https://br.linkedin.com/pub/gl%25C3%25A1ucia-esppenchutz/47/81a/312&source=gmail-imap&ust=1684926082000000&usg=AOvVaw1L489x8tkB9Jqoh_PnNYUr >>> > > >> >>> > > > >>> > > > >>> > > > -- >>> > > > Gláucia Esppenchutz >>> > > > >>> > > > ----------------------------------------------------- >>> > > > Twitter: @lyuric19 >>> > > > Linkedin: >>> > > >>> > >>> https://www.google.com/url?q=https://br.linkedin.com/pub/gl%25C3%25A1ucia-esppenchutz/47/81a/312&source=gmail-imap&ust=1684926082000000&usg=AOvVaw1L489x8tkB9Jqoh_PnNYUr >>> > > >>> > > >>> > > -- >>> > > databloom AI, Inc. >>> > > >>> > > 3401 N. MIAMI AVE. STE 230 >>> > > 33127 Miami, Florida >>> > > United States >>> > > >>> > > >>> > > -- Please consider the environment before printing this >>> > > email -- >>> > > >>> > > >>> > > >>> > > Disclaimer: >>> > > The content of this message is confidential. If you >>> > > have received it by mistake, please inform us by an email reply and >>> then >>> > > delete the message. It is forbidden to copy, forward, or in any way >>> > reveal >>> > > the contents of this message to anyone. The integrity and security of >>> > this >>> > > email cannot be guaranteed over the Internet. Therefore, the sender >>> will >>> > > not be held liable for any damage caused by the message. >>> > > >>> > > >>> > >>> >>> >>> -- >>> Gláucia Esppenchutz >>> >>> ----------------------------------------------------- >>> Twitter: @lyuric19 >>> Linkedin: https://br.linkedin.com/pub/gláucia-esppenchutz/47/81a/312 >>> >> >> >> >> -- >> Gláucia Esppenchutz >> >> ----------------------------------------------------- >> Twitter: @lyuric19 >> Linkedin: https://br.linkedin.com/pub/gláucia-esppenchutz/47/81a/312 >> > > > -- > Gláucia Esppenchutz > > ----------------------------------------------------- > Twitter: @lyuric19 > Linkedin: https://br.linkedin.com/pub/gláucia-esppenchutz/47/81a/312 > -- Gláucia Esppenchutz ----------------------------------------------------- Twitter: @lyuric19 Linkedin: https://br.linkedin.com/pub/gláucia-esppenchutz/47/81a/312
