Let's get this worked out, since I think we might be cutting 0.13.0
sooner rather than later. I've already got one incompatible change committed
and it'd be good to maybe just make it "the incompatible release" or something.
Haha.
> On Jun 16, 2020, at 8:15 PM, Sean Busbey <bus...@apache.org> wrote:
> To minimize the learning curve for new contributors I'd say we should
> go with whatever GitHub changes the default to. I haven't seen
> anything on the main github site, but the article you linked (and a
> couple others I've seen) suggests "main" ?
I was hoping by now that there would be a more definitive timeline from
GitHub. On the plus side, it appears that there is a general movement towards
'main'. [At least given by the number of tutorials on how to do this that have
popped up lately... e.g.,
https://dev.to/afrodevgirl/replacing-master-with-main-in-github-2fjf, which
also has a lot of interesting discussion ] IMO, I'm glad to see more of a
community decision rather than GitHub dictating.
> On Jun 22, 2020, at 3:46 PM, Nick Dimiduk <ndimi...@apache.org> wrote:
> For the test-patch default, maybe we omit a default value going forward and
> require the user always provide it.
Every new required setting is one more barrier to entry. I already
hate how many things users are required to set. (Frankly, the restrictions we
have around default --plugins is enough to make me question whether the ASF is
the correct place for this project.)
> For that matter, if we make this value
> available as an environment variable, a project can specify it's default
> branch name via personality file.
Personalities already have this capability.
