On 11/6/06, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
Great, will do.

A little more detail on when I think we should mark WONTFIX (lets
discuss).  I think it's nice to have enhancement requests/future
thoughts in JIRA.  The "wont fix" is rather offputting.

agreed.  but it is better than silently ignoring such things.  i think
it's more polite if a committer responds with a strong negative than
if no one responds.

There's a continuum for responses to enhancement requests..
-- committers really enthusiastic about idea; will certainly go in
-- idea fits with philosophical direction of tool, might go in but not right now
-- idea is from left field, will likely not go in

I'd suggest we always leave the first two bullets as open issues.
Helps capture usage details, example cases, mailing list threads.

+1

The third is a matter of judgement.  Doesn't hurt to occasionally
leave a creative idea open, but more often we should provide feedback
and (if appropriate) ask the poster to move sample code to the wiki.

+1  pushing the wiki is very good

A good rule of thumb should be that all active committers believe an
idea is "from left field" in order to mark WONTFIX.

+1 if and only if...

  Or at least that
it's ok for a committer who's interested in immediate reopen the
issue.

this is the canonical process.  close if you don't like it.  if no
committer re-opens, then that means no interest.   this is more
workable than seeking acks on a motion to close an issue.

Just my thoughts.  Comments?

WILL

On 11/6/06, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote:
> "Will Glass-Husain" <[EMAIL PROTECTED]> writes:
>
> Sure, go ahead. I thought the wiki page to be sufficient but if you feel
> more comfortable with having it in JIRA, I'm all +1 for that.
>
>         Best regards
>                 Henning
>
>
> >Henning,
>
> >I noticed you closed all the Macro-related JIRA issues.  I see this as
> >a usability barrier and something we should definitely address in a
> >future version.  In particular, the need to be able to #parse a file
> >that includes macros is important.
>
> >I'd like to reopen the issues.  They serve as a reminder to address
> >these issues for 1.6.
> >But I don't want to get into a open/close/open/close fight.  Any
> >comments before I do this?
>
> >(see 
http://blogs.codehaus.org/people/geir/archives/001414_somtimes_process_is_good_somtimes_not.html
> >)
>
> >WILL
>
> >--
> >Forio Business Simulations
>
> >Will Glass-Husain
> >[EMAIL PROTECTED]
> >www.forio.com
>
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
> [EMAIL PROTECTED]        +49 9131 50 654 0   http://www.intermeta.de/
>
> RedHat Certified Engineer -- Jakarta Turbine Development  -- hero for hire
>    Linux, Java, perl, Solaris -- Consulting, Training, Development
>
> Social behaviour: Bavarians can be extremely egalitarian and folksy.
>                                     -- http://en.wikipedia.org/wiki/Bavaria
> Most Franconians do not like to be called Bavarians.
>                                     -- http://en.wikipedia.org/wiki/Franconia
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Forio Business Simulations

Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to