4. Feature Freeze √ Stable Branch is forked from Mainline √ Regular development resumes on Mainline. √ Avoid major refactorings on Mainline. √ Only bug fixes committed to Stable Branch. √ Bug fixes are cherrypicked from Mainline. √ Inkscape must pass 'make distcheck' String Freeze √ No further string changes allowed on Stable Branch. √ Finalize tutorials to be shipped with release √ Finalize other docs included in the release √ Finalize about screen √ Finalize Release Notes except Known Issues √ Translators work on translations. √ Recruit Release Wardens for Hard Freeze 5. Hard freeze. √ Only Release Wardens can commit to Stable Branch Cherrypick bug fixes from Mainline to Stable Complete any late work under advisement of Wardens Focus on release-critical bug fixing. Finalize all extensions Finalize codebase translations Finalize Known Issues section of Release Notes Finalize packaging scripts Post additional inkscape-0.91-pre*.tar.gz releases Inkscape has completed Feature Freeze and String Freeze, and is now moving to Hard Freeze. Translators, thanks for your efforts. If there are any late translations please coordinate with Jazzynico, and submit them to him for committing. We're down to the wire though so don't delay! Developers, at this point only Josh and I should be committing to the tree. We'll accept patches if they're either a) obviously safe and a useful fix, or b) more complex but fix a particularly severe bug. In either case, please make sure the fix is already applied to the 0.92 branch, and then send Josh and I a backported patch ready to be landed on 0.91. Josh will follow up with our evaluation of blocker bugs. Things actually look to be in fairly good shape. If anyone has a bug they want to raise as a blocker, now's the time to do it! Since we're in a new stage of the release, I'll cut one last pre-release tarball. Bryce P.S. We're also going to need to do some marketing work to publicise the release, and I'm thinking we should establish a formal marketing team. I'll try to organize something soon; if you're interested in joining early, or have ideas to consider in the meantime, please shoot me an email. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg... _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Johan, What are your reservations about removing it? What are your reservations about naming it something aside from Beta? Are you planning to change it but want users to have it available in the interim? Cheers, Josh On Thu, Nov 20, 2014 at 11:42 AM, Johan Engelen <jbc.engelen@...2592...> wrote: > This is good news. > However, PowerStroke's "CubicBezierJohan" issue still stands. We either > have to remove it for now, or we should rename this to > "CubicBezierBeta"? (In the UI, and also in the XML representation) > > thanks, > Johan > > > On 20-11-2014 9:18, Bryce Harrington wrote: >> 4. Feature Freeze √ Stable Branch is forked from Mainline >> √ Regular development resumes on Mainline. >> √ Avoid major refactorings on Mainline. >> √ Only bug fixes committed to Stable Branch. >> √ Bug fixes are cherrypicked from Mainline. >> √ Inkscape must pass 'make distcheck' >> String Freeze √ No further string changes allowed on Stable Branch. >> √ Finalize tutorials to be shipped with release >> √ Finalize other docs included in the release >> √ Finalize about screen >> √ Finalize Release Notes except Known Issues >> √ Translators work on translations. >> √ Recruit Release Wardens for Hard Freeze >> >> 5. Hard freeze. √ Only Release Wardens can commit to Stable Branch >> Cherrypick bug fixes from Mainline to Stable >> Complete any late work under advisement of Wardens >> Focus on release-critical bug fixing. >> Finalize all extensions >> Finalize codebase translations >> Finalize Known Issues section of Release Notes >> Finalize packaging scripts >> Post additional inkscape-0.91-pre*.tar.gz releases >> >> >> Inkscape has completed Feature Freeze and String Freeze, and is now >> moving to Hard Freeze. >> >> Translators, thanks for your efforts. If there are any late >> translations please coordinate with Jazzynico, and submit them to him >> for committing. We're down to the wire though so don't delay! >> >> Developers, at this point only Josh and I should be committing to the >> tree. We'll accept patches if they're either a) obviously safe and a >> useful fix, or b) more complex but fix a particularly severe bug. >> In either case, please make sure the fix is already applied to the 0.92 >> branch, and then send Josh and I a backported patch ready to be landed >> on 0.91. >> >> Josh will follow up with our evaluation of blocker bugs. Things >> actually look to be in fairly good shape. If anyone has a bug they want >> to raise as a blocker, now's the time to do it! >> >> Since we're in a new stage of the release, I'll cut one last >> pre-release tarball. >> >> Bryce >> >> >> P.S. We're also going to need to do some marketing work to publicise the >> release, and I'm thinking we should establish a formal marketing team. >> I'll try to organize something soon; if you're interested in joining >> early, or have ideas to consider in the meantime, please shoot me an >> email. >> >> >> >> >> ------------------------------------------------------------------------------ >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> with Interactivity, Sharing, Native Excel Exports, App Integration & more >> Get technology previously reserved for billion-dollar corporations, FREE >> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg... >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg... > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

