- development-process (223x)
- development-methodologies (47x)
- methodology (47x)
development-methodology (1x) There are also questions tagged process (3x) and processes (5x). All 3 questions tagged process are about development methodologies. 4 of the 5 questions tagged processes are about development methodologies and software engineering process, while the fifth is about emulating UNIX processes.
Yannis (and others) have cleaned up the
processes tags so there are no more questions with these tags applied to them. This leaves four tags to deal with.
The FAQ uses the term "development methodologies" to describe what's on-topic, merging all into the development-methodologies tag might be appropriate. However, development-process is much more widely used. Although the formal name is "software engineering process", I'd shy away from that name because the descriptor "software engineering" is redundant here and "process" alone is too vague (development processes versus business processes versus system processes).
Ultimately, I think that this tag might need manual clean up as part of the Structured Tag Clean Up effort to capture the breadth of software engineering process: process improvement, software development life cycles, process assessment, process quality. It would be easier to see if this was necessary and then implement it if we had everything in one tag, though, rather than across 5 or 6.
Proposal: Automatically merge development-methodologies, methodology, development-methodology, and process into development-process. Synonymize development-methodologies, methodology, and development-methodology with development-process. Manually retag the 4 development methodology questions in processes into development-methodologies. Evaluate the quality of the development-methodologies tag as part of Structured Tag Clean Up at a later date.