I would pose it even a bit stricter: does anyone care enough to provide a dev env *and* fix bugs :)
Fwiw, +1 on releasing with a known bug... Sent from my HTC ----- Reply message ----- From: "Patricia Shanahan" <[email protected]> To: "[email protected]" <[email protected]> Subject: Remaining Work For Next Release Date: Fri, Apr 1, 2011 02:52 On 3/31/2011 5:41 PM, Niclas Hedhman wrote: > On Wed, Mar 30, 2011 at 5:48 AM, Jason Pratt<[email protected]> wrote: >> please don't release anything with failures. i've been a big fan/user of >> jini since it was released. now that it is alive again via river, a good >> release history will be key to success/survival > > Assume for a second that the failure is related to the SPARC JVM > implementation; For how long do you intend us to hold off a release to > the other 99.9654% of the users, searching for a compatible way to > work around the problem? > > Sometimes, "known bugs" are just that. The "unknown bugs" is in most > cases a longer list, and should that also hold off a release until we > find and correct them? > > I hope I don't come across as too antagonistic... ;-) ... just want > to provide some perspective. Here's a key question for the future. Are there users that need River on SPARC? Do we go on supporting it? Does anyone care enough to make a SPARC development environment available? Patricia