On Thu, Nov 20, 2014 at 1:11 PM, Johan Engelen <jbc.engelen@...2592...> wrote: > If we keep it in: I'm all for another name. It is just a suggestion from the > technical creator. If people have other ideas, that'd be great. Technically, > (iirc), the parameter sets the 'beta' for the whole curve. If kept in and the SVG name changes, doesn't that break it for the previous users?

> A potential problem is that it is the only interpolator that needs a > parameter. If we create another interpolator that needs a parameter, I'm not > sure if the current thing is set up well for that. So additional parameters aren't really future-proof? Would that be for the beta type or any other existing/future interpolators?

Hi, We need to decide what to do about a whole set of bugs brought on by the current behavior when changing inkscape:document-unit.[1] In 0.48 this attribute only effected what values were shown in the GUI. All values inside the SVG file were still stored as 'user-units' ('px' in CSS styles). In 0.91 changing inkscape:document-unit form the 'Page' tab of the Document Properties dialog changes the 'viewBox' and attempts to change all the length units inside the SVG file (rectangle width/height, etc.) to match. I can see how this could be useful but it is incredibly difficult to do right as illustrated by the number of bugs reported (and the many more I am sure have not been reported, think, for example of all the length values inside filters). Question: How easy would it be to revert back to the 0.48 behavior for 0.91? Tav [1] http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape:_Document_Unit_...

On Thu, 2014-11-20 at 22:05 +0100, Johan Engelen wrote: > FYI: I just had a friend upgrade to trunk to get the 0.91 unit behavior. > He actually needs this for work to do a very accurate technical design. > In other words: the viewBox change is /awesome/. It is very unfortunate > that there are bugs related to it. But backing-off completely is a huge > step back. Including the viewBox IS awesome. I don't want to get rid of this part. What I want to suppress is changing the ratio between the SVG height/width and viewBox once the document is created which is what happens when the unit identifier is changes. It is this change that causes problems. > I thought most annoying bugs are related to changing the units for an > existing document. Is that correct? If so, all we have to do is warn > people about that, e.g. with an extra dialog telling people that > changing document unit only works for fresh documents or 0.91 documents. > Documents from earlier versions of Inkscape may have troubles. 0.91 documents don't work either once you've put in things like clips, filters, symbols etc. This is seriously broken. Changing units on a fresh document does work but then one can use the Generic Template to get whatever SVG unit you want.

On Thu, 2014-11-20 at 22:05 +0100, Johan Engelen wrote: > I thought most annoying bugs are related to changing the units for an > existing document. Is that correct? If so, all we have to do is warn > people about that, e.g. with an extra dialog telling people that > changing document unit only works for fresh documents or 0.91 documents. > Documents from earlier versions of Inkscape may have troubles. 0.91 documents don't work either once you've put in things like clips, filters, symbols etc. This is seriously broken. Changing units on a fresh document does work but then one can use the Generic Template to get whatever SVG unit you want.

FYI: I just had a friend upgrade to trunk to get the 0.91 unit behavior. He actually needs this for work to do a very accurate technical design. In other words: the viewBox change is /awesome/. It is very unfortunate that there are bugs related to it. But backing-off completely is a huge step back. I thought most annoying bugs are related to changing the units for an existing document. Is that correct? If so, all we have to do is warn people about that, e.g. with an extra dialog telling people that changing document unit only works for fresh documents or 0.91 documents. Documents from earlier versions of Inkscape may have troubles.

I'm afraid we will run into the exact same problems when we postpone this change to the next release. My intuition tells me that there is no general way to properly upgrade a "broken" Inkscape pre-0.91 document that works in all cases. But I may be wrong of course.

-Johan On 20-11-2014 21:09, Tavmjong Bah wrote: >Hi, > >We need to decide what to do about a whole set of bugs brought on by the >current behavior when changing inkscape:document-unit.[1] In 0.48 this >attribute only effected what values were shown in the GUI. All values >inside the SVG file were still stored as 'user-units' ('px' in CSS >styles). In 0.91 changing inkscape:document-unit form the 'Page' tab of >the Document Properties dialog changes the 'viewBox' and attempts to >change all the length units inside the SVG file (rectangle width/height, >etc.) to match. I can see how this could be useful but it is incredibly >difficult to do right as illustrated by the number of bugs reported (and >the many more I am sure have not been reported, think, for example of >all the length values inside filters). > >Question: How easy would it be to revert back to the 0.48 behavior for >0.91? > >Tav > >[1] >http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape:_Document_Unit_Change > > >

