Bug 1644049

Summary:	Deprecating /etc/sysconfig/nfs
Product:	[Fedora] Fedora	Reporter:	Ben Cotton <bcotton>
Component:	Changes Tracking	Assignee:	Steve Dickson <steved>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	30	CC:	bcotton, riehecky, steved
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nfs-utils-2.3.3-6.rc2.fc30	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-30 15:49:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ben Cotton 2018-10-29 21:08:58 UTC

This is a tracking bug for Change: Deprecating /etc/sysconfig/nfs
For more details, see: https://fedoraproject.org/wiki/Changes/nfs.conf

Deprecate /etc/sysconfig/nfs and only use /etc/nfs.conf to configure NFS daemons.

Comment 1 Ben Cotton 2019-02-19 20:30:19 UTC

According to the Fedora 30 schedule[1], today is the deadline for changes to be in a testable state. If your change is ready to be tested, please set the status to MODIFIED. If you know your change will not be ready for Fedora 30, you can set the version to rawhide and notify bcotton. For more information about this milestone, see the Changes Policy[2].

[1] https://fedoraproject.org/wiki/Releases/30/Schedule
[2] https://fedoraproject.org/wiki/Changes/Policy#Change_Checkpoint:_Completion_deadline

Comment 2 Steve Dickson 2019-02-20 17:36:54 UTC

(In reply to Ben Cotton from comment #1)
> According to the Fedora 30 schedule[1], today is the deadline for changes to
> be in a testable state. If your change is ready to be tested, please set the
> status to MODIFIED. If you know your change will not be ready for Fedora 30,
> you can set the version to rawhide and notify bcotton. For
> more information about this milestone, see the Changes Policy[2].
> 
> [1] https://fedoraproject.org/wiki/Releases/30/Schedule
> [2]
> https://fedoraproject.org/wiki/Changes/Policy#Change_Checkpoint:
> _Completion_deadline

Sorry about that.... I did the build last week but forgot to
update the bz.

Comment 3 Ben Cotton 2019-03-05 21:49:55 UTC

We have reached the Code Complete (100%) milestone in the Fedora 30 development cycle. At this point, all Changes should be fully code complete and ready for testing during the beta freeze. If your Change has reached this milestone, please set the status to ON_QA. If it has not, this Change will be submitted to FESCo to evaluate the contigency plan and decide if the Change will continue in the Fedora 30 cycle.