Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tdrwN-00ADEH-C3 for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Jan 2025 14:24:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tdrwM-000lUS-4T for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Jan 2025 14:24:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tdrwL-000lUK-OH for pgsql-hackers@lists.postgresql.org; Fri, 31 Jan 2025 14:24:13 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tdrwH-002Tbv-2a for pgsql-hackers@lists.postgresql.org; Fri, 31 Jan 2025 14:24:12 +0000 Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-304e4562516so19695411fa.1 for ; Fri, 31 Jan 2025 06:24:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeltef.nl; s=google; t=1738333447; x=1738938247; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=+g1t8CPiWt49wvRQrhVZos/7JfX7mfauPa1q4HAJXSs=; b=FNNizdfFy49j6psuYlKX/vT9H+k5hHO05L+XssoKBoPHG7HdDZUaJB3xNdXws3ymyV vD1lek6YEaTp9eSJ3p+3gURbnrZc3EcD+PaTQjTXJpAepPDezKci5ePHJTOeKoGnjcKB kjPtZn5CfUMzCb2i4paq0Gl1kK+Nkgsa5suNi0e9fR0HumK+xEws8SUxf6zOjc83tdpf PYA0TRmqtAAkSXDOPAtXCnPayqSunjYr6LoOsCrckf778vshvqXdSu8uBeEtbjuK1OE8 6//CBtfua6LSpg2+RmkrkgHmk6BBxdARE2xOuFym3w2xmvd9mHsf9DdgFXQ9STgqnLlr QRcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738333447; x=1738938247; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=+g1t8CPiWt49wvRQrhVZos/7JfX7mfauPa1q4HAJXSs=; b=HLed0ygeQYIXU7uqRwG2MieMRd7ZOD6sQ5ZN1n/I4t0ngeCC1xWfDS6/WXcavr6SES hH1B9s75xwJUeJOdHsJ9DuJiFTGBEGihDdsxWd3LNFa76eUeH4hQbPIlpEK0obBaY4YU a1RiZ01aW5Ynp+U+MmqsE4ardoSRhXH3j5wn262yCL0RCfY2byVAx+RvJJ3L6T5tcYRd 1+KHvGKiqMHj3NE55DKUFrwKmho78PjcMNEIoAT3sNQmzOwDbinGiBjCvWsgbsjIgOb9 o+XT68P8/bOqFK+8AOu/jayr/q1nXAfam+iqweKv0KAPCWt6qiH9+v3i+9y4LAIH7rH4 cr6A== X-Gm-Message-State: AOJu0YwrmXZNqKJTpnimCBQJX0qtK75eL0DPbYm7y9dget7ekQLk23yp gT8oFhBsEm5SMvAh9mXH7jBigrDE28TM3ISHqL45bNjSEKseaWOB4j6jeUheI4/8zCld1Kr3WWZ ynly9RWLHkgZ5y7RYlp0DQtNQV9KeptFhIT09++ce3LjdOm3DLZgH6g== X-Gm-Gg: ASbGncu1dTLWn5mT2Ho/37BGZ5UmXp9ynlhkaXHdeaqHtou9dh2CaEKOlIyXCq/SO8C Ko1fbnpGgseBK76Hl6q6lzNXNG/1wMYU2MMYOoN6SeA/t8JCqd4/d2B0JGvzNayPaWcWHfF66 X-Google-Smtp-Source: AGHT+IFbn9Upds/VVxBjRhvQXflxovtIT5yrvwO/X38kgiwuLcTHdLLbFAgzuwgXv7uLqFf4si/YtkR4Nt+wN/p6t9A= X-Received: by 2002:a2e:bd83:0:b0:306:1380:2410 with SMTP id 38308e7fff4ca-307a10b5409mr27343411fa.1.1738333447123; Fri, 31 Jan 2025 06:24:07 -0800 (PST) MIME-Version: 1.0 From: Jelte Fennema-Nio Date: Fri, 31 Jan 2025 15:23:56 +0100 X-Gm-Features: AWEUYZlGnp2sg54DZPge3bkEzo0PBlM-JSRWKqv2tFnIOhLA5YKzFH156SHQQ84 Message-ID: Subject: Commitfest app release on Feb 17 with many improvements To: PostgreSQL Hackers Cc: Jacob Brazeal Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk At the FOSDEM dev meeting we discussed potential improvements to the commitfest app and how to handle deploying future changes with minimal disruption to existing workflows. We're going to try a new approach: announcing a new commitfest release ~2 weeks in advance, including release notes. That way people can try out the changes on the staging environment and raise concerns/objections. So hereby such an announcement: The next commitfest app release will take place on February 17 and will contain the following user facing changes: 1. Showing CFBot status on patch and commitfest pages 2. Showing a link to the CFBot github diff on patch and commitfest pages 3. Showing total additions/deletions of the most recent patchset on patch and commitfest pages 4. Showing additions/deletions of the first patch of the most recent patchset on the patch page 5. Showing the version and number of patches of the most recent patchset on the patch page 6. Canonical links for the patch page are now /patch/{patchid} instead of /{cfid}/{patchid} 7. If you subscribed for emails or patches where you're an author, you will now get an email when your patch needs a rebase. 8. Clicking headers will toggle sorting, instead of always enabling it 9. Allow sorting patches by name 10. Allow sorting patches by total additions/deletions (added together for total lines changed) 11. Add ID column to commitfest page (allows sorting) 12. Allow sorting using the header of closed patches too 13. Fix dropdown direction for dropdowns at the bottom of the page (they now drop up) 14. The previous GiHub and CirrusCI links are now integrated into the new CFBot status row of the patch page 15. The previous GitHub checkout instructions are now integrated into the new CFBot status row as a button that copies the commands to the clipboard You can try out these changes on the staging environment[1] with pgtest:pgtest as user & password for the http auth. If you want to make edits you need to create a new account, read-only doesn't need an account. [1]: https://commitfest-test.postgresql.org/