Hi, We need to decide what to do about a whole set of bugs brought on by the current behavior when changing inkscape:document-unit.[1] In 0.48 this attribute only effected what values were shown in the GUI. All values inside the SVG file were still stored as 'user-units' ('px' in CSS styles). In 0.91 changing inkscape:document-unit form the 'Page' tab of the Document Properties dialog changes the 'viewBox' and attempts to change all the length units inside the SVG file (rectangle width/height, etc.) to match. I can see how this could be useful but it is incredibly difficult to do right as illustrated by the number of bugs reported (and the many more I am sure have not been reported, think, for example of all the length values inside filters). Question: How easy would it be to revert back to the 0.48 behavior for 0.91? Tav [1] http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape:_Document_Unit_...

Is "Default units" a misnomer if people can change unit widgets for the document in other places? Cheers, Josh On Fri, Nov 21, 2014 at 11:14 AM, Johan Engelen <jbc.engelen@...2592...> wrote: > I just noticed the option is still called "Default units". I thought I > mentioned this before, but it should really be renamed to "Document > units". "Default units" is a huge misnomer. > > - Johan > > > On 20-11-2014 21:09, Tavmjong Bah wrote: >> Hi, >> >> We need to decide what to do about a whole set of bugs brought on by the >> current behavior when changing inkscape:document-unit.[1] In 0.48 this >> attribute only effected what values were shown in the GUI. All values >> inside the SVG file were still stored as 'user-units' ('px' in CSS >> styles). In 0.91 changing inkscape:document-unit form the 'Page' tab of >> the Document Properties dialog changes the 'viewBox' and attempts to >> change all the length units inside the SVG file (rectangle width/height, >> etc.) to match. I can see how this could be useful but it is incredibly >> difficult to do right as illustrated by the number of bugs reported (and >> the many more I am sure have not been reported, think, for example of >> all the length values inside filters). >> >> Question: How easy would it be to revert back to the 0.48 behavior for >> 0.91? >> >> Tav >> >> [1] >> http://wiki.inkscape.org/wiki/index.php/Units_In_Inkscape:_Document_Unit_...

On Fri, Nov 21, 2014 at 12:09 PM, Johan Engelen <jbc.engelen@...2592...> wrote: > So this is what confuses me then perhaps? > People want it to work as setting the default unit for the UI? If I'm not mistaken, that is all it did in 0.41-0.48.5.

On 22-11-2014 19:24, Johan Engelen wrote: > On 21-11-2014 21:17, Josh Andler wrote: >> On Fri, Nov 21, 2014 at 12:09 PM, Johan Engelen >> <jbc.engelen@...2592...> wrote: >>> So this is what confuses me then perhaps? >>> People want it to work as setting the default unit for the UI? >> If I'm not mistaken, that is all it did in 0.41-0.48.5. > Ok, so shall I then disable the change to viewbox upon Default unit change? > It is pretty straightforward to do. See rev. 13748 in trunk. -J ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg... _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

I think it might be worth back porting the procedural templates that are in trunk. This certainly would be a huge cleanup of the templates under 'File->New->Templates' and would allow one to choose in many cases the default document unit when the new file is created (something that is suppose to be a highlight of this release). Please compare the list of templates between trunk and 0.91. The only possible disadvantage of back porting is the need to translate the new templates.

On Sat, Nov 22, 2014 at 08:21:10PM +0100, Tavmjong Bah wrote: > > Thanks Johan, > > I hope this works as it would really move us closer to a release. This > exactly the solution I was hoping for. > > I've found a rather nasty bug if units are changed to 'meters' and back > but maybe it won't matter in 0.91 with the change you've made. What was the issue?

