On 5/2/06, Martin Cooper <[EMAIL PROTECTED]> wrote:
On 5/2/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
>
> We'd suck all the data into a project in Jira called Commons. Then
> we'd move stuff out of it into individual projects until we had just
> [site]/[all] issues left. Then we'd delete the versions and components
> in that Jira project and it becomes our catch-all Jira project.
The problem with that is that you can be sure that plenty of people will
file issues under something called just "Commons" without looking for the
component. We'd be better off, IMHO, creating explicit components for 'site'
and 'all'. (I'm not at all convinced we need the latter, though, since there
would be issues with figuring out when it's ready to be marked Closed.)
It does sound likely. Looking at Bugzilla, there are 6 issues for
[site], one of which was more to do with the build system.
Let's go ahead and have a Commons Site project, and forget about the
all bit, or keeping the Commons project used for the migration.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
