On 2014-04-10 24:01 +0100, Krzysztof Kosiński wrote:
> I would like to push out Inkscape 0.48.5 in the very near future (1-2
> weeks at most), since a fair number of bugfixes have accumulated since
> the last stable release 15 months ago.
>
> If you know of any simple bugs that can be fixed by backporting a few
> lines of code, please tag them with "backport-proposed" in the
> Launchpad bug tracker, so that I can fix them.
>
> I could use some assistance with the following:
> 1. Writing release notes
> 2. Making binary packages for Windows and OSX
> 3. Announcing the release on the website and mailing lists
>
> Anyone wants to help?
Re OSX:
the currently available packaging scripts are outdated and fail on Mac
OS X 10.6 Snow Leopard and later versions of OS X. See also:
<http://wiki.inkscape.org/wiki/index.php/Notes_on_Packaging_for_OS_X>
Possibly of interest:
During the past months I have attempted to rewrite parts of the existing
scripts to support creating a GTK+/Quartz based application bundle for
trunk (0.91):
<https://code.launchpad.net/~suv-lp/inkscape/osxmenu>
A backport to stable 0.48.x is here:
<https://code.launchpad.net/~suv-lp/inkscape/osxmenu-0.48.x>
Teaser screenshot of latest stable build earlier today:
<https://dl.dropboxusercontent.com/u/65084033/irc/stable-osxmenu-1.png>
Both branches (and the available packages) have to be considered
experimental at this stage:
1) the modified scripts (osx-build.sh and osx-app.sh) have not been
vetted to work on other systems with dependencies installed in different
prefixes: the main goal for now was to be able to produce working,
self-containted relocatable application bundles which support (almost)
as many features as installs on other platforms. A lot of necessary
checks, e.g. for OS X and Xcode version (for compiler flags) need to be
updated or added.
2) no updated documentation available about the process itself (from
getting the required dependencies installed to compiling inkscape itself
to creating the application bundle)
3) both branches have changes not only to scripts in 'packaging', but
also in 'src' (for OS integration like global menubar and keyboard
shortcut modifiers, and for relocation support). Since I don't really
code in C/C++ myself, my primary goal was to make the required changes
work as expected (which they do, mostly), but all these changes really
need code review and a lot of help to improve/fix them (avoid mem leaks
etc.). Some features are still pending (due to lack of skills and time).
A summary of open known issues is listed on the branch page:
<https://code.launchpad.net/~suv-lp/inkscape/osxmenu>
Some of the issues I would consider critical for the release of new
GTK+/Quartz based OS X packages (stable or trunk):
<https://code.launchpad.net/bugs/1046068>
<https://code.launchpad.net/bugs/1116468>
<https://code.launchpad.net/bugs/1302627>
<https://code.launchpad.net/bugs/1024344>
Regards, V
P.S: Please note: available packages for testing are currently shared
via my personal Dropbox account (a free one, which has download limits
for shared files). They are (from my point of view) at this stage not
yet ready for wider testing (please don't post the dropbox links
elsewhere, thx). Clayton Walker, Andy Fitzsimon and Michael New have
been testing trunk builds on OS X Mavericks and provide(d) very helpful
feedback.
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1794...s.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel