On 3/31/24 11:49, Tom Lane wrote:
Joe Conway writes:
I am saying maybe those patches should be eliminated in favor of our
tree including build options that would produce the same result.
I don't really see how that can be expected to work sanely.
It turns the responsibility for platform
of assuming that bad things can't happen to
us.
+1
and again with the +1 ;-)
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
certain certifications. Of course there is no guarantee that such
reviews would catch everything, but maybe we could establish post commit
reviews by contributors in a more rigorous way? Granted, getting more
qualified volunteers is not a trivial problem...
--
Joe Conway
PostgreSQL Contributors
.
+1
Markdown is pretty readable as text, I'm not sure why we need both.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
of the PostgreSQL Contributors Team
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
the conversion even simpler.
That's a pretty convincing proof-of-concept. Let's just do this,
and then make sure to keep the file legible as plain text.
+1
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
at best sub-linearly (limited by the
velocity of knowledge sharing). I agree with Andrey on this, the only
way I see to handle this is to scale CF management efforts.
The number of items tracked are surely growing, but I am not sure I
would call it exponential -- see attached
--
Joe Conway
seriously.
Maybe do a FOSDEM-style dev meeting with triage review at PG.EU would at
least move us forward? Granted it is less early and perhaps less often
than the thread seems to indicate, but has been tossed around before and
seems doable.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open
I'm
still here, please review my patch," we've already lost the game. That
person isn't sad because we asked them to click a link. They're sad
it's already been N * 2 months and nothing has happened.
+many
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon
On 5/17/24 09:08, Peter Eisentraut wrote:
On 17.05.24 14:42, Joe Conway wrote:
Namely, the week before commitfest I don't actually know if I will
have the time during that month, but I will make sure my patch is in
the commitfest just in case I get a few clear days to work on it.
Because
On 5/17/24 08:31, Jelte Fennema-Nio wrote:
On Fri, 17 May 2024 at 14:19, Joe Conway wrote:
On 5/16/24 22:26, Robert Haas wrote:
> For example, imagine that the CommitFest is FORCIBLY empty
> until a week before it starts. You can still register patches in the
> system generally, but
sing the point. What we really want is to not see that stuff in
the first place. It's a CommitFest, not
once-upon-a-time-I-wrote-a-patch-Fest.
+1
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
that lesson
the hard way. I'm just distressed at our utter failure to learn
from experience.
I don't dispute that we could do better, and this is just a simplistic
look based on "number of commits per day", but the attached does put it
in perspective to some extent.
--
Joe Conway
he policy written down somewhere, or is it only project lore? In
either case, what is the actual policy?
Thanks,
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
On 6/2/24 15:17, Neil Conway wrote:
Inspired by David Rowley's work [1]
Welcome back!
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
re changes.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
401 - 416 of 416 matches
Mail list logo
