23 Feb
2008
23 Feb
'08
7:53 a.m.
The reason is backward compatibility for the acronym, so that newcomers would check old issues and see "RTBC" and the new words would match it same with the old words.
Personally, we break backward compatibility all the time in Drupal, and saw what the heck, it is worth it. So why not do the same with issue status and documentation too? Yeah, some inconvenience for sure, but better in the long term.
So we're choosing sub-optimal status fields to preserve backward compatibility? That is very non-Drupal ... The whole 'tested and reviewed by the community' stuff doesn't make a whole lot of sense to me. I wouldn't mind to have us switch back to 'ready to be committed'. -- Dries Buytaert :: http://buytaert.net/