Closed out in bulk with a comment (liking that Auto Closed resolution),
looks like I managed not to accidentally email everyone on each update, and
will be looking to get the process into the website soon.
~Josh
On Sat, Sep 11, 2021 at 2:52 AM Berenguer Blasi
wrote:
> +100 to closing anything t
>
> Where I think there becomes a grey area is on refactoring
ISTM we have two types of refactors:
1) Improving logic, tracking, state machines, etc (behavior, invasive)
2) Should be opaque to end user with zero change to behavior (hygiene, code
organization)
Feature flag on #1 as it's kind of a
With 6 (six) +1 votes and no -1 votes, the vote passes. Thanks everyone!
On Sat, Sep 11, 2021 at 11:41 PM Jordan West wrote:
> +1
>
> On Wed, Sep 8, 2021 at 11:38 AM Chris Lohfink
> wrote:
>
> > +1
> >
> > On Wed, Sep 8, 2021 at 11:58 AM bened...@apache.org >
> > wrote:
> >
> > > +1
> > >
> >
Perhaps re-add the settings virtual table mutability. That way the same
place can be used to update settings at runtime for multiple things instead
of creating a new virtual table per service we want to make hot props for.
Might be kinda nice to allow REGISTER and EVENT CQL events to be created
wi
I don’t think we can or we should cover every particular case but this is a
good baseline/guideline and we should encourage people to hit the mailing
list when there is uncertainty.
My understanding is that this document will support also the initially
mentioned one where I saw something that proba
