Re: naming development branches consistently

+1 for trunk and main. Thanks for raising this Brandon. On Tue, 25 Aug 2020 at 20:40, Cyril Scetbon wrote: > Scott, I don’t think it does and don’t see any offense in what I’ve said. > Can you be more specific instead of sending a link with rules numbers that > I don’t think apply ? I can als

Re: naming development branches consistently

Scott, I don’t think it does and don’t see any offense in what I’ve said. Can you be more specific instead of sending a link with rules numbers that I don’t think apply ? I can also send links to definitions of all the words in the rules you sent but it could be a waste of time. We can continue

Re: naming development branches consistently

Cyril, your commentary violates the code of conduct of the ASF re rules #2 and #5. It could also be very hurtful to those who feel this is important, as many in the community do. Please think before pushing further on this as projects need to be

Re: [DISCUSS] CEP-7 Storage Attached Index

> > Does community plan to open another discussion or CEP on modularization? We probably should have a discussion on the ML or monthly contrib call about it first to see how aligned the interested contributors are. Could do that through CEP as well but CEP's (at least thus far sans k8s operator) t

Re: [DISCUSS] CEP-7 Storage Attached Index

>>> SASI's performance, specifically the search in the B+ tree component, >>> depends a lot on the component file's header being available in the >>> pagecache. SASI benefits from (needs) nodes with lots of RAM. Is SAI bound >>> to this same or similar limitation? SAI also benefits from larger mem