I hadn't turned up issues with my own testing yesterday, but it's not surprising that suv was able to do so. :) Note the following does not happen in unpatched 0.91. With patched 0.91, behavior is incorrect in the following scenario: 1) Launch patched 0.91.x with default new prefs (default new doc) 2) Open Document Properties, change Default units to mm 3) Draw a rect, then change the size numerically in the Rectangle Tool Controls bar to something round like 100x100 (ruler will show it's not as expected) 4) Switch to Selector Tool and look at the width and height in the Controls Bar Symptoms: The rect is nowhere near the correct size on canvas. The rectangle tool reports a different size than selector tool & rulers. It does appear that the root issue happens in trunk as well (it manifests differently though as the scaling looks to be off in the other direction). In Trunk for step 2 switch to px instead. It seems like this issue is probably worth looking into since it exists in both branches (0.91 possibly just papered over) and could be rectangle tool specific. Cheers, Josh On Sat, Nov 22, 2014 at 10:44 AM, Josh Andler <scislac@...400...> wrote: > Thanks for looking into this. I will do some tests, apply it against > my copy of 0.91.x, do the same tests again, and report back. > > Cheers, > Josh > > On Sat, Nov 22, 2014 at 10:40 AM, Johan Engelen > <jbc.engelen@...2592...> wrote: >> On 22-11-2014 19:24, Johan Engelen wrote: >>> On 21-11-2014 21:17, Josh Andler wrote: >>>> On Fri, Nov 21, 2014 at 12:09 PM, Johan Engelen >>>> <jbc.engelen@...2592...> wrote: >>>>> So this is what confuses me then perhaps? >>>>> People want it to work as setting the default unit for the UI? >>>> If I'm not mistaken, that is all it did in 0.41-0.48.5. >>> Ok, so shall I then disable the change to viewbox upon Default unit change? >>> It is pretty straightforward to do. >> >> See rev. 13748 in trunk. >> >> -J >> >> ------------------------------------------------------------------------------ >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> with Interactivity, Sharing, Native Excel Exports, App Integration & more >> Get technology previously reserved for billion-dollar corporations, FREE >> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg... >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel

String Freeze √ No further string changes allowed on Stable Branch. √ Finalize tutorials to be shipped with release

√ Finalize other docs included in the release √ Finalize about screen √ Finalize Release Notes except Known Issues √ Translators work on translations. √ Recruit Release Wardens for Hard Freeze

Masato Hashimoto <cabezon.hashimoto@...400...> a écrit : >Bryce Harrington <bryce@...961...> wrote: >> String Freeze √ No further string changes allowed on Stable Branch. I agree that we should not change existing string so that we don't break existing translations, but is it still ok to add missing strings? I'm referring to Bug #1388916 "There seem to be untranslatable strings in MapSymbolsNPS.svg" (https://bugs.launchpad.net/inkscape/+bug/1388916).

>> √ Finalize tutorials to be shipped with release >Tutorial of Tracing-pixcelart is incomplete yet. >Descriptions of the GUI are already obsolete. > Although it's not listed in 0.91-tutorial-review[1], it appears in Help > Tutorials. Thanks for the reminder, Masato. I'm going to work on the documentation files (tutorials, man pages and Keys and mouse reference) next week and generate updated SVG versions. While I'm at it, I'll try to fix the Pixelart tutorial. Of course it would be great if someone with very good English skills could help (the minimum would be to review my changes...).

As a translator, I'd like to be decided it asap:)

Traceing-pixelart tutorial is a brand-new tutorial for 0.91. And current it describes about non-existent GUI.

IMHO, we have two options for it which include it in 0.91 or not (in 0.91.1).

"What connection should I keep?" isn't existent current GUI (and was existent past revision, afair).

> I would suggest if there are changes to the english versions of the > documentations, to hold those for 0.91.1, and focus on just getting the > existing versions translated. We probably only have a week or two left > for this work. > > Bryce Traceing-pixelart tutorial is a brand-new tutorial for 0.91. And current it describes about non-existent GUI.

IMHO, we have two options for it which include it in 0.91 or not (in 0.91.1).

Since we're in a new stage of the release, I'll cut one last pre-release tarball.

P.S. We're also going to need to do some marketing work to publicise the release, and I'm thinking we should establish a formal marketing team. I'll try to organize something soon; if you're interested in joining early, or have ideas to consider in the meantime, please shoot me an email.

4. Feature Freeze √ Stable Branch is forked from Mainline √ Regular development resumes on Mainline. √ Avoid major refactorings on Mainline. √ Only bug fixes committed to Stable Branch. √ Bug fixes are cherrypicked from Mainline. √ Inkscape must pass 'make distcheck' String Freeze √ No further string changes allowed on Stable Branch. √ Finalize tutorials to be shipped with release √ Finalize other docs included in the release √ Finalize about screen √ Finalize Release Notes except Known Issues √ Translators work on translations. √ Recruit Release Wardens for Hard Freeze

Inkscape has completed Feature Freeze and String Freeze, and is now moving to Hard Freeze. Translators, thanks for your efforts. If there are any late translations please coordinate with Jazzynico, and submit them to him for committing. We're down to the wire though so don't delay! Developers, at this point only Josh and I should be committing to the tree. We'll accept patches if they're either a) obviously safe and a useful fix, or b) more complex but fix a particularly severe bug. In either case, please make sure the fix is already applied to the 0.92 branch, and then send Josh and I a backported patch ready to be landed on 0.91. Josh will follow up with our evaluation of blocker bugs. Things actually look to be in fairly good shape. If anyone has a bug they want to raise as a blocker, now's the time to do it! Since we're in a new stage of the release, I'll cut one last pre-release tarball. Bryce P.S. We're also going to need to do some marketing work to publicise the release, and I'm thinking we should establish a formal marketing team. I'll try to organize something soon; if you're interested in joining early, or have ideas to consider in the meantime, please shoot me an email. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg... _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel