Agree for PR #5053, that makes sense. I will do a new pass on this one :) Regards JB
On Fri, Aug 28, 2026 at 3:25 PM Dmitri Bourlatchkov <[email protected]> wrote: > > +1 to including PR 5053 into 1.8.0. > > Thanks, JBm for driving this release! > > Cheers, > Dmitri. > > On Fri, Aug 28, 2026 at 12:34 PM Yufei Gu <[email protected]> wrote: > > > Since we have worked on PR 5053 for a while, and it's getting close to > > being done, I'd suggest including it in 1.8.0. > > > > Yufei > > > > > > On Wed, Aug 26, 2026 at 8:48 AM Jean-Baptiste Onofré <[email protected]> > > wrote: > > > > > Hi Robert, > > > > > > That works for me. > > > > > > I just wanted to gauge the community's thoughts on some of the > > > proposals currently in progress. There is no pressure to include them, > > > and given our monthly cadence, waiting for future cycles is not an > > > issue. > > > > > > Regards, > > > JB > > > > > > On Wed, Aug 26, 2026 at 8:07 AM Robert Stupp <[email protected]> wrote: > > > > > > > > Hi JB, > > > > > > > > +1 to the proposed 1.8.0 schedule, and thanks for volunteering to drive > > > it. > > > > > > > > I would keep this release focused on the fixes and improvements that > > are > > > > ready for users today. > > > > > > > > For the features mentioned, I do not think we yet have a sufficiently > > > > bounded and documented end-to-end user workflow to present any of them > > > as a > > > > preview or experimental feature. > > > > There is still important design or implementation work in each area, > > and > > > > the label would otherwise be ambiguous for users. > > > > > > > > It would be great to keep that work moving and revisit it once a > > feature > > > > has a clear scope, documented behavior and non-goals, and a workflow > > that > > > > users can actually evaluate. > > > > > > > > Cheers, > > > > Robert > > > > > > > > On Tue, Aug 25, 2026 at 9:49 AM Ayush Saxena <[email protected]> > > > wrote: > > > > > > > > > +1, Thanx JB for volunteering!!! > > > > > > > > > > -Ayush > > > > > > > > > > On 2026/08/24 17:06:42 Alexandre Dutra wrote: > > > > > > Hi JB, > > > > > > > > > > > > +1 on your proposed schedule. > > > > > > > > > > > > On a personal note, and just FYI, I will be OOO for most of > > > September, > > > > > > but I am confident that the team is fully prepared and > > well-equipped > > > > > > to lead the upcoming release successfully. > > > > > > > > > > > > Thanks, > > > > > > Alex > > > > > > > > > > > > On Mon, Aug 24, 2026 at 5:59 PM Yufei Gu <[email protected]> > > > wrote: > > > > > > > > > > > > > > +1 on the timeline. Thanks for the volunteering, JB! > > > > > > > > > > > > > > Yufei > > > > > > > > > > > > > > > > > > > > > On Mon, Aug 24, 2026 at 5:55 AM Jean-Baptiste Onofré < > > > [email protected]> > > > > > > > wrote: > > > > > > > > > > > > > > > Hi folks, > > > > > > > > > > > > > > > > Regarding our monthly release pace, I propose releasing Apache > > > > > Polaris > > > > > > > > 1.8.0 at the beginning of September. > > > > > > > > > > > > > > > > In addition to our usual fixes and improvements, it would be > > > great to > > > > > > > > include a preview or beta version of a new feature, such as > > > > > > > > Directories, Tags, OpenLineage, or Data Sharing. > > > > > > > > > > > > > > > > Wdyt? > > > > > > > > > > > > > > > > On a related note, I plan to review the proposals that are not > > > > > > > > currently linked to a GitHub issue. For instance, OpenLineage > > and > > > > > Data > > > > > > > > Sharing are not appearing in our tracking view: > > > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/apache/polaris/issues?q=is%3Aissue%20state%3Aopen%20label%3Aproposal > > > > > > > > > > > > > > > > Linking these proposals will help provide better visibility and > > > > > > > > insights to the community. > > > > > > > > > > > > > > > > Regards, > > > > > > > > JB > > > > > > > > > > > > > > > > > > > > > > > >
