Lines Matching +full:key +full:- +full:release
5 --------
6 XFS is a well known high-performance filesystem in the Linux kernel.
10 Patches are generally merged to the for-next branch of the appropriate
12 After a testing period, the for-next branch is merged to the master
15 Kernel code are merged to the xfs-linux tree[0].
18 Ondisk format documentation are merged to the xfs-documentation tree[3].
21 list linux-xfs@vger.kernel.org.
24 -----
25 There are eight key roles in the XFS project.
31 - **Outside Contributor**: Anyone who sends a patch but is not involved
36 - **Developer**: Someone who is familiar with the XFS codebase enough to
42 - **Senior Developer**: A developer who is very familiar with at least
46 They should help prioritize development and review work for each release
51 - **Reviewer**: Someone (most likely also a developer) who reads code
63 - **Testing Lead**: This person is responsible for setting the test
66 release managers execute on the testing.
71 - **Bug Triager**: Someone who examines incoming bug reports in just
78 - **Release Manager**: This person merges reviewed patchsets into an
81 The release manager is not expected to work on new feature patchsets.
83 the release manager must have the ability to intervene to try to drive a
86 The release manager should identify themselves with an ``M:`` entry in
89 - **Community Manager**: This person calls and moderates meetings of as many
95 - **LTS Maintainer**: Someone who backports and tests bug fixes from
99 The maintainer for a given LTS release should identify themselves with an
105 -----------------------------
108 - Patches affecting only the filesystem itself should be based against
109 the latest -rc or the for-next branch.
110 These patches will be merged back to the for-next branch.
112 - Authors of patches touching other subsystems need to coordinate with
116 - Any patchset changing XFS should be cc'd in its entirety to linux-xfs.
120 - Anyone making kernel changes that have corresponding changes to the
124 - Authors of bug fix patches are expected to use fstests[2] to perform
129 - Authors of new feature patchsets must ensure that fstests will have
130 appropriate functional and input corner-case test cases for the new
133 - When implementing a new feature, it is strongly suggested that the
157 - Patchsets for the new tests should be submitted as separate patchsets
160 - Changes to the on-disk format of XFS must be described in the ondisk
164 - Patchsets implementing bug fixes and further code cleanups should put
167 Key Release Cycle Dates
168 -----------------------
169 Bug fixes may be sent at any time, though the release manager may decide to
173 -rc1 and -rc6.
178 next merge window should be sent between -rc1 and -rc4.
183 --------------
186 developers that have Reviewed-by tags for XFS changes to take a look and
190 ----------
191 | [0] https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/
192 | [1] https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/
193 | [2] https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/
194 | [3] https://git.kernel.org/pub/scm/fs/xfs/xfs-documentation.git/