On Tue, May 31, 2016 at 6:03 AM, Sage Weil <sage@xxxxxxxxxxxx> wrote: > On Tue, 31 May 2016, John Spray wrote: >> Hi all, >> >> Currently we have "Category", which is sort of a mixture of physical >> components (e.g. MDS, OSD, client, librados) and higher level >> features/topics. >> >> Lots of tickets actually refer to both a feature and a component, for >> example in cephfs we have lots of tickets related to FSCK, and some of >> them are MDS changes while some are tool changes. Currently we sort >> of work around this by prefacing things to subjects. >> >> I'm thinking that maybe we need two fields, one saying which component >> (i.e. which subdir in the git tree), and one giving a higher level >> category (which I'm imagining calling "topics"). >> >> In a CephFS context, examples of components would be MDS, client, >> ceph-fuse, libcephfs, libcephfs-python, cephfs-volume-client, kernel >> client, hadoop plugin, samba plugin, ganesha plugin, tools, >> MDSMonitor, qa-suite. >> >> ...whereas topics would be features that affect multiple components >> like: multi-mds, multi-fs, snapshots, fsck. >> >> Thoughts? > > Sounds good to me! This might be slighly tricky to set up in redmine (not > sure if 'categories' is special or not). Hah, looks like we just create another "list" custom field. I'll experiment with splitting "category" into "component" and "topic" later today. (Actually, it'll probably be "category" and "component", but we'll see how things behave.) -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
