Hey SUV,
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.
Thanks for all your work with testing, it's amazing.
Martin,
2013/9/19 Martin Owens <doctormo@...400...>:
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?
The 0.49 milestone contains some non-blocking bugs:
On Thu, 2013-09-19 at 15:46 +0200, Krzysztof Kosiński wrote:
The 0.49 milestone contains some non-blocking bugs:
OK that makes a lot of sense. ;-) although 760 bugs is probably a pipe dream, there's no way we have that sort of economic power available. But I guess we can attack the high priority ones first.
Thanks Krzysztof
Martin,
Well, most of those are fixed. 55 remaining unfixed & targeted to v0.49 [1]
[1] https://bugs.launchpad.net/inkscape/+bugs?field.searchtext=&orderby=-imp...
On 19 September 2013 15:10, Martin Owens <doctormo@...400...> wrote:
On Thu, 2013-09-19 at 15:46 +0200, Krzysztof Kosiński wrote:
The 0.49 milestone contains some non-blocking bugs:
OK that makes a lot of sense. ;-) although 760 bugs is probably a pipe dream, there's no way we have that sort of economic power available. But I guess we can attack the high priority ones first.
Thanks Krzysztof
Martin,
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
On Thu, 2013-09-19 at 15:29 +0100, Alex Valavanis wrote:
Well, most of those are fixed. 55 remaining unfixed & targeted to v0.49 [1]
Where did I leave my brain today.
OK, we're actually doing pretty well. Lots to do, but much more complete. We're holding onto ~720 fixes from 0.48 that doesn't include the already fixes-released fixed regressions or the backports right?
Martin,
Correct :)
* Regressions have no milestone set, so they won't appear in the list. * Anything other "Fix Released" bugs will be targeted to an earlier (stable) milestone e.g., 0.48.4, so they won't be on the list either. * Unreleased backports will have been marked "Fix Committed", with the 0.48.5 milestone.
So yes, 55 unfixed bugs left targetted to 0.49. Note though that
1. Some of those aren't so important (e.g., ones that affect the experimental GTK+ 3 build) and could probably be untargetted 2. There are probably some untargetted bugs that we will want to add to the 0.49 milestone! Probably worth looking through anything that is marked as High importance or "build"/"crash"-tagged bugs too.
AV
On 19 September 2013 15:55, Martin Owens <doctormo@...400...> wrote:
On Thu, 2013-09-19 at 15:29 +0100, Alex Valavanis wrote:
Well, most of those are fixed. 55 remaining unfixed & targeted to v0.49 [1]
Where did I leave my brain today.
OK, we're actually doing pretty well. Lots to do, but much more complete. We're holding onto ~720 fixes from 0.48 that doesn't include the already fixes-released fixed regressions or the backports right?
Martin,
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
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
On Thu, 2013-09-19 at 18:35 +0100, Alex Valavanis wrote:
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.
Very much so. Do we have a bug report for this item or if you think it's worth splitting it into a bunch of reports for different areas of failure?
Martin,
Yep, there are only three: http://goo.gl/V4HrD1. Once they're fixed, we can mark the test suite as a known pass rather than a known fail.
AV
On 19 September 2013 20:52, Martin Owens <doctormo@...400...> wrote:
On Thu, 2013-09-19 at 18:35 +0100, Alex Valavanis wrote:
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.
Very much so. Do we have a bug report for this item or if you think it's worth splitting it into a bunch of reports for different areas of failure?
Martin,
On Thu, Sep 19, 2013 at 06:51:10PM +0200, su_v 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)
Thanks, very handy list.
This shows 17 regression bugs, 4 of which have owners. They look like they have steps to reproduce identified. A few might be wontfix but need some discussion.
Bryce
participants (5)
-
Alex Valavanis -
Bryce Harrington -
Krzysztof Kosiński -
Martin Owens -
su_v