I think that it's probably good to go through the last incubating release before we do the graduation to go through the clean-up and final checks from IPMC.
On the other hand, I don't want to block the graduation process for creating a new release if there is no special requirement for that. The release process can take quite a while. How other ppl think about creating the release before/after graduation? Best, Seunghyun On Mon, May 10, 2021 at 12:25 PM kishore g <g.kish...@gmail.com> wrote: > > Thanks Seunghyun for starting this thread. > > There is no special requirement to have a graduation release. Graduation is a > separate process from release. It’s just that release process changes > slightly after the graduation. > > Do you want to do this release before or after graduation? > > On Mon, May 10, 2021 at 11:27 AM Subbu Subramaniam <mcvsu...@apache.org> > wrote: >> >> Hopefully, everyone has been following the process of labelling PRs for >> release notes and noting any compatibility issues as well. >> >> If so, you should be able to get a list of commits (and PRs) and look for >> the labelled ones to answer the compatibility and release notes questions. >> >> I don't know of any other way than scanning the commit messages to come up >> with the major features or bug fixes list. >> >> -Subbu >> >> On 2021/05/10 18:04:41, Seunghyun Lee <sn...@apache.org> wrote: >> > Hi all, >> > >> > Given that we started to have a conversation about the graduation >> > process, I would like to use this thread for discussing about 0.8.0 >> > release (graduation release). >> > >> > Some points that we need to discuss: >> > - What are the major features that we would like to highlight? >> > - Do we have any pending features that need to be part of 0.8.0 release? >> > - Have we introduced any backward incompatibility? >> > >> > By the way, I would like to volunteer for creating the 0.8.0 release. >> > Given that I set up the initial Apache release pipeline for Pinot and >> > created the first 0.1.0 Pinot release, I think that I have enough >> > context to clear some issues that got brought up during the last >> > release process (e.g. LICENSE). >> > >> > Best, >> > Seunghyun >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org >> > For additional commands, e-mail: dev-h...@pinot.apache.org >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org >> For additional commands, e-mail: dev-h...@pinot.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org For additional commands, e-mail: dev-h...@pinot.apache.org
