On 5/22/24 12:32 AM, Zachary Santer wrote:
On Tue, May 21, 2024 at 3:06 PM Chet Ramey <chet.ra...@case.edu> wrote:
On 5/21/24 11:14 AM, Zachary Santer wrote:
On Tue, May 21, 2024 at 9:01 AM Chet Ramey <chet.ra...@case.edu> wrote:
On 5/21/24 6:17 AM, Zachary Santer wrote:
I was wondering what the relationship between the devel and master
branches was.
No mystery: the devel branch captures ongoing development, gets the latest
bug fixes, and is where new features appear. The master branch is for
stable releases.
But the devel branch won't get changes for bash versions beyond what's
in alpha right now?
I'm genuinely curious how you got that from what I said, especially since
devel has gotten changes since I released bash-5.3-alpha.
Changes I assumed would make it into master while master is bash-5.3.
It sounded like you didn't want to implement anything in devel right
now that wasn't going to make it into bash-5.3. I probably didn't
phrase that very well.
I'm not planning on including any additional new features in bash-5.3
beyond what's in alpha now. If I do some work on new features -- I don't
usually, I try to spend my time on bug fixes and release engineering --
I'll do it in a private branch that doesn't get merged until after
bash-5.3 is released.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
