On 2020-06-03 at 20:59:39, Junio C Hamano wrote: > Here are the topics that have been cooking. Commits prefixed with > '-' are only in 'pu' (proposed updates) while commits prefixed with > '+' are in 'next'. The ones marked with '.' do not appear in any of > the integration branches, but I am still holding onto them. > > Git 2.27 has been tagged, and the first batch of topics (including > the "throw protocol v2 to the experimental group of features" thing) > have been merged to the 'master' branch. I'm planning to rewind the > tip of 'next' in a not-so-distant future. > > Seeing a handful of regression reports [*] immediately after a > feature release is made gives me a mixed feeling: people are eager > enough to help by reporting issues they encounter, but there are not > enough people who are eager enough to help by testing the tip of > 'master' before the release. Are there things we can do to help > them become early adopters so that they do not have to scramble > after the release? For folks that are using Debian, Jonathan Nieder kindly keeps Debian experimental generally within about a week or so of the latest next (with the -rc merged into it during that period). (As of today, the version is from 2020-05-31.) This is usually what I use and it's reasonably stable, so folks who want to test things may find it convenient to rely on existing packages. I don't happen to use a lot of these features, so I don't notice any issues with them, but I have seen issues in the past with other features and reported them. Maybe if there are companies with folks who are using sparse-checkout and similar features it may be helpful to build and deploy an -rc or two if they have some way of standard deployments to developer machines (which I admit most places don't). -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204
Attachment:
signature.asc
Description: PGP signature
