Hard Freeze for 0.91
by Bryce Harrington
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.
8 years, 4 months
inkscape-0.91pre4 source tarball
by Bryce Harrington
Download it at:
https://inkscape.org/en/download/
Tagged on the release branch as:
INKSCAPE_0_91_PRE4
This likely is the last pre-release before our official release. There
are a few more remaining changes that Josh and I are aware of, but
nothing to cause undue delay. Hopefully the release will be finalized
within the coming week.
Please make sure any bugs you find are properly recorded in the bug
tracker[1]. If you find particularly serious issues, please also make
sure the issue (and any work-arounds) are detailed in our Release
Notes[2], and hopefully we can tackle them in future point releases.
Packagers, if you haven't already I recommend using this release as an
opportunity to try out the new package upload system on the main
website. Make sure to set your uploads as Mirrored, so we can start
utilizing the new mirroring service. Please see Martin's tutorial
posted on Dec 31st, and contact him directly if you need permissions or
help uploading.
One of the major remaining tasks we have is to write up release
announcements. The drafts are being developed here:
http://wiki.inkscape.org/wiki/index.php?title=AnnouncePlanning091
It needs formal and informal announcements written. To see what we need
to make it look like, see:
http://wiki.inkscape.org/wiki/index.php?title=AnnouncePlanning046
In particular we'll need to identify a few volunteers to send the
notices out. I can take care of a portion of the notifications but
there's quite more to do than I'll have time for, and so would
appreciate any help.
Bryce
1: https://bugs.launchpad.net/inkscape/
2: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91#Known_issues
8 years, 4 months
Re: [Inkscape-devel] Inkscape-0.91pre3 Windows builds
by the Adib
Johan,
if you confirm that the win64 binary 0.91pre4 on sourceforge is fine. (take
the ...win64.7z)
Then please upload the provided cairo files to the devlibs64 on launchpad.
Best regards,
Adib.
--
On Tue, Jan 20, 2015 at 10:05 PM, Johan Engelen <jbc.engelen@...2592...>
wrote:
> I did not build the devlibs.
>
> -Johan
>
>
> On 20-1-2015 20:53, the Adib wrote:
>
> Johan,
>
> if you build the devlibs and you use the same compiler version as
> described I will be happy to recompile using your libs. I am afraid in
> mixing libs created using different gcc versions.
>
> Also could you pls doublecheck if there is any other library where dll
> and lib/include mismatch.
>
> Regards,
>
> Adib
>
> Am Dienstag, 20. Januar 2015 schrieb Johan Engelen :
>
>> Sorry for the problems.
>>
>> -Johan
>>
>>
>>
>> On 20-1-2015 20:17, the Adib wrote:
>>
>> I published the windows binaries on sourceforge. The win64 ones contains
>> the cairo lirary provided by Partha.
>>
>> Within the next few days I can only check my mails rarely.
>>
>>
>> Best regards,
>>
>>
>> Adib.
>>
>> Am Montag, 19. Januar 2015 schrieb the Adib :
>>
>>> I just replaced the dll on my computer with the given dlls:
>>> - pdf reports cairo 1.14.1
>>> - there is no crash for printing
>>>
>>>
>>> So far this looks promising :-)
>>>
>>> I do not know how abi compatible gcc4.9 and gcc4.8 are, Partha do you
>>> have any chance to recompile using gcc4.9 sjlj (as mentioned here
>>> http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit
>>> )
>>>
>>> Many thanks.
>>>
>>> Best regards,
>>>
>>> Adib.
>>> --
>>>
>>>
>>>
>>> On Sun, Jan 18, 2015 at 10:42 PM, Partha Bagchi <partha1b@...400...>
>>> wrote:
>>>
>>>> I have rebuilt cairo from git (cloned today). If someone can help me
>>>> put the files in devlibs, it would be much appreciated.
>>>>
>>>> http://www.partha.com/temp/cairo-git.7z
>>>>
>>>> Built with gcc 4.8.1 sjlj 64bit.
>>>>
>>>> Thanks,
>>>> Partha
>>>>
>>>> On Sun, Jan 18, 2015 at 3:07 PM, su_v <suv-sf@...58...>
>>>> wrote:
>>>> > Independent of how the devlibs64 arrived at the current inconsistent
>>>> > state - I'd like to remind again that inkscape (trunk, 0.91.x) with
>>>> > unpatched cairo 1.14.0 is quite unstable (random crashes with data
>>>> > loss). So before the missing files get committed to
>>>> inkscape-devlibs64,
>>>> > now, I'd recommend to thoroughly test a local inkscape build with
>>>> cairo
>>>> > 1.14.0, and patch cairo if needed. For further details, see e.g. this
>>>> > earlier message:
>>>> > http://sourceforge.net/p/inkscape/mailman/message/32980381/
>>>> >
>>>> > Additional notes:
>>>> > AFAIU the cairo bug is not a platform-related crash limited to OS X
>>>> > (some linux distros already include the same patch from cairo git
>>>> master
>>>> > with stable cairo 1.14 packages, others may have bug reports pending
>>>> > with the same patch proposed):
>>>> >
>>>> > - Related cairo bug reports (same backtrace after crash):
>>>> > https://bugs.freedesktop.org/show_bug.cgi?id=85151
>>>> > https://bugs.freedesktop.org/show_bug.cgi?id=85591
>>>> >
>>>> > - Debian:
>>>> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766479
>>>> >
>>>> http://metadata.ftp-master.debian.org/changelogs//main/c/cairo/cairo_1.14...
>>>> > - Fedora:
>>>> > https://bugzilla.redhat.com/show_bug.cgi?id=1152451#c3
>>>> > - Arch Linux:
>>>> > https://bugs.archlinux.org/task/42596
>>>> >
>>>> https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packa...
>>>> >
>>>> >
>>>> > Regards, V
>>>> >
>>>> >
>>>> > On 2015-01-18 20:03 (+0100), Partha Bagchi wrote:
>>>> >> If your runtime is bundled with 1.12.16 and you built against 1.14.0
>>>> >> then how did it function? It should have crashed I think.
>>>> >>
>>>> >> On Sun, Jan 18, 2015 at 1:21 PM, the Adib <theadib@...400...> wrote:
>>>> >>> ok, I see. The package -3 I made with the latest devlibs64
>>>> available.
>>>> >>>
>>>> >>> pls check
>>>> >>>
>>>> http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/change...
>>>> >>>
>>>> >>> This revision #14 stated to update the cairo to version 1.14. But
>>>> it only
>>>> >>> updates the development files.
>>>> >>>
>>>> >>> The file bin/libcairo-2.dll remains untouched.
>>>> >>>
>>>> >>> So we link against cairo 1.14 but the runtime is bundled 1.12.16.
>>>> >>> Remaining is to update the dlls in the bin directory.
>>>> >>>
>>>> >>> Cheers, Adib.
>>>> >>> --
>>>> >>>
>>>> >>>
>>>> >>> On Sun, Jan 18, 2015 at 6:17 PM, su_v <...> wrote:
>>>> >>>>
>>>> >>>> @AdiB: the two most recent 0.91pre3-x64 msi installers (64bit)
>>>> available
>>>> >>>> for download still use cairo 1.12.16 (i.e. a cairo version which is
>>>> >>>> affected by the cairo bug when printing documents with text on
>>>> Windows).
>>>> >>>> Do you use up-to-date inkscape-devlibs64?
>>>> >>>>
>>>> >>>> Installers tested today on Windows 7:
>>>> >>>> 1) inkscape-0.91pre3-x64-2.msi (from 2015-01-04)
>>>> >>>> http://sourceforge.net/projects/inkscape/files/inkscape/0.91pre3/
>>>> >>>> 2) inkscape-0.91pre3-x64-3.msi (from 2015-01-06)
>>>> >>>>
>>>> >>>>
>>>> https://drive.google.com/folderview?id=0ByQpCQ-C8wR2b09fYkRTSVk5bWM&usp=s...
>>>> >>>>
>>>> >>>> Steps to determine the cairo version used by installed Inkscape:
>>>> >>>> 1) open a new document in currently installed Inkscape 0.91pre3
>>>> >>>> 2) save a copy as PS file
>>>> >>>> 3) open PS file in a plain-text editor and look in the comments
>>>> section
>>>> >>>> at the top of the document for the comment starting with
>>>> >>>>
>>>> >>>> %%Creator:
>>>> >>>>
>>>> >>>> This comment shows which cairo version was used by Inkscape for PS
>>>> >>>> export (i.e. on Windows and OS X, which version of cairo is
>>>> bundled with
>>>> >>>> the Inkscape package).
>>>> >>>>
>>>> >>>> Header from PS file created with inkscape-0.91pre3-x64-3.msi:
>>>> >>>>
>>>> >>>> %!PS-Adobe-3.0
>>>> >>>> %%Creator: cairo 1.12.16 (http://cairographics.org)
>>>> >>>> %%CreationDate: Sun Jan 18 17:48:47 2015
>>>> >>>> %%Pages: 1
>>>> >>>> %%DocumentData: Clean7Bit
>>>> >>>> %%LanguageLevel: 2
>>>> >>>> %%DocumentMedia: A4 595 842 0 () ()
>>>> >>>> %%BoundingBox: 79 438 504 471
>>>> >>>> %%EndComments
>>>> >>>>
>>>> >>>>
>>>> >>>> Regards, V
>>>> >>>>
>>>> >>>>
>>>> >>>> On 2015-01-18 14:36 (+0100), the Adib wrote:
>>>> >>>>> Hello Johan,
>>>> >>>>>
>>>> >>>>> Obviously there is a showblocker in the devlibs64: Inkscape
>>>> crashes
>>>> >>>>> while printing text.
>>>> >>>>> https://bugs.launchpad.net/inkscape-devlibs64/+bug/1366250
>>>> >>>>>
>>>> >>>>> Is there a patched cairo source/lib available?
>>>> >>>>> Maybe it is also related if lib and exe use compiler having
>>>> different
>>>> >>>>> exception handling sjlj vs. seh.
>>>> >>>>> Are we sure we have the same exception handling on libs and exe?
>>>> >>>>>
>>>> >>>>> According to the wiki doc we use sjlj compiler:
>>>> >>>>>
>>>> >>>>>
>>>> http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit
>>>> >>>>>
>>>> >>>>> Best regards,
>>>> >>>>>
>>>> >>>>> Adib.
>>>> >>>>> --
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> On Sat, Jan 17, 2015 at 11:15 PM, su_v <...> wrote:
>>>> >>>>>
>>>> >>>>> On 2015-01-17 23:02 (+0100), Partha Bagchi wrote:
>>>> >>>>> > Well, I provided the latest builds of all of gtk+ and
>>>> friends when
>>>> >>>>> I
>>>> >>>>> > updated Cairo to 1.4.0. It's possible only the devlibs from
>>>> May
>>>> >>>>> that I
>>>> >>>>> > provided are in devlibs. If you use pkg-config, you should
>>>> be able
>>>> >>>>> to
>>>> >>>>> > tell which versions of glib/gtk/cairo/poppler etc are used
>>>> in
>>>> >>>>> devlibs.
>>>> >>>>>
>>>> >>>>> Using pkg-config likely won't work - AFAICT the update from
>>>> cairo
>>>> >>>>> 1.12.16 to 1.14.0 in revision 14 of the devlibs64 did not
>>>> include
>>>> >>>>> the
>>>> >>>>> cairo*.pc files:
>>>> >>>>>
>>>> >
>>>>
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.http://p.sf.net/sfu/gigenet
>>
>>
>>
>> _______________________________________________
>> Inkscape-devel mailing listInkscape-devel@...1901...://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>
>>
>>
>
8 years, 4 months
Inkscape-0.91pre3 Windows builds
by Josh Andler
Hey All,
In an unlikely turn of events, we have an OSX package available and
none for Windows yet. Anyone interested in taking this on?
Cheers,
Josh
8 years, 4 months
doxygen document "other directories" is dead link.
by michinari.nukazawa
Hello.
I build doxygen local file documents from a Inkscape source repository.
$doxygen Doxfile
Inkscape "other directories" in this document top, is dead link.
I want to read those.
(document top: ${inkscape local repository}/doxygen/html/index.html )
(other directories: ${inkscape local
repository}/doxygen/html/dirs.html )
What should I do to read it?
Thanks!
8 years, 4 months
Tighten up command line options
by Sebastian Zartner
The command line parameter list of Inkscape is quite long - 44 parameters
to be precise. It splits similar functionality into multiple parameters
while it doesn't offer all possible options. On the other side it offers
some functions, which may be unnecessary or just too complex.
So I suggest to restructure the command line functionality to separate the
actual commands from their parameters. A good example for how that works is
the git command line tool <http://www.git-scm.com/downloads>.
So the commands would be
open
convert
query
version
help
The syntax for 'open' would be
open <file path>
The syntax for 'convert' would be
convert -in=<input file name> -out=<output file name>
[-out-type=<outupt file type>] [-edit=<edit function>]
[-area=drawing|page|<object id>|<x0>:<y0>:<x1>:<y1>] [-id-only]
[-width=<width>] [-height=<height>] [-dpi=<dpi>]
[-vacuum-defs] [-background=<color>] [-text-to-path] [-margin]
[-ignore-filters] [-version=<file type version>]
covering all --export-* parameters and the -vacuum-defs parameter and where
the different --export-<file type> parameters are combined in the optional
-out-type parameter. -edit replaces --verb by allowing to apply different
transformations and filters. (Are there other use cases for --verb than
that?) If -out-type is not defined, the type will be inferred from the
extension of the file name given in -out.
Syntax for 'query' would be
query x|y|width|height|all -in=<input file name> [-id=<object id>]
covering all --query-* parameters.
'version' and 'help' wouldn't have any parameters and do what --version and
--help currently do.
--with-gui, --without-gui, --select, --export-use-hints (rather confusing
than helping) and --verb-list (needs a different implementation, probably
via 'help') and --usage (should be shown in the output of 'help') are
removed as they are not needed anymore.
--print, --export-area-snap, --export-latex and --shell are not listed,
because I'm not sure about their usage.
Usage examples:
inkscape version
inkscape open "/path/to/file"
inkscape help
inkscape query width -in="/path/to/input file" -id=path1234
inkscape convert -in="/path/to/input file"
-out="/path/to/output file" -edit=grayscale,move(1.0 1.0)
-vacuum-defs
Sebastian
8 years, 4 months
Team cleanup for inkscape-web
by Martin Owens
Hey Devels,
I'm going to do a bit of cleaning on inkscape-web's admin team, anyone
who joined before 2013, I'll set to expire in 6 months with the aim of
clearing out people who aren't interested in a renewal. Hopefully some
people will renew.
https://launchpad.net/~inkscape-webadmin/+members
Any issues anyone can see with this plan?
Best Regards, Martin Owens
8 years, 4 months
