Re: [native-lang] Update: Sun/NLC meeting

Christian wrote:

> > It might be assigned to a dummy owner and/or we might use the useless
> > RESOLVED-LATER status for it, but we should not close it.
> I disagree, mainly because of working on the open issues gets easier

Why not have flags that indicate one of the following:
i) Feature can not be implemented because of coding problems.
ii) Feature will not, under any circumstances be implemented by Sun.
iii) Feature not cost effective for Sun to implement.

> Closing it with an appropriate comment may even result in the reporter searching for "independent" developers actively

That will happen if, and only if the reporter has an understanding of
why the issue was closed. The last time I was wading through closed
Issuezilla listings, if the bug/feature wasn't fixed, there either is
no explanation, or an irrational explanation for closing it. 
[Irrational as in "decimal separator as a comma only occurs in one
obscure language in one country."]

xan

jonathon
-- 
A Fork requires: 
   Seven systems with:
       1+ GHz Processors
       2+ GB RAM
       0.25 TB Hard drive space