All of lore.kernel.org
 help / color / mirror / Atom feed
From: Victoria Dye <vdye@github.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	Derrick Stolee <derrickstolee@github.com>
Subject: Git 2.41 release date
Date: Wed, 22 Mar 2023 10:59:50 -0700	[thread overview]
Message-ID: <f337e514-8d3b-927a-5fe3-34f67f199435@github.com> (raw)

Hi everyone! 

While perusing the Git Calendar [1], I noticed that the final 2.41 release
date is on a major US holiday (Memorial Day, May 29). In the past, release
dates have been shifted to avoid situations like this, and doing so has been
noticeably helpful to downstream maintainers/integrators. Would it make
sense to similarly shift 2.41?

Thanks,
-Victoria 

[1] https://calendar.google.com/calendar/u/0/embed?src=jfgbl2mrlipp4pb6ieih0qr3so@group.calendar.google.com

             reply	other threads:[~2023-03-22 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 17:59 Victoria Dye [this message]
2023-03-22 19:16 ` Git 2.41 release date Junio C Hamano
2023-03-23  4:27   ` Victoria Dye

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f337e514-8d3b-927a-5fe3-34f67f199435@github.com \
    --to=vdye@github.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.