All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Oakley <philipoakley@iee.email>
To: Elijah Newren <newren@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jun 2020, #01; Wed, 3)
Date: Sat, 6 Jun 2020 14:57:48 +0100	[thread overview]
Message-ID: <ca05688f-4f03-97b4-7f88-a4fc89bc119a@iee.email> (raw)
In-Reply-To: <CABPp-BFLUZvycq_o6mPcx3ZQkeQy79nQ_mGD3B+JLzBwb6ER=g@mail.gmail.com>

On 05/06/2020 02:46, Elijah Newren wrote:
> Another consideration we could make is just scheduling .1 releases
> automatically, and not limiting them to security fixes but instead
> considering the same kinds of things that would be allowed around the
> time of -rc1 or -rc2.  I still want to push to make the quality of .0
> releases as high as we can, but given that human nature seems to lean
> towards avoiding things until they are labelled as official, and since
> we benefit from that wider feedback, maybe we adjust slightly to take
> advantage of natural behavior and do .1 releases?  Anyway, just a
> thought.

Maybe simply tag the current master every 2 weeks of the cycle (.wk2,
.wk4, wk6), as appropriate, just to give potential users/testers a stake
in the ground to reference to.

Or maybe a 'mid cycle' .mc1 release for a similar 'nudge' effect [1] of
'try this one'.

Philip

[1] https://en.wikipedia.org/wiki/Nudge_theory

  reply	other threads:[~2020-06-06 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 20:59 What's cooking in git.git (Jun 2020, #01; Wed, 3) Junio C Hamano
2020-06-04  8:14 ` Elijah Newren
2020-06-04 14:32   ` Christian Couder
2020-06-04 14:39     ` Christian Couder
2020-06-06 14:53     ` Kaartic Sivaraam
2020-06-07  6:27       ` Christian Couder
2020-06-04 14:49   ` Junio C Hamano
2020-06-05  1:46     ` Elijah Newren
2020-06-06 13:57       ` Philip Oakley [this message]
2020-06-04 23:41 ` brian m. carlson

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=ca05688f-4f03-97b4-7f88-a4fc89bc119a@iee.email \
    --to=philipoakley@iee.email \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newren@gmail.com \
    /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.