Am 2022-11-18 um 03:15 schrieb larry mccay:
Personally, I find RTC much more appropriate for mature-ish projects where
quality and awareness are a higher priority than fast innovation.
I think the sub-topic here actually supports that notion.
Faster innovation and iterative development can happe
Personally, I find RTC much more appropriate for mature-ish projects where
quality and awareness are a higher priority than fast innovation.
I think the sub-topic here actually supports that notion.
Faster innovation and iterative development can happen in feature branches
with appropriate merge c
There's your answer Cater, it was intentional, unreviewed, and unilateral.
On 2022/11/15 21:22:29 Oleg Kalnichevski wrote:
> On Tue, 2022-11-15 at 15:41 -0500, Gary Gregory wrote:
> > This is a distraction from the problem I brought up in another
> > thread: Oleg
> > erases other people's commits
On Tue, 2022-11-15 at 15:41 -0500, Gary Gregory wrote:
> This is a distraction from the problem I brought up in another
> thread: Oleg
> erases other people's commits at he wishes, CTR or RTC won't matter.
> This
> is not the Apache way.
>
You have a long history of making really bad changes to t
On Tue, Nov 15, 2022, at 15:41, Gary Gregory wrote:
> This is a distraction from the problem I brought up in another thread: Oleg
> erases other people's commits at he wishes, CTR or RTC won't matter. This
> is not the Apache way.
Was this omission intentional, or accidental?
Thanks for bringing this up!
I prefer RTC myself for a number of reasons:
It's easier for me to follow development when I get PR notifications, the
github PR UI is fantastic.
Based on email updates from PR discussion, I can join conversations where I
have relevant experience.
Even for minor chan
This is a distraction from the problem I brought up in another thread: Oleg
erases other people's commits at he wishes, CTR or RTC won't matter. This
is not the Apache way.
Gary
On Tue, Nov 15, 2022, 15:37 Michael Osipov wrote:
> Am 2022-11-15 um 14:32 schrieb Oleg Kalnichevski:
> > We have an
Am 2022-11-15 um 14:32 schrieb Oleg Kalnichevski:
We have an implicit commit-them-review policy ever since the inception
of the project in the year of 2005. We all are free to commit what we
deem appropriate but no commit can be considered safe until it has been
voted upon and tagged with a rel
We have an implicit commit-them-review policy ever since the inception
of the project in the year of 2005. We all are free to commit what we
deem appropriate but no commit can be considered safe until it has been
voted upon and tagged with a release tag.
If an objection has been raised about a
