It would be nice to "tag" commits that we want to back port with git notes
or some such thing.
Last week's V2.6 commits that need backporting will be ported this week (a
week behind in time to allow some testing in V2.6)
Whoever is going to tag the release can "cherry-pick" the commits (any
merge conflicts will be coordinated with the author).
Regards, Malahal.
On Thu, Oct 5, 2017 at 3:09 AM, Frank Filz <ffilz...@mindspring.com> wrote:
> When we first talked about stable maintenance for V2.5, it seemed like IBM
> was most likely to be using V2.5 and we elected Malahal to be V2.5-stable
> maintainer.
>
> It now seems we have pressure from other fronts for V2.5 stable fixes, I'd
> like to open the discussion on how best to manage it? I'd be happy to do
> additional backports and V2.5-stable tagging, or we could ask Kaleb to do
> it, or we can operate on a "make requests to Malahal" procedure.
>
> Any input here is welcome, I want to make sure we respect everyone's needs
> for V2.5-stable.
>
> Frank
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
