Thanks Hemant for bringing them up here. Since the release vote ended, let’s make sure to include them in known issues section with the workaround suggestions. Next time let’s make sure to set the right priorities so that RM can consider them.
Let’s plan for 1.4.1. Regards, Uma On Fri, Jan 19, 2024 at 1:40 PM Hemant Kumar <hem...@apache.org> wrote: > Hi Attila/All, > These bugs are not causing data loss and more for better user experience. > > At this point of the release, I guess it should be fine to highlight them > as known issues and incorporate them in the 1.4.1 release as you said. > > Thanks, > Hemant > > On Fri, Jan 19, 2024 at 12:51 PM Attila Doroszlai <adorosz...@apache.org> > wrote: > > > Hi Hemant, > > > > > Jira priority is not set properly. If it helps I can change it to > blocker > > > for 1.4.0 release. > > > > 1.4.0 is released (vote passed, artifacts in place), it's just not > > announced yet on the website. > > > > > Both issues are important for Ozone Snapshot feature and if the issue > > > occurs, we have to restart OM nodes (at least the OM leader). > > > I don't think it is a good customer experience if it happens > frequently. > > > > My take: If the bug caused irreversible problems (data loss), we > > should remove the release to prevent it. Otherwise we can highlight > > it as a known issue in the release announcement. Users can decide to > > live with it temporarily, or wait for the bugfix release. > > > > Once we have the fixes for these bugs, we can release 1.4.1. We > > should strive for more frequent releases anyway. > > > > -Attila > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org > > For additional commands, e-mail: dev-h...@ozone.apache.org > > > > >
