Thanks Bryce,

As discussed on IRC, I'm taking the backport-proposed list off your
hands: https://bugs.launchpad.net/inkscape/+bugs?field.tag=backport-pro
posed

And I might be able to run the screen contest. So long as I don't step
on Josh's toes and I can get (or we already have) password for the
inkscape group on deviantArt. (or Josh if you can make me co-owner of
the group)

Best Regards, Martin Owens

On Tue, 2016-10-04 at 18:06 -0700, Bryce Harrington wrote:
> A number of different things need to be done to get the release out
> the
> door, but presently these are the top priorities:
>
>   1.  Packaging for Windows and OSX - Has anyone taken a shot at
> doing
>       Windows or OSX packaging for the snapshot releases?  I'm
> worried
>       when we get to the point of doing the release announcement, we
> may
>       not have packages supporting all platforms.  I would be ok if
> we
>       end up having the initial release be Linux-only but I know most
>       people would be disappointed if we don't have simultaneous
>       platform support.
>
>       *** We need volunteers to work on/coordinate packaging for each
> of
>           these platforms.  If no volunteers are available then we'll
>           drop that platform from the release announcement plans.
>
>   2.  DPI Scaling bug #1389723 - This appears to be the last serious
>       regression that really *has* to be fixed for the release.  Good
>       news is that there is already a proposed fix and a plan in
> place
>       for resolving it.  There is no named assignee, although several
>       people have been working on it.  But right now it needs more
> eyes
>       to review and test it, with a particular look at usability and
> how
>       the fix will be accepted by affected users.
>
>       *** We need a core developer to take a coordinational role for
>           this bug and help shepherd the proposed patches to a
>           resolution.  No particular experience with the problem is
>           needed, just available time to test, track remaining
> issues,
>           and chase down people to address them.
>
>   3.  Disable unstable features, bug #1589340 - I've landed most of
> the
>       proposed changes, but there is one more to do (comment #11,
>       essentially re-introduce the fix for bug #619903).
>
>       *** We need someone to apply the fix for bug #619903 to the
> 0.92
>           branch.  If no volunteers are available, then I'll take
> care
>           of it when I get some time.
>
>   4.  Fonts not shown in font manager (Win32), bug #1416674 - This
>       is platform-specific on Windows but appears to be relatively
> bad
>       for folks.  Its not a 0.92 regression but was a regression on
>       0.91.  Unfortunately there doesn't seem to be a clear path to a
>       fix, and we do not have an assignee for the bug.
>
>       *** We need someone to record this bug as a Known Issue in the
>           release notes.
>       *** We need a skilled developer to investigate the bug,
> identify a
>           solution, and volunteer to be the assignee for the bug.  If
> no
>           volunteers are available, I'll drop this as a release
> blocker.
>
>   5.  About screen - Josh and Martin were coordinating work on a
> contest
>       here, but I don't think it got kicked off.  I understand Josh
> has
>       been quite tied up with other issues, so perhaps someone could
>       volunteer to assist with the grunt work of getting this off the
>       ground?  I think there's still going to be adequate time to do
> a
>       contest if it gets going soonish but I don't want to delay the
>       release on it; worst case we can just rev the number on 0.91's
>       about screen.
>
>       *** We need someone to volunteer to assist here, or possibly to
>           take over the task of organizing the contest.
>       *** We need someone to meanwhile rev the current about screen
>           number to 0.92, in case the contest can't be done.
>
>
>   6.  The Release Notes look pretty good, but as we near to the
> release
>       we need to finish reviewing and copyediting, and make sure all
> new
>       features are adequately described:
>
>       http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92
>
>
>   7.  New snapshot release - I've been procrastinating on this since
> I'm
>       not sure anyone's actually packaging them, but I'll try and get
>       another one out soon.
>
>
> I'll followup on these items some time next week, so if you can
> volunteer for any of the above items by then please do so, else we'll
> have to start going with the plan B's one some of them.
>
> Bryce
>
>
>
>
> #   Period           Tasks                                           
>       
> -------------------------------------------------------------------
> -------------
> √1.  Open development.
>                      √ Implement new build system
>                      √ Begin switching packaging to use new build
> system
>
> 2.  Chill.           √ Development focuses on wrapping up
>                      √ Post inkscape-0.92-pre0.tar.gz
>                      √ Disable features that aren't finished
>                      √ Identify 'make distcheck' issues
>                      √ Identify remaining writing needed for Release
> Notes.
>                      √ Identify any release blocker bugs [scislac]
>                      √ Recruit Release Wardens for Hard Freeze
>
> 3.  Frost.           √ Only production-ready code committed to
> Mainline
>                        Finalize any major changes to platform
> packaging
>                        Inkscape must pass 'make distcheck'
>                      √ Finalize Release Notes except Known Issues
>                        Start an About Screen contest
>                      √ Post additional inkscape-0.92-pre*.tar.gz
> releases
>                        Packagers test creating pkgs of the -pre*
> releases
>
> 4.  Freeze.          √ Stable Branch is forked from Mainline
>                      √ Regular development resumes on Mainline.
>                        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.
>     String Freeze    √ No further string changes allowed on Stable
> Branch.
>                      √ Translators work on translations.
>                      √ Finalize all extensions
>                      √ Finalize codebase translations
>                        Finalize about screen
>                        Finalize Known Issues section of Release Notes
>                        Finalize packaging scripts
>                        Post additional inkscape-0.92-pre*.tar.gz
> releases
>
> 5.  Release.           Post inkscape-0.92.tar.gz to website launchpad
> project page
>                        Post Windows build, MSI or EXE installer to
> website
>                        Post MacOSX build, dmg installer to website
>                        Make Debian build available in stable ppa or
> distribution archive
>                        Make Fedora build available in stable yum repo
> or distribution archive
>                        Post official announcements
>                        Plan 0.92.1+ release(s), if needed
>
> 6.  Open development.
>
>
>
> -------------------------------------------------------------------
> -----------
> Check out the vibrant tech community on one of the world's most 
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel@...142...ge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...142...ge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel