Thanks for your feedback. Have now committed a new copy of the file with a brief introduction, and links to 9 bugs:
http://scm.dspace.org/trac/dspace/browser/dspace/trunk/dspace/KNOWN_BUGS Feel free to add / remove / amend the list of issues. Cheers, Stuart Lewis IT Innovations Analyst and Developer Te Tumu Herenga The University of Auckland Library Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand Ph: 64 9 373-7599 x81928 http://www.library.auckland.ac.nz/ On 27/02/2010, at 12:27 AM, Tim Donohue wrote: > Graham's idea sounds logical to me as well. Note a few known bugs that we've > decided to reschedule for a subminor release (e.g. scheduled for 1.6.1, and > not yet resolved for 1.6.0). In addition we should definitely provide a link > back to the JIRA page for all bugs for that release. > > - Tim > > On Fri, Feb 26, 2010 at 3:17 AM, Graham Triggs <grahamtri...@gmail.com> wrote: > > I don't think auto populating it from JIRA would be useful - at any one time, > there may be lots of minor known bugs. But if they weren't largely > inconsequential, you would think we would choose to postpone a new release > until they are fixed. > > Of course, there may be exceptions to that, but then if we were releasing > with a known significant issue (ie. this definitely doesn't work on Oracle, > or with JDK 7, etc.), then that's the time we would want to put it in > KNOWN_BUGS - but we wouldn't want that drowned by all the inconsequential > issues. > > My vote would be to keep it, but mostly empty apart from significant > (compatibility) issues that we need to draw attention to, and a link to JIRA > for all the bugs marked as affecting that release (which has the benefit of > being up to date with any bugs found after the release). > > G > > On 26 February 2010 00:39, Stuart Lewis <s.le...@auckland.ac.nz> wrote: > Hi, > > As we get ready to release 1.6 final, I thought I'd ask about our KNOWN_BUGS > file that gets included with the download: > > http://scm.dspace.org/trac/dspace/browser/dspace/trunk/dspace/KNOWN_BUGS > > Now we have JIRA, does this still server a purpose? Should we populate it > with all open JIRA issues? Does anyone ever read it? > > Thoughts appreciated. > > Cheers, > > > Stuart Lewis > IT Innovations Analyst and Developer > Te Tumu Herenga The University of Auckland Library > Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand > Ph: 64 9 373-7599 x81928 > http://www.library.auckland.ac.nz/ > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
