From: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: fedfs-utils Developers
<fedfs-utils-devel-N0ozoZBvEnrZJqsBc5GL+g@public.gmane.org>,
Linux NFS Mailing List
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "fedfs-utils;release announcements"
<fedfs-utils-announce-N0ozoZBvEnrZJqsBc5GL+g@public.gmane.org>,
autofs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Chuck Lever via samba-technical
<samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org>
Subject: Re: Proposal for end-of-life for fedfs-utils development
Date: Wed, 14 Jun 2017 16:53:07 -0400 [thread overview]
Message-ID: <43E4D612-8CCD-4511-9E1D-265F4D459EE6@oracle.com> (raw)
In-Reply-To: <56804FBE-34B2-47FB-96EF-013D4476D89A-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
> On Jun 2, 2017, at 11:01 AM, Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> wrote:
>
> Upstream fedfs-utils has not been under active development for
> two years or more, and there is a scant user base. I'd like to
> propose making 0.10 the final major release of fedfs-utils.
>
> The plan:
>
> - Since 0.10 is in at least one major enterprise distribution,
> I will remain available to integrate security fixes and make
> new minor releases in the 0.10 line, as needed, for one to
> two more years.
>
> - Retire and remove fedfs-utils from upstream mirror distros
> such as Fedora rawhide.
>
> - Transfer utilities such as nfsref into nfs-utils, with
> support for FedFS junctions removed.
>
> - Announcements of the change in status will be made on
> fedfs-utils-announce and on the wiki.linux-nfs.org site.
>
>
>
> Comments welcome!
This was meant as a Request For Comments, but the cat is
out of bag now:
https://lwn.net/Articles/725411/rss
;-)
I haven't heard any objections to this proposal, so let's
go with it. Consider this the official announcement of
the end-of-life of fedfs-utils.
--
Chuck Lever
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
parent reply other threads:[~2017-06-14 20:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <56804FBE-34B2-47FB-96EF-013D4476D89A-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43E4D612-8CCD-4511-9E1D-265F4D459EE6@oracle.com \
--to=chuck.lever-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=autofs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=fedfs-utils-announce-N0ozoZBvEnrZJqsBc5GL+g@public.gmane.org \
--cc=fedfs-utils-devel-N0ozoZBvEnrZJqsBc5GL+g@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).