Also, is it reasonable for us to aim to fix all the existing unit tests in time for release? I suspect that most of the issues are quite simple to fix for people who know the relevant chunks of code.
AV
On 19 September 2013 17:51, su_v <suv-sf@...58...> wrote:
On 2013-09-19 15:26 +0200, Martin Owens wrote:
I'm interested in a list of bugs which /should/ be fixed for release, but don't block. Do we have one of those? I couldn't find an existing tag, should we make one?
Basically we want to prioritize the next round of bug fixes so we can get Inkscape more ready for a good 0.49 release.
The milestone page includes most of such reports, as already mentioned by others.
Here's a launchpad search result with a list of regressions introduced by changes in trunk (tagged with 'regression' and milestoned to 0.49 temporarily - the milestone will be removed once the fix is committed to trunk, and the report then closed as 'Fix Released')
(newest reports are at the top - AFAICT the 3 oldest reports at the bottom of the list track regressions introduced in earlier stable releases which would be nice or feasible to address for 0.49)
hth, V
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel