Hi everyone, Update on this: - Made some docs about the contribution and small changes on README.md - I was investing some time reading the Apache release docs and found out I was missing some steps. - I was recommended to use the maven-release-plugin, and will try it later today :)
I give more updates about it soon! Em sex., 16 de jun. de 2023 às 17:21, Kaustubh Beedkar <[email protected]> escreveu: > +1 on that. > > Best, > Kaustubh > > > > On Fri, Jun 16, 2023, 21:10 Zoi Kaoudi <[email protected]> wrote: > > > No objections from me either. Please go ahead and thanks a lot for the > > efforts :) > > > > Best > > -- > > Zoi > > > > Στις Παρασκευή 16 Ιουνίου 2023 στις 12:44:18 μ.μ. CEST, ο χρήστης > > Alexander Alten-Lorenz <[email protected]> έγραψε: > > > > Hey Glaucia, > > > > +1 > > > > Thank you, > > —Alex > > > > Sent from my iPhone > > > > > On 16. Jun 2023, at 11:27, Gláucia Esppenchutz <[email protected]> > > wrote: > > > > > > > > > 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. > > > > > > > > > > > > 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. > > > > > > Let me know what you think, and if everyone approves, I will do it > > immediately. > > > > > > Glaucia > > > > -- > > 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
