[Evergreen-dev] Changing branch name "master" to "main" at the conference

[Galen Charlton]

Agreed; "main" appears to be the new default for Git projects that use that
kind of branch structure, so I think we should just run with that.

Regards,

Galen

On Tue, Nov 1, 2022 at 8:06 PM Jeff Davis via Evergreen-dev <
evergreen-dev at list.evergreen-ils.org> wrote:

> I think we should reduce the friction for new contributions as much as
> possible, and it seems to me that "main" will cause the fewest headaches
> for new developers.  It's the branch name that people are starting to
> expect now that Github and others have made the change.  I don't really
> see a compelling reason not to use "main" at this point.
>
> Jeff
>
> On 2022-11-01 2:01 PM, Jason Stephenson via Evergreen-dev wrote:
> > Hi, all.
> >
> > I know calling the main branch "main" is all the rage these days, but
> > I'd like to ask why not call it "trunk?"  It's the default for SVN and
> > possibly CVS, IIRC.  It's also still in our configure.ac.
> >
> > Cheers,
> > Jason
> > _______________________________________________
> > Evergreen-dev mailing list
> > Evergreen-dev at list.evergreen-ils.org
> > http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
> _______________________________________________
> Evergreen-dev mailing list
> Evergreen-dev at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
>


-- 
Galen Charlton
Implementation and IT Manager
Equinox Open Library Initiative
gmc at equinoxOLI.org
https://www.equinoxOLI.org
phone: 877-OPEN-ILS (673-6457)
direct: 770-709-5581
<http://evergreen-ils.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-dev/attachments/20221102/dbb6e4ce/attachment.htm>