2. Chill. √ Development focuses on wrapping up √ Disable features that aren't finished √ Identify 'make distcheck' issues -----> Identify any critical OSX/Win32 packaging issues Identify remaining writing needed for Release Notes. √ Regressions Bug Hunt: 500 points Update tutorials and other docs

------------------------------------------------------------------------ OSX Packaging Issues ------------------------------------------------------------------------

On Mac, our packaging needs some major renovation. In the past we've had it use Mac's X11 compatibility but our users will have the best installation experience if the installer uses the native Gtk-Quartz functionality.

I'm guessing that pretty much this can copy how GIMP has done it, but the devil's always in the details of course. The challenge is we need to get this done fast - ideally within a month or two - in order for it to not cause the overall schedule to delay.

Would someone be interested and willing to take on this endeavor?

------------------------------------------------------------------------ Windows Packaging Issues ------------------------------------------------------------------------

I didn't get as much feedback on the status of the Windows package for Inkscape, but poking around a bit it looks like the NSI stuff basically works. There are 15 bugs tagged 'win32' and 'packaging', but only 2 of those are high priority and both of those sound more like porting issues than packaging.

However, on our downloads page I notice that we're pointing people offsite to a third party for 64-bit windows packages. We need to be providing 64-bit packages from the official site.

Also, on the download page we offer three different types of windows installers. In the interest of keeping things simple for users and consistent for developers, can we pick one of those three as our official packaging, and merge or drop the other two?

So, the tasks we need done near-term:

* Test creating a Win32 package using the stuff in packaging/win32, and report on whether it "just works" or hits errors.

* What would it take to get our packaging to generate 64-bit packages?

* Is there a reason we should have more than one win32 package? If not, what should we be focusing on?