-1
Its too much of a pain to move issues to a real project once the
project needs one. Also this will end up being a mess for people to
see what is actually going on for one of the projects in the
sandbox. And makes it practically impossible for those projects to
use the version/road map feature of JIRA.
As its been mentioned before, its easy enough to create and drop
projects. If we add a new category for Geronimo Sandbox, then we can
classify these up and coming G sub-projects.
--jason
On Jun 15, 2006, at 8:12 AM, Donald Woods wrote:
Why not create a geronimo-sandbox JIRA to cover all activities in
there?
John Sisson wrote:
+1 . How about having "sandbox" as part of the name of the Project
or Component so it is clear to users what the status of the
project is.
John
Alan D. Cabrera wrote:
Well, who can argue with that line of reasoning. :)
Now that I think of it, if making a Jira project helps build a
community around it, let's do it. It will be trivial to drop the
project, as Dain has previously mentioned.
Regards,
Alan
Jason Dillon wrote:
GShell isn't gonna die... it will rule the world one day... its
already kicking much ass.
Unix geeks are gonna love us... :-]
--jason
On 6/9/06, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
On Jun 9, 2006, at 9:35 AM, Alan D. Cabrera wrote:
> Jason Dillon wrote:
>> Can we create a new JIRA project for GShell? I've got a
bunch of
>> task/todo items that I would like to track in JIRA so it is
easier
>> to prioritize and plan.
>>
>> Thoughts?
>>
>> --jason
>>
> IMO, if it gets out of the sandbox, it deserves a Jira project.
I seen no reason not to give it a JIRA. If it dies in the
sandbox,
we can always delete the JIRA.
-dain
