De : Josh Andler <scislac@...400...> No, there is no plan for 0.48.5 date-wise. If there have been no win32 devlibs regressions since 0.48.4 we could probably move forward soon.

Does anyone know of any other issues that need to be fixed

Committed the stuff from [1] ! (with very slight modifications) Please test again :-) Cheers, Johan On 12-11-2013 13:39, Alex Valavanis wrote: > > Hi All, > > Please can we look into releasing 0.48.5 in the very near future? > 0.48.4 fails to build in Ubuntu Saucy, Ubuntu Trusty and OSX > Mavericks, and anything else that uses current versions of gcc or > clang! > > We have one remaining bug targeted at 0.48.5 [1]. Does anyone know of > any other issues that need to be fixed, or can we quickly address that > one bug and release the binaries? > > Thanks, > > > AV > > [1] https://bugs.launchpad.net/inkscape/+bug/1245722 > > On 31 May 2013 09:19, Nicolas Dufour <nicoduf@...48...> wrote: >> >> Hi, >> >> >>> De : Josh Andler <scislac@...400...> >>> No, there is no plan for 0.48.5 date-wise. If there have been no win32 >>> devlibs regressions since 0.48.4 we could probably move forward soon. >> >> There's one with the new Cairo lib (1.12.14). It fixes some bugs, but is >> considerably slower on some computers. I'm still trying to find out why, but >> if we decide to move forward soon, it could be necessary to revert and use >> the old Cairo lib (1.11.2). >> >> Cheers, >> -- >> Nicolas >> > > ------------------------------------------------------------------------------ > November Webinars for C, C++, Fortran Developers > Accelerate application performance with scalable programming models. > Explore > techniques for threading, error checking, porting, and tuning. Get the > most > from the latest Intel processors and coprocessors. See abstracts and > register > > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.... > > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel >

I'm super focused on replacing 0.48 with 0.49 and a point release feels too much like a surrender. But I can also see getting fixes into that version. On balance I will take no action and trust my esteemed colleges to make the call and commit.

Addendum: Looks like Johan Engelen just did the backport. Thanks Johan! Martin,

