Given the hectic nature of my life at the moment, I would say longer than a week. Would it make sense to do an M2 to verify the APIs and then lock down and comb through documentation with a fine tooth comb, looking for errors and missing explanations before an M3 that has no code, just documentation changes?
Claude On Thu, Jun 13, 2024 at 12:47 PM Gary Gregory <garydgreg...@gmail.com> wrote: > It would be better IMO to have the updated documentation for M2 but not > critical, let me know if you think you can do it "soon" (say within a week) > or if it's just on a longer term to-do list. > > TY, > Gary > > On Thu, Jun 13, 2024, 3:39 AM Claude Warren <cla...@xenei.com> wrote: > > > The only changes I am considering are to remove any stream usage within > the > > code, no external changes. Additionally, there may be some new > > documentation coming but that can wait until after M2. > > > > Thanks for all your hard work on this. > > Claude > > > > On Wed, Jun 12, 2024 at 7:30 PM Gary D. Gregory <ggreg...@apache.org> > > wrote: > > > > > HI All, Claude W, Alex H: > > > > > > I would like to cut a 4.5.0-M2 RC later this week to capture latest > bloom > > > filter code. > > > > > > Feel free to ask me to hold back if you plan further changes first. > > > > > > TY! > > > Gary > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > -- > > LinkedIn: http://www.linkedin.com/in/claudewarren > > > -- LinkedIn: http://www.linkedin.com/in/claudewarren
