Hi team,

Sure!
To make sure we are on the same page:
- Do a minor release or wait and release all together in a major?

In my opinion, I think we should do a minor (0.7.0) and a major with the
cleanup Dimitris is doing.
Doing all together I think there will be a lot for just one release, even
if its a major :)

Let me know what you think!

Em qua., 21 de jun. de 2023 às 09:10, Zoi Kaoudi <[email protected]>
escreveu:

> +1 to wait
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Wednesday, June 21, 2023, 09:34, Kaustubh Beedkar <[email protected]>
> wrote:
>
> Thank you Glaucia,
>
> I would also vote for waiting until the code is cleaned up, as this would
> be the first major release.
>
> Best,
> Kaustubh
>
> On Wed, Jun 21, 2023, 12:32 Alexander Alten <[email protected]> wrote:
>
> > Hey Glaucia,
> >
> > Thank you, looks good. One thing, I thing that Dimitris works to clean
> the
> > code and bring it in line with a maven structure?
> > https://github.com/apache/incubator-wayang/issues/283
> >
> > Should we wait until this is finished? Thoughts @all?
> >
> > Best,
> >  —Alex
> >
> > > On 20. Jun 2023, at 22:47, Gláucia Esppenchutz <[email protected]>
> > wrote:
> > >
> > > Hi everyone,
> > >
> > > Can you please review the Release notes attached?
> > > I tried to aggregate everything together, but since I recently joined
> > the team, I may miss something :)
> > >
> > > Thanks!
> > >
> > > Em seg., 19 de jun. de 2023 às 14:48, Alexander Alten <
> [email protected]
> > <mailto:[email protected]>> escreveu:
> > >> Awesome, and merged!
> > >>
> > >> > On 19. Jun 2023, at 15:36, Gláucia Esppenchutz <[email protected]
> > <mailto:[email protected]>> wrote:
> > >> >
> > >> > 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] <mailto:[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] <mailto:[email protected]
> >>
> > έγραψε:
> > >> >>>
> > >> >>> Hey Glaucia,
> > >> >>>
> > >> >>> +1
> > >> >>>
> > >> >>> Thank you,
> > >> >>> —Alex
> > >> >>>
> > >> >>> Sent from my iPhone
> > >> >>>
> > >> >>>> On 16. Jun 2023, at 11:27, Gláucia Esppenchutz <
> > [email protected] <mailto:[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://www.google.com/url?q=https://br.linkedin.com/pub/gl%25C3%25A1ucia-esppenchutz/47/81a/312&source=gmail-imap&ust=1687786661000000&usg=AOvVaw39cpVv1IEfRTOo5BnDA01W
> > <
> >
> 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%3D1687786661000000%26usg%3DAOvVaw39cpVv1IEfRTOo5BnDA01W&source=gmail-imap&ust=1687898858000000&usg=AOvVaw2kCiEoKDPB2Uj8Zqh9Y-jw
> > >
> > >>
> > >>
> > >> --
> > >> 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 <
> >
> https://www.google.com/url?q=https://br.linkedin.com/pub/gl%25C3%25A1ucia-esppenchutz/47/81a/312&source=gmail-imap&ust=1687898858000000&usg=AOvVaw0aHxiuRuKX9kJol8IVdHc3
> > ><release_notes.txt>
> >
> >
> > --
> > 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

Reply via email to