On Tue, 2013-11-12 at 21:29 +0000, Alex Valavanis wrote: > Great! > > @Martin - are you planning on taking care of the backport for bug > #166371 yourself, or do you need input from other devs? > > AV > > On 12 November 2013 21:10, Johan Engelen <jbc.engelen@...2592...> wrote: >> Committed the stuff from [1] ! (with very slight modifications) >> Please test again :-) >> >> Cheers, >> Johan >> >> >> On 12-11-2013 13:39, Alex Valavanis wrote: >>> Hi All, >>> >>> Please can we look into releasing 0.48.5 in the very near future? >>> 0.48.4 fails to build in Ubuntu Saucy, Ubuntu Trusty and OSX >>> Mavericks, and anything else that uses current versions of gcc or >>> clang! >>> >>> We have one remaining bug targeted at 0.48.5 [1]. Does anyone know of >>> any other issues that need to be fixed, or can we quickly address that >>> one bug and release the binaries? >>> >>> Thanks, >>> >>> >>> AV >>> >>> [1] https://bugs.launchpad.net/inkscape/+bug/1245722 >>> >>> On 31 May 2013 09:19, Nicolas Dufour <nicoduf@...48...> wrote: >>>> Hi, >>>> >>>> >>>>> De : Josh Andler <scislac@...400...> >>>>> No, there is no plan for 0.48.5 date-wise. If there have been no win32 >>>>> devlibs regressions since 0.48.4 we could probably move forward soon. >>>> There's one with the new Cairo lib (1.12.14). It fixes some bugs, but is >>>> considerably slower on some computers. I'm still trying to find out why, but >>>> if we decide to move forward soon, it could be necessary to revert and use >>>> the old Cairo lib (1.11.2). >>>> >>>> Cheers, >>>> -- >>>> Nicolas >>>> >>> ------------------------------------------------------------------------------ >>> November Webinars for C, C++, Fortran Developers >>> Accelerate application performance with scalable programming models. >>> Explore >>> techniques for threading, error checking, porting, and tuning. Get the >>> most >>> from the latest Intel processors and coprocessors. See abstracts and >>> register >>> >>> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.... >>> >>> _______________________________________________ >>> Inkscape-devel mailing list >>> Inkscape-devel(a)lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >>> > ------------------------------------------------------------------------------ > DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps > OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access > Free app hosting. Or install the open source package on any LAMP server. > Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! > http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.... > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Addendum: Looks like Johan Engelen just did the backport. Thanks Johan! Martin, On Tue, 2013-11-12 at 21:29 +0000, Alex Valavanis wrote: > Great! > > @Martin - are you planning on taking care of the backport for bug > #166371 yourself, or do you need input from other devs? > > AV > > On 12 November 2013 21:10, Johan Engelen <jbc.engelen@...2592...> wrote: > > Committed the stuff from [1] ! (with very slight modifications) > > Please test again :-) > > > > Cheers, > > Johan > > > > > > On 12-11-2013 13:39, Alex Valavanis wrote: > >> > >> Hi All, > >> > >> Please can we look into releasing 0.48.5 in the very near future? > >> 0.48.4 fails to build in Ubuntu Saucy, Ubuntu Trusty and OSX > >> Mavericks, and anything else that uses current versions of gcc or > >> clang! > >> > >> We have one remaining bug targeted at 0.48.5 [1]. Does anyone know of > >> any other issues that need to be fixed, or can we quickly address that > >> one bug and release the binaries? > >> > >> Thanks, > >> > >> > >> AV > >> > >> [1] https://bugs.launchpad.net/inkscape/+bug/1245722 > >> > >> On 31 May 2013 09:19, Nicolas Dufour <nicoduf@...48...> wrote: > >>> > >>> Hi, > >>> > >>> > >>>> De : Josh Andler <scislac@...400...> > >>>> No, there is no plan for 0.48.5 date-wise. If there have been no win32 > >>>> devlibs regressions since 0.48.4 we could probably move forward soon. > >>> > >>> There's one with the new Cairo lib (1.12.14). It fixes some bugs, but is > >>> considerably slower on some computers. I'm still trying to find out why, but > >>> if we decide to move forward soon, it could be necessary to revert and use > >>> the old Cairo lib (1.11.2). > >>> > >>> Cheers, > >>> -- > >>> Nicolas > >>> > >> > >> ------------------------------------------------------------------------------ > >> November Webinars for C, C++, Fortran Developers > >> Accelerate application performance with scalable programming models. > >> Explore > >> techniques for threading, error checking, porting, and tuning. Get the > >> most > >> from the latest Intel processors and coprocessors. See abstracts and > >> register > >> > >> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.... > >> > >> _______________________________________________ > >> Inkscape-devel mailing list > >> Inkscape-devel(a)lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel > >> > > > > ------------------------------------------------------------------------------ > DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps > OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access > Free app hosting. Or install the open source package on any LAMP server. > Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! > http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.... > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

On Tue, 2013-11-12 at 22:32 +0000, Alex Valavanis wrote: > > By the way, is Josh still managing the next release or are you taking > care of this one? Or someone else? I've lost track!

I think Josh is taking some time off, so Bryce or Krzysztof will be leaders this time I believe.

Just for my reference, who else is planning on assisting with the release work, and in what aspects?

On Sun, 2013-12-01 at 20:49 -0800, Bryce Harrington wrote: > Just for my reference, who else is planning on assisting with the > release work, and in what aspects? For 0.49, I'm here. If you have an existing process to follow, I'll be happy to run through it for the release. Martin,

On 2013-12-02 08:20 +0100, Bryce Harrington wrote: > Thanks. Josh and I will get a task list together this week. Sounds > like in the meantime the priority is getting regression bugs analyzed > and resolved. If we haven't already we'll need a burndown list of those > bugs. <http://sourceforge.net/mailarchive/message.php?msg_id=31423493>

On 2013-12-02 23:49 +0100, Bryce Harrington wrote: > On Mon, Dec 02, 2013 at 03:08:33PM +0100, su_v wrote: >> On 2013-12-02 08:20 +0100, Bryce Harrington wrote: >>> Thanks. Josh and I will get a task list together this week. Sounds >>> like in the meantime the priority is getting regression bugs analyzed >>> and resolved. If we haven't already we'll need a burndown list of those >>> bugs. >> >> <http://sourceforge.net/mailarchive/message.php?msg_id=31423493> Pasting the link from that earlier message: List of reports tagged with 'regression' and milestoned to '0.49', sorted by 'newest first': <http://tinyurl.com/o9lq44w> > suv, I notice the subject of the referenced email is "Non-blockers"; > does that imply that the bugs in this list are not deemed to be release > blockers? If that's true, then do we have a shortlist of blocking bugs, > or have those all been resolved already? I didn't choose that thread topic myself… Personally, I think that many (if not most) of the so far known regressions introduced in trunk need to (or ought to) be fixed before a new stable release branch is created. AFAICT the impacts of the recent large merges have not been fully addressed yet (e.g. units, C++ification), and there are a couple of performance, units and precision regressions which would likely affect many users. TBH I somewhat lost track of the current state of ellipse and circle elements (both internally, and what is exposed to the user). Reports which currently have an explicit 'blocker' status (i.e. have the tag 'blocker' added) are listed here (they are excluded from the other search): <https://bugs.launchpad.net/inkscape/+bugs/?field.tag=blocker> > Also, I see that some good thinking has gone into setting priorities for > pretty much all of these bugs, and only a handful are marked High. suv, > do you have an opinion on how we should treat the bug priorities for the > release? I.e., should we focus heaviest on getting the High priority > bugs closed, and not really worry about the low priority ones? Or > should priority be interpreted in some other fashion? Maybe we had been too technically minded in the past when assigning the priorities, roughly based on these criteria: - high: all crashes (unless they occur under very rare circumstances), bugs with the risk of data loos - medium: severe bugs for which workarounds are known, bugs which produce incorrect or unxepected results - low: only occur under rare circumstances, or can be easily worked around, GUI regressions The statuses do not (or rarely) reflect the impact on usability or the bug's level of 'annoyance'. Personally, I had stopped tagging additional reports as 'blocker' a couple of weeks ago (except for two reports, very recently) - it would be great if someone could help with that task (for one thing I do find it rather difficult to decide, after having read too many reactions from bug reporters disagreeing about how bugs have been triaged, and for another thing I don't really like having to decide that for reports I filed myself). @JazzyNico - what's your view? Regards, V ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.... _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

With the number of regressions, do we not want to have a period of freeze or maybe a demi-hemi-freeze to slow down the rate of regression addition and ask for more fixes?

On 2013-12-02 23:49 +0100, Bryce Harrington wrote: > On Mon, Dec 02, 2013 at 03:08:33PM +0100, su_v wrote: > Also, I see that some good thinking has gone into setting priorities for > pretty much all of these bugs, and only a handful are marked High. suv, > do you have an opinion on how we should treat the bug priorities for the > release? I.e., should we focus heaviest on getting the High priority > bugs closed, and not really worry about the low priority ones? Or > should priority be interpreted in some other fashion? Maybe we had been too technically minded in the past when assigning the priorities, roughly based on these criteria: - high: all crashes (unless they occur under very rare circumstances), bugs with the risk of data loos - medium: severe bugs for which workarounds are known, bugs which produce incorrect or unxepected results - low: only occur under rare circumstances, or can be easily worked around, GUI regressions The statuses do not (or rarely) reflect the impact on usability or the bug's level of 'annoyance'.