0.92 release status (volunteers needed)

classic Classic list List threaded Threaded
35 messages Options
12
Reply | Threaded
Open this post in threaded view
|

0.92 release status (volunteers needed)

Bryce Harrington-3
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Martin Owens-2
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
> [hidden email]
> 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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Victor Westmann
Hi there,

I can do my best to try to assist in creating an installer for Windows. I'm a long time Windows user.

1. However I'm not sure I can generate the binaries of the Inkscape on Windows platform (the easiest path, or at least so it seemed at first sight, was to compile Inkscape on Windows through Visual Studio. But it demanded some paid plugin (GDB) to make it work...) myself. Any thoughts on this?

5. Tell me what steps should be taken and I'll try to help. I love these contests. Really good material comes from them almost always. :-)

Let me know how I can be useful for the team.



--Victor Westmann

2016-10-04 19:28 GMT-07:00 Martin Owens <[hidden email]>:
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
> [hidden email]
> 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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Josh Andler
In reply to this post by Martin Owens-2
On Tue, Oct 4, 2016 at 7:28 PM, Martin Owens <[hidden email]> wrote:
> 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)

No toes would be stepped on... I have invited you to be a co-founder
of the "Inkscapers" group on DeviantART. The "Inkscape" one on DA is a
User Account and I can pass on the login info for that. In fact, we
need to get back on the credential sharing stuff to reduce the bus
factor. I'd say if it's possible to run it on the website, it's
probably the way to go as I think it would end up being more inclusive
since there are login methods more friendly than just one like DA has
(plus not needing to manually tally votes).

However, I'm still willing to run it, I just couldn't figure out some
piece of it after you demoed how it should work.

Cheers,
Josh

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Bryce Harrington-3
In reply to this post by Victor Westmann
On Tue, Oct 04, 2016 at 07:43:11PM -0700, Victor Westmann wrote:
> Hi there,
>
> I can do my best to try to assist in creating an installer for Windows. I'm
> a long time Windows user.

Thanks for lending a hand on this.

> 1. However I'm not sure I can generate the binaries of the Inkscape on
> Windows platform (the easiest path, or at least so it seemed at first
> sight, was to compile Inkscape on Windows through Visual Studio. But it
> demanded some paid plugin (GDB) to make it work...) myself. Any thoughts on
> this?

There's a wiki page explaining how to build Inkscape on Windows using
mingw:

    http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows

That should get you more on the right path.  I see it describes
building using cmake, so hopefully the page isn't too out of date.
Don't be shy about updating the page to include more accurate directions
where needed.

I suspect many of the past folks who have done Windows builds in
the past are still around, so also don't be shy about asking for (or
offering) help to anyone else that pops up to work on it.  If you look
at the bzr log for the Windows-specific build files you can identify
specific people worth contacting and their email addresses.

> 5. Tell me what steps should be taken and I'll try to help. I love these
> contests. Really good material comes from them almost always. :-)
>
> Let me know how I can be useful for the team.

Thanks again Victor,
Bryce

> --Victor Westmann
>
> 2016-10-04 19:28 GMT-07:00 Martin Owens <[hidden email]>:
>
> > 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
> > > [hidden email]
> > > 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
> > [hidden email]
> > 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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Victor Westmann
Hi Bryce and team,

Thank you for your kind words.

I struggled a bit to get the source code of Inkscape on my machine so I made sure to reflect actions to be taken when Windows newcomers get to the Wiki.

Will follow it through and as I follow more troubles, and hopefully how to overcome them, I'll write it down in the wiki. :)


Thanks!



--Victor Westmann

2016-10-05 10:01 GMT-07:00 Bryce Harrington <[hidden email]>:
On Tue, Oct 04, 2016 at 07:43:11PM -0700, Victor Westmann wrote:
> Hi there,
>
> I can do my best to try to assist in creating an installer for Windows. I'm
> a long time Windows user.

Thanks for lending a hand on this.

> 1. However I'm not sure I can generate the binaries of the Inkscape on
> Windows platform (the easiest path, or at least so it seemed at first
> sight, was to compile Inkscape on Windows through Visual Studio. But it
> demanded some paid plugin (GDB) to make it work...) myself. Any thoughts on
> this?

There's a wiki page explaining how to build Inkscape on Windows using
mingw:

    http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows

That should get you more on the right path.  I see it describes
building using cmake, so hopefully the page isn't too out of date.
Don't be shy about updating the page to include more accurate directions
where needed.

I suspect many of the past folks who have done Windows builds in
the past are still around, so also don't be shy about asking for (or
offering) help to anyone else that pops up to work on it.  If you look
at the bzr log for the Windows-specific build files you can identify
specific people worth contacting and their email addresses.

> 5. Tell me what steps should be taken and I'll try to help. I love these
> contests. Really good material comes from them almost always. :-)
>
> Let me know how I can be useful for the team.

Thanks again Victor,
Bryce

> --Victor Westmann
>
> 2016-10-04 19:28 GMT-07:00 Martin Owens <[hidden email]>:
>
> > 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
> > > [hidden email]
> > > 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
> > [hidden email]
> > 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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Partha Bagchi
On Windows, you can simply navigate to https://code.launchpad.net/~inkscape.dev/inkscape/trunk -> browse the code -> view rivision
-> download tarball. 

Use 7z to untar. 

This will get you the latest code from launchpad.

HTH,
Partha
 

On Fri, Oct 7, 2016 at 10:18 AM, Victor Westmann <[hidden email]> wrote:
Hi Bryce and team,

Thank you for your kind words.

I struggled a bit to get the source code of Inkscape on my machine so I made sure to reflect actions to be taken when Windows newcomers get to the Wiki.

Will follow it through and as I follow more troubles, and hopefully how to overcome them, I'll write it down in the wiki. :)


Thanks!



--Victor Westmann

2016-10-05 10:01 GMT-07:00 Bryce Harrington <[hidden email]>:
On Tue, Oct 04, 2016 at 07:43:11PM -0700, Victor Westmann wrote:
> Hi there,
>
> I can do my best to try to assist in creating an installer for Windows. I'm
> a long time Windows user.

Thanks for lending a hand on this.

> 1. However I'm not sure I can generate the binaries of the Inkscape on
> Windows platform (the easiest path, or at least so it seemed at first
> sight, was to compile Inkscape on Windows through Visual Studio. But it
> demanded some paid plugin (GDB) to make it work...) myself. Any thoughts on
> this?

There's a wiki page explaining how to build Inkscape on Windows using
mingw:

    http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows

That should get you more on the right path.  I see it describes
building using cmake, so hopefully the page isn't too out of date.
Don't be shy about updating the page to include more accurate directions
where needed.

I suspect many of the past folks who have done Windows builds in
the past are still around, so also don't be shy about asking for (or
offering) help to anyone else that pops up to work on it.  If you look
at the bzr log for the Windows-specific build files you can identify
specific people worth contacting and their email addresses.

> 5. Tell me what steps should be taken and I'll try to help. I love these
> contests. Really good material comes from them almost always. :-)
>
> Let me know how I can be useful for the team.

Thanks again Victor,
Bryce

> --Victor Westmann
>
> 2016-10-04 19:28 GMT-07:00 Martin Owens <[hidden email]>:
>
> > 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
> > > [hidden email]
> > > 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
> > [hidden email]
> > 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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Eduard Braun

Seeing that Victor is still struggling with building and even downloading the code I had a first look at packaging the current 0.92.x branch for Windows myself.
Since I recently joined Nicolas in creating nightly builds and updating devlibs I have a pretty good idea of which files need to be bundled...

  • The .msi installer (via WiX) technically works with my changes from r15100 [1]. A first experimental package is available at [2].
    What has to be done is checking if all files are properly installed and the (individually installable) components have to be checked and adjusted where needed. At the very least locales have changed their location (from /locale to /share/locale)
  • The .exe installer (via NSIS) has a lot more problems (some I already addressed in r15101 [3]) and does not compile yet.
    A large part of the work to be done is probably adjusting file locations. However (if I'm not mistaken) some additional fixes are needed to account for 64-bit builds and path changes due to CMake.

I'd be happy to continue working on this but some help would definitely be welcome!

Regards,
Eduard

[1] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15100
[2] http://download.tuxfamily.org/inkscape/win64/inkscape-0.92pre1-x64.msi
[3] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15101


Am 07.10.2016 um 16:37 schrieb Partha Bagchi:
On Windows, you can simply navigate to https://code.launchpad.net/~inkscape.dev/inkscape/trunk -> browse the code -> view rivision
-> download tarball. 

Use 7z to untar. 

This will get you the latest code from launchpad.

HTH,
Partha
 

On Fri, Oct 7, 2016 at 10:18 AM, Victor Westmann <[hidden email]> wrote:
Hi Bryce and team,

Thank you for your kind words.

I struggled a bit to get the source code of Inkscape on my machine so I made sure to reflect actions to be taken when Windows newcomers get to the Wiki.

Will follow it through and as I follow more troubles, and hopefully how to overcome them, I'll write it down in the wiki. :)


Thanks!



--Victor Westmann

2016-10-05 10:01 GMT-07:00 Bryce Harrington <[hidden email]>:
On Tue, Oct 04, 2016 at 07:43:11PM -0700, Victor Westmann wrote:
> Hi there,
>
> I can do my best to try to assist in creating an installer for Windows. I'm
> a long time Windows user.

Thanks for lending a hand on this.

> 1. However I'm not sure I can generate the binaries of the Inkscape on
> Windows platform (the easiest path, or at least so it seemed at first
> sight, was to compile Inkscape on Windows through Visual Studio. But it
> demanded some paid plugin (GDB) to make it work...) myself. Any thoughts on
> this?

There's a wiki page explaining how to build Inkscape on Windows using
mingw:

    http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows

That should get you more on the right path.  I see it describes
building using cmake, so hopefully the page isn't too out of date.
Don't be shy about updating the page to include more accurate directions
where needed.

I suspect many of the past folks who have done Windows builds in
the past are still around, so also don't be shy about asking for (or
offering) help to anyone else that pops up to work on it.  If you look
at the bzr log for the Windows-specific build files you can identify
specific people worth contacting and their email addresses.

> 5. Tell me what steps should be taken and I'll try to help. I love these
> contests. Really good material comes from them almost always. :-)
>
> Let me know how I can be useful for the team.

Thanks again Victor,
Bryce

> --Victor Westmann
>
> 2016-10-04 19:28 GMT-07:00 Martin Owens <[hidden email]>:
>
> > 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
> > > [hidden email]
> > > 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
> > [hidden email]
> > 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
[hidden email]
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Eduard Braun

Just a quick follow-up:

NSIS creates an installer, too, now. A first experimental package is available at [4].

I fixed it to work for 32bit and 64bit builds as well as btool and cmake builds in r15103 [5]. This also fixes all issues I discovered with NSIS 3.0, so the new version can be used now, too.

[4] http://download.tuxfamily.org/inkscape/win64/Inkscape-0.92pre1-x64-1.exe
[5] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15103

Am 08.10.2016 um 20:22 schrieb Eduard Braun:

Seeing that Victor is still struggling with building and even downloading the code I had a first look at packaging the current 0.92.x branch for Windows myself.
Since I recently joined Nicolas in creating nightly builds and updating devlibs I have a pretty good idea of which files need to be bundled...

  • The .msi installer (via WiX) technically works with my changes from r15100 [1]. A first experimental package is available at [2].
    What has to be done is checking if all files are properly installed and the (individually installable) components have to be checked and adjusted where needed. At the very least locales have changed their location (from /locale to /share/locale)
  • The .exe installer (via NSIS) has a lot more problems (some I already addressed in r15101 [3]) and does not compile yet.
    A large part of the work to be done is probably adjusting file locations. However (if I'm not mistaken) some additional fixes are needed to account for 64-bit builds and path changes due to CMake.

I'd be happy to continue working on this but some help would definitely be welcome!

Regards,
Eduard

[1] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15100
[2] http://download.tuxfamily.org/inkscape/win64/inkscape-0.92pre1-x64.msi
[3] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15101


Am 07.10.2016 um 16:37 schrieb Partha Bagchi:
On Windows, you can simply navigate to https://code.launchpad.net/~inkscape.dev/inkscape/trunk -> browse the code -> view rivision
-> download tarball. 

Use 7z to untar. 

This will get you the latest code from launchpad.

HTH,
Partha
 

On Fri, Oct 7, 2016 at 10:18 AM, Victor Westmann <[hidden email]> wrote:
Hi Bryce and team,

Thank you for your kind words.

I struggled a bit to get the source code of Inkscape on my machine so I made sure to reflect actions to be taken when Windows newcomers get to the Wiki.

Will follow it through and as I follow more troubles, and hopefully how to overcome them, I'll write it down in the wiki. :)


Thanks!



--Victor Westmann

2016-10-05 10:01 GMT-07:00 Bryce Harrington <[hidden email]>:
On Tue, Oct 04, 2016 at 07:43:11PM -0700, Victor Westmann wrote:
> Hi there,
>
> I can do my best to try to assist in creating an installer for Windows. I'm
> a long time Windows user.

Thanks for lending a hand on this.

> 1. However I'm not sure I can generate the binaries of the Inkscape on
> Windows platform (the easiest path, or at least so it seemed at first
> sight, was to compile Inkscape on Windows through Visual Studio. But it
> demanded some paid plugin (GDB) to make it work...) myself. Any thoughts on
> this?

There's a wiki page explaining how to build Inkscape on Windows using
mingw:

    http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows

That should get you more on the right path.  I see it describes
building using cmake, so hopefully the page isn't too out of date.
Don't be shy about updating the page to include more accurate directions
where needed.

I suspect many of the past folks who have done Windows builds in
the past are still around, so also don't be shy about asking for (or
offering) help to anyone else that pops up to work on it.  If you look
at the bzr log for the Windows-specific build files you can identify
specific people worth contacting and their email addresses.

> 5. Tell me what steps should be taken and I'll try to help. I love these
> contests. Really good material comes from them almost always. :-)
>
> Let me know how I can be useful for the team.

Thanks again Victor,
Bryce

> --Victor Westmann
>
> 2016-10-04 19:28 GMT-07:00 Martin Owens <[hidden email]>:
>
> > 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
> > > [hidden email]
> > > 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
> > [hidden email]
> > 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
[hidden email]
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
[hidden email]
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Victor Westmann
Hi Eduard, how do you do?

I will be more than happy to help you (at least to test the software) if I can!

Thank you for your packaged version of the 0.92 pre-release. The installer works like a charm (but, for some reason, it pointed automatically to the x86 folder, which is for 32 bit software only on Windows. But that's fine.

Will test this right now and let you know if something unusual happens. Please let me know how can I help and/or get involved more with the project.

Did a minor edit in the Inkscape Wiki these past days. :)

Cheers!



--Victor Westmann

2016-10-08 17:38 GMT-07:00 Eduard Braun <[hidden email]>:

Just a quick follow-up:

NSIS creates an installer, too, now. A first experimental package is available at [4].

I fixed it to work for 32bit and 64bit builds as well as btool and cmake builds in r15103 [5]. This also fixes all issues I discovered with NSIS 3.0, so the new version can be used now, too.

[4] http://download.tuxfamily.org/inkscape/win64/Inkscape-0.92pre1-x64-1.exe
[5] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15103

Am 08.10.2016 um 20:22 schrieb Eduard Braun:

Seeing that Victor is still struggling with building and even downloading the code I had a first look at packaging the current 0.92.x branch for Windows myself.
Since I recently joined Nicolas in creating nightly builds and updating devlibs I have a pretty good idea of which files need to be bundled...

  • The .msi installer (via WiX) technically works with my changes from r15100 [1]. A first experimental package is available at [2].
    What has to be done is checking if all files are properly installed and the (individually installable) components have to be checked and adjusted where needed. At the very least locales have changed their location (from /locale to /share/locale)
  • The .exe installer (via NSIS) has a lot more problems (some I already addressed in r15101 [3]) and does not compile yet.
    A large part of the work to be done is probably adjusting file locations. However (if I'm not mistaken) some additional fixes are needed to account for 64-bit builds and path changes due to CMake.

I'd be happy to continue working on this but some help would definitely be welcome!

Regards,
Eduard

[1] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15100
[2] http://download.tuxfamily.org/inkscape/win64/inkscape-0.92pre1-x64.msi
[3] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15101


Am 07.10.2016 um 16:37 schrieb Partha Bagchi:
On Windows, you can simply navigate to https://code.launchpad.net/~inkscape.dev/inkscape/trunk -> browse the code -> view rivision
-> download tarball. 

Use 7z to untar. 

This will get you the latest code from launchpad.

HTH,
Partha
 

On Fri, Oct 7, 2016 at 10:18 AM, Victor Westmann <[hidden email]> wrote:
Hi Bryce and team,

Thank you for your kind words.

I struggled a bit to get the source code of Inkscape on my machine so I made sure to reflect actions to be taken when Windows newcomers get to the Wiki.

Will follow it through and as I follow more troubles, and hopefully how to overcome them, I'll write it down in the wiki. :)


Thanks!



--Victor Westmann

2016-10-05 10:01 GMT-07:00 Bryce Harrington <[hidden email]>:
On Tue, Oct 04, 2016 at 07:43:11PM -0700, Victor Westmann wrote:
> Hi there,
>
> I can do my best to try to assist in creating an installer for Windows. I'm
> a long time Windows user.

Thanks for lending a hand on this.

> 1. However I'm not sure I can generate the binaries of the Inkscape on
> Windows platform (the easiest path, or at least so it seemed at first
> sight, was to compile Inkscape on Windows through Visual Studio. But it
> demanded some paid plugin (GDB) to make it work...) myself. Any thoughts on
> this?

There's a wiki page explaining how to build Inkscape on Windows using
mingw:

    http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows

That should get you more on the right path.  I see it describes
building using cmake, so hopefully the page isn't too out of date.
Don't be shy about updating the page to include more accurate directions
where needed.

I suspect many of the past folks who have done Windows builds in
the past are still around, so also don't be shy about asking for (or
offering) help to anyone else that pops up to work on it.  If you look
at the bzr log for the Windows-specific build files you can identify
specific people worth contacting and their email addresses.

> 5. Tell me what steps should be taken and I'll try to help. I love these
> contests. Really good material comes from them almost always. :-)
>
> Let me know how I can be useful for the team.

Thanks again Victor,
Bryce

> --Victor Westmann
>
> 2016-10-04 19:28 GMT-07:00 Martin Owens <[hidden email]>:
>
> > 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
> > > [hidden email]
> > > 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
> > [hidden email]
> > 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
[hidden email]
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
[hidden email]
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
[hidden email]
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Martin Owens-2
In reply to this post by Eduard Braun
Additional Information for Packagers:

If you are building inkscape packages for the release, then you can ask
the website team to increase your quota on the website, allowing you to
upload large files.

When you do, we ask for you to keep an eye on the number of packages
you upload. For a release I'm budgeting ten or so release packages per
major platform. If your platform releases more than that, let me know
so I can assess and purge some of the older files (it has to be done
manually and the webserver's disk isn't huge)

The advantage of using the website is that the costing is consistent,
it's supported by a nice CDN and you can (and we strongly encourage you
to) add gpg signatures (or md5 signatures) to your uploads to give them
some verification that they've not been messed with.

Best Regards, Martin Owens
Inkscape Website

On Sun, 2016-10-09 at 02:38 +0200, Eduard Braun wrote:

> Just a quick follow-up:
> NSIS creates an installer, too, now. A first experimental package is
> available at [4].
> I fixed it to work for 32bit and 64bit builds as well as btool and
> cmake builds in r15103 [5]. This also fixes all issues I discovered
> with NSIS 3.0, so the new version can be used now, too.
> [4] http://download.tuxfamily.org/inkscape/win64/Inkscape-0.92pre1-x6
> 4-1.exe
> [5] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revisio
> n/15103
> Am 08.10.2016 um 20:22 schrieb Eduard Braun:
> > Seeing that Victor is still struggling with building and even
> > downloading the code I had a first look at packaging the current
> > 0.92.x branch for Windows myself.
> > Since I recently joined Nicolas in creating nightly builds and
> > updating devlibs I have a pretty good idea of which files need to
> > be bundled...
> > The .msi installer (via WiX) technically works with my changes from
> > r15100 [1]. A first experimental package is available at [2].
> > What has to be done is checking if all files are properly installed
> > and the (individually installable) components have to be checked
> > and adjusted where needed. At the very least locales have changed
> > their location (from /locale to /share/locale)
> > The .exe installer (via NSIS) has a lot more problems (some I
> > already addressed in r15101 [3]) and does not compile yet.
> > A large part of the work to be done is probably adjusting file
> > locations. However (if I'm not mistaken) some additional fixes are
> > needed to account for 64-bit builds and path changes due to CMake.
> > I'd be happy to continue working on this but some help would
> > definitely be welcome!
> > Regards,
> > Eduard
> > [1] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revis
> > ion/15100
> > [2] http://download.tuxfamily.org/inkscape/win64/inkscape-0.92pre1-
> > x64.msi
> > [3] http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revis
> > ion/15101
> >
> > Am 07.10.2016 um 16:37 schrieb Partha Bagchi:
> > > On Windows, you can simply navigate to https://code.launchpad.net
> > > /~inkscape.dev/inkscape/trunk -> browse the code -> view
> > > rivision 
> > > -> download tarball. 
> > >
> > > Use 7z to untar. 
> > >
> > > This will get you the latest code from launchpad.
> > >
> > > HTH,
> > > Partha
> > >  
> > >
> > > On Fri, Oct 7, 2016 at 10:18 AM, Victor Westmann <victor.westmann
> > > @gmail.com> wrote:
> > > > Hi Bryce and team,
> > > >
> > > > Thank you for your kind words.
> > > >
> > > > I struggled a bit to get the source code of Inkscape on my
> > > > machine so I made sure to reflect actions to be taken when
> > > > Windows newcomers get to the Wiki.
> > > >
> > > > Will follow it through and as I follow more troubles, and
> > > > hopefully how to overcome them, I'll write it down in the wiki.
> > > > :)
> > > >
> > > >
> > > > Thanks!
> > > >
> > > >
> > > >
> > > > --Victor Westmann
> > > >
> > > > 2016-10-05 10:01 GMT-07:00 Bryce Harrington <bryce@bryceharring
> > > > ton.org>:
> > > > > On Tue, Oct 04, 2016 at 07:43:11PM -0700, Victor Westmann
> > > > > wrote:
> > > > > > Hi there,
> > > > > >
> > > > > > I can do my best to try to assist in creating an installer
> > > > > for Windows. I'm
> > > > > > a long time Windows user.
> > > > >
> > > > > Thanks for lending a hand on this.
> > > > >
> > > > > > 1. However I'm not sure I can generate the binaries of the
> > > > > Inkscape on
> > > > > > Windows platform (the easiest path, or at least so it
> > > > > seemed at first
> > > > > > sight, was to compile Inkscape on Windows through Visual
> > > > > Studio. But it
> > > > > > demanded some paid plugin (GDB) to make it work...) myself.
> > > > > Any thoughts on
> > > > > > this?
> > > > >
> > > > > There's a wiki page explaining how to build Inkscape on
> > > > > Windows using
> > > > > mingw:
> > > > >
> > > > >     http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscap
> > > > > e_on_Windows
> > > > >
> > > > > That should get you more on the right path.  I see it
> > > > > describes
> > > > > building using cmake, so hopefully the page isn't too out of
> > > > > date.
> > > > > Don't be shy about updating the page to include more accurate
> > > > > directions
> > > > > where needed.
> > > > >
> > > > > I suspect many of the past folks who have done Windows builds
> > > > > in
> > > > > the past are still around, so also don't be shy about asking
> > > > > for (or
> > > > > offering) help to anyone else that pops up to work on it.  If
> > > > > you look
> > > > > at the bzr log for the Windows-specific build files you can
> > > > > identify
> > > > > specific people worth contacting and their email addresses.
> > > > >
> > > > > > 5. Tell me what steps should be taken and I'll try to help.
> > > > > I love these
> > > > > > contests. Really good material comes from them almost
> > > > > always. :-)
> > > > > >
> > > > > > Let me know how I can be useful for the team.
> > > > >
> > > > > Thanks again Victor,
> > > > > Bryce
> > > > >
> > > > > > --Victor Westmann
> > > > > >
> > > > > > 2016-10-04 19:28 GMT-07:00 Martin Owens <[hidden email]
> > > > > >:
> > > > > >
> > > > > > > Thanks Bryce,
> > > > > > >
> > > > > > > As discussed on IRC, I'm taking the backport-proposed
> > > > > list off your
> > > > > > > hands: https://bugs.launchpad.net/inkscape/+bugs?field.ta
> > > > > g=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_n
> > > > > otes/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/slas
> > > > > hdot
> > > > > > > > _______________________________________________
> > > > > > > > Inkscape-devel mailing list
> > > > > > > > [hidden email]
> > > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-d
> > > > > evel
> > > > > > >
> > > > > > > -------------------------------------------------------
> > > > > -----
> > > > > > > ------------------
> > > > > > > Check out the vibrant tech community on one of the
> > > > > world's most
> > > > > > > engaging tech sites, SlashDot.org! http://sdm.link/slashd
> > > > > ot
> > > > > > > _______________________________________________
> > > > > > > Inkscape-devel mailing list
> > > > > > > [hidden email]
> > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-dev
> > > > > el
> > > > > > >
> > > > > > >
> > > > >
> > > >
> > > > -------------------------------------------------------------
> > > > -----------------
> > > > 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
> > > > [hidden email]
> > > > 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
> > > [hidden email]
> > > 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
> > [hidden email]
> > 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
> [hidden email]
> 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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Eduard Braun
In reply to this post by Victor Westmann
Am 09.10.2016 um 04:17 schrieb Victor Westmann:
> Thank you for your packaged version of the 0.92 pre-release. The
> installer works like a charm (but, for some reason, it pointed
> automatically to the x86 folder, which is for 32 bit software only on
> Windows. But that's fine.

Fixed in r15108 (along with some other issues)
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15108


One thing I can't seem to be able to fix are some leftover empty
directories after uninstallation. Somehow NSIS fails to release a lock
on them during the uninstallation process and prevents itself from
removal subsequently.

Does anybody have some experience with NSIS and knows what might go wrong?


Regards,
Eduard

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Partha Bagchi
Eduard, 

I have not seen your installer (I build my own. :)). You have to delete the uninstaller first before anything. Are you doing that?

Thanks,
Partha

On Mon, Oct 10, 2016 at 6:02 PM, Eduard Braun <[hidden email]> wrote:
Am 09.10.2016 um 04:17 schrieb Victor Westmann:
> Thank you for your packaged version of the 0.92 pre-release. The
> installer works like a charm (but, for some reason, it pointed
> automatically to the x86 folder, which is for 32 bit software only on
> Windows. But that's fine.

Fixed in r15108 (along with some other issues)
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15108


One thing I can't seem to be able to fix are some leftover empty
directories after uninstallation. Somehow NSIS fails to release a lock
on them during the uninstallation process and prevents itself from
removal subsequently.

Does anybody have some experience with NSIS and knows what might go wrong?


Regards,
Eduard

------------------------------------------------------------------------------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Eduard Braun

The uninstaller is copied to / run from a temporary directory.
All files are properly deleted (i.e. there are no files left that could block removal of those directories).


Am 11.10.2016 um 00:08 schrieb Partha Bagchi:
Eduard, 

I have not seen your installer (I build my own. :)). You have to delete the uninstaller first before anything. Are you doing that?

Thanks,
Partha

On Mon, Oct 10, 2016 at 6:02 PM, Eduard Braun <[hidden email]> wrote:
Am 09.10.2016 um 04:17 schrieb Victor Westmann:
> Thank you for your packaged version of the 0.92 pre-release. The
> installer works like a charm (but, for some reason, it pointed
> automatically to the x86 folder, which is for 32 bit software only on
> Windows. But that's fine.

Fixed in r15108 (along with some other issues)
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15108


One thing I can't seem to be able to fix are some leftover empty
directories after uninstallation. Somehow NSIS fails to release a lock
on them during the uninstallation process and prevents itself from
removal subsequently.

Does anybody have some experience with NSIS and knows what might go wrong?


Regards,
Eduard

------------------------------------------------------------------------------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Partha Bagchi
Here is what I do. Never had a problem so far.

Function un.onInit
!insertmacro MUI_UNGETLANGUAGE
  MessageBox MB_ICONQUESTION|MB_YESNO|MB_DEFBUTTON2 "Are you sure you want to completely remove $(^Name) and all of its components?" IDYES +2
  Abort
FunctionEnd
 
 
Section Uninstall
  Delete "$INSTDIR\${PRODUCT_NAME}.url"
  Delete "$INSTDIR\${PRODUCT_NAME}uninst.exe"
  RMDir /r "$INSTDIR"
  Delete "$SMPROGRAMS\${PRODUCT_NAME}-${PRODUCT_VERSION}\Website.lnk"
  Delete "$SMPROGRAMS\${PRODUCT_NAME}-${PRODUCT_VERSION}\Uninstall.lnk"
  Delete "$DESKTOP\${PRODUCT_NAME}-${PRODUCT_VERSION}.lnk"
  DeleteRegKey ${PRODUCT_UNINST_ROOT_KEY} "${PRODUCT_UNINST_KEY}"
  DeleteRegKey HKLM "${PRODUCT_DIR_REGKEY}"
  DeleteRegKey HKLM "SOFTWARE\${PRODUCT_NAME}"
  ; Remove the path we added (need both PATH and Path?)
  ; ${un.EnvVarUpdate} $0 "PATH" "R" "HKLM" "$INSTDIR\bin;$INSTDIR\Frameworks"  #Remove the Inkscape from the path
  ; ${un.EnvVarUpdate} $0 "Path" "R" "HKLM" "$INSTDIR\bin;$INSTDIR\Frameworks"  #Remove the Inkscape from the path
  SetAutoClose true
SectionEnd


Hope that helps you, Eduard.

Thanks,
Partha


On Mon, Oct 10, 2016 at 6:13 PM, Eduard Braun <[hidden email]> wrote:

The uninstaller is copied to / run from a temporary directory.
All files are properly deleted (i.e. there are no files left that could block removal of those directories).


Am 11.10.2016 um 00:08 schrieb Partha Bagchi:
Eduard, 

I have not seen your installer (I build my own. :)). You have to delete the uninstaller first before anything. Are you doing that?

Thanks,
Partha

On Mon, Oct 10, 2016 at 6:02 PM, Eduard Braun <[hidden email]> wrote:
Am 09.10.2016 um 04:17 schrieb Victor Westmann:
> Thank you for your packaged version of the 0.92 pre-release. The
> installer works like a charm (but, for some reason, it pointed
> automatically to the x86 folder, which is for 32 bit software only on
> Windows. But that's fine.

Fixed in r15108 (along with some other issues)
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15108


One thing I can't seem to be able to fix are some leftover empty
directories after uninstallation. Somehow NSIS fails to release a lock
on them during the uninstallation process and prevents itself from
removal subsequently.

Does anybody have some experience with NSIS and knows what might go wrong?


Regards,
Eduard

------------------------------------------------------------------------------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Eduard Braun

No, not really, the official installer is a "bit" more complex and has a lot more functionality... Check out the code in the repository if you want to help.

Regarding you code: It's evil ^^
Think about what would happen if you accidentally install to "C:\Program Files" or even "C:\" and then uninstall... The uninstaller would just go ahead and delete everything on the drive. :-0


Am 11.10.2016 um 00:29 schrieb Partha Bagchi:
Here is what I do. Never had a problem so far.

Function un.onInit
!insertmacro MUI_UNGETLANGUAGE
  MessageBox MB_ICONQUESTION|MB_YESNO|MB_DEFBUTTON2 "Are you sure you want to completely remove $(^Name) and all of its components?" IDYES +2
  Abort
FunctionEnd
 
 
Section Uninstall
  Delete "$INSTDIR\${PRODUCT_NAME}.url"
  Delete "$INSTDIR\${PRODUCT_NAME}uninst.exe"
  RMDir /r "$INSTDIR"
  Delete "$SMPROGRAMS\${PRODUCT_NAME}-${PRODUCT_VERSION}\Website.lnk"
  Delete "$SMPROGRAMS\${PRODUCT_NAME}-${PRODUCT_VERSION}\Uninstall.lnk"
  Delete "$DESKTOP\${PRODUCT_NAME}-${PRODUCT_VERSION}.lnk"
  DeleteRegKey ${PRODUCT_UNINST_ROOT_KEY} "${PRODUCT_UNINST_KEY}"
  DeleteRegKey HKLM "${PRODUCT_DIR_REGKEY}"
  DeleteRegKey HKLM "SOFTWARE\${PRODUCT_NAME}"
  ; Remove the path we added (need both PATH and Path?)
  ; ${un.EnvVarUpdate} $0 "PATH" "R" "HKLM" "$INSTDIR\bin;$INSTDIR\Frameworks"  #Remove the Inkscape from the path
  ; ${un.EnvVarUpdate} $0 "Path" "R" "HKLM" "$INSTDIR\bin;$INSTDIR\Frameworks"  #Remove the Inkscape from the path
  SetAutoClose true
SectionEnd


Hope that helps you, Eduard.

Thanks,
Partha


On Mon, Oct 10, 2016 at 6:13 PM, Eduard Braun <[hidden email]> wrote:

The uninstaller is copied to / run from a temporary directory.
All files are properly deleted (i.e. there are no files left that could block removal of those directories).


Am 11.10.2016 um 00:08 schrieb Partha Bagchi:
Eduard, 

I have not seen your installer (I build my own. :)). You have to delete the uninstaller first before anything. Are you doing that?

Thanks,
Partha

On Mon, Oct 10, 2016 at 6:02 PM, Eduard Braun <[hidden email]> wrote:
Am 09.10.2016 um 04:17 schrieb Victor Westmann:
> Thank you for your packaged version of the 0.92 pre-release. The
> installer works like a charm (but, for some reason, it pointed
> automatically to the x86 folder, which is for 32 bit software only on
> Windows. But that's fine.

Fixed in r15108 (along with some other issues)
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15108


One thing I can't seem to be able to fix are some leftover empty
directories after uninstallation. Somehow NSIS fails to release a lock
on them during the uninstallation process and prevents itself from
removal subsequently.

Does anybody have some experience with NSIS and knows what might go wrong?


Regards,
Eduard

------------------------------------------------------------------------------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Partha Bagchi
OK, Thanks. Sorry it didn't help

On Mon, Oct 10, 2016 at 6:37 PM, Eduard Braun <[hidden email]> wrote:

No, not really, the official installer is a "bit" more complex and has a lot more functionality... Check out the code in the repository if you want to help.

Regarding you code: It's evil ^^
Think about what would happen if you accidentally install to "C:\Program Files" or even "C:\" and then uninstall... The uninstaller would just go ahead and delete everything on the drive. :-0


Am 11.10.2016 um 00:29 schrieb Partha Bagchi:
Here is what I do. Never had a problem so far.

Function un.onInit
!insertmacro MUI_UNGETLANGUAGE
  MessageBox MB_ICONQUESTION|MB_YESNO|MB_DEFBUTTON2 "Are you sure you want to completely remove $(^Name) and all of its components?" IDYES +2
  Abort
FunctionEnd
 
 
Section Uninstall
  Delete "$INSTDIR\${PRODUCT_NAME}.url"
  Delete "$INSTDIR\${PRODUCT_NAME}uninst.exe"
  RMDir /r "$INSTDIR"
  Delete "$SMPROGRAMS\${PRODUCT_NAME}-${PRODUCT_VERSION}\Website.lnk"
  Delete "$SMPROGRAMS\${PRODUCT_NAME}-${PRODUCT_VERSION}\Uninstall.lnk"
  Delete "$DESKTOP\${PRODUCT_NAME}-${PRODUCT_VERSION}.lnk"
  DeleteRegKey ${PRODUCT_UNINST_ROOT_KEY} "${PRODUCT_UNINST_KEY}"
  DeleteRegKey HKLM "${PRODUCT_DIR_REGKEY}"
  DeleteRegKey HKLM "SOFTWARE\${PRODUCT_NAME}"
  ; Remove the path we added (need both PATH and Path?)
  ; ${un.EnvVarUpdate} $0 "PATH" "R" "HKLM" "$INSTDIR\bin;$INSTDIR\Frameworks"  #Remove the Inkscape from the path
  ; ${un.EnvVarUpdate} $0 "Path" "R" "HKLM" "$INSTDIR\bin;$INSTDIR\Frameworks"  #Remove the Inkscape from the path
  SetAutoClose true
SectionEnd


Hope that helps you, Eduard.

Thanks,
Partha


On Mon, Oct 10, 2016 at 6:13 PM, Eduard Braun <[hidden email]> wrote:

The uninstaller is copied to / run from a temporary directory.
All files are properly deleted (i.e. there are no files left that could block removal of those directories).


Am 11.10.2016 um 00:08 schrieb Partha Bagchi:
Eduard, 

I have not seen your installer (I build my own. :)). You have to delete the uninstaller first before anything. Are you doing that?

Thanks,
Partha

On Mon, Oct 10, 2016 at 6:02 PM, Eduard Braun <[hidden email]> wrote:
Am 09.10.2016 um 04:17 schrieb Victor Westmann:
> Thank you for your packaged version of the 0.92 pre-release. The
> installer works like a charm (but, for some reason, it pointed
> automatically to the x86 folder, which is for 32 bit software only on
> Windows. But that's fine.

Fixed in r15108 (along with some other issues)
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15108


One thing I can't seem to be able to fix are some leftover empty
directories after uninstallation. Somehow NSIS fails to release a lock
on them during the uninstallation process and prevents itself from
removal subsequently.

Does anybody have some experience with NSIS and knows what might go wrong?


Regards,
Eduard

------------------------------------------------------------------------------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

the Adib-2
In reply to this post by Eduard Braun
Hello Eduard,

The installer must only remove directories and files that has been created during install.

If inkscape creates more files and directories or just modifies files, those must remain.

Does it happen with 0.91 as well?

Regards, Adib.
--

Am Dienstag, 11. Oktober 2016 schrieb Eduard Braun :
Am 09.10.2016 um 04:17 schrieb Victor Westmann:
> Thank you for your packaged version of the 0.92 pre-release. The
> installer works like a charm (but, for some reason, it pointed
> automatically to the x86 folder, which is for 32 bit software only on
> Windows. But that's fine.

Fixed in r15108 (along with some other issues)
http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/revision/15108


One thing I can't seem to be able to fix are some leftover empty
directories after uninstallation. Somehow NSIS fails to release a lock
on them during the uninstallation process and prevents itself from
removal subsequently.

Does anybody have some experience with NSIS and knows what might go wrong?


Regards,
Eduard

------------------------------------------------------------------------------
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
<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;Inkscape-devel@lists.sourceforge.net&#39;)">Inkscape-devel@...
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Eduard Braun
Am 11.10.2016 um 07:59 schrieb the Adib:
> Hello Eduard,
>
> The installer must only remove directories and files that has been
> created during install.
That's what it does. Probably the source of the problem is in that code,
though...
>
> If inkscape creates more files and directories or just modifies files,
> those must remain.
I disagree. Most files Inkscape creates can be safely removed (personal
preferences obviously have an additional setting).
What we have to preserve are files the user might have modfied/created!
>
> Does it happen with 0.91 as well?
That I have yet to check. Since I'm using NSIS 3.0 now (instead of 2.x)
it's quite possible it's even an NSIS regression, but I hadn't have time
to cross-check with an older version yet.
>
> Regards, Adib.

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reply | Threaded
Open this post in threaded view
|

Re: 0.92 release status (volunteers needed)

Brynn
In reply to this post by Martin Owens-2
Let me know when About Screen Contest is ready, and I'll announce on forums.

I could also make a brief News item on the website, if no one else has time.

All best,
brynn


--------------------------------------------------
From: "Martin Owens" <[hidden email]>
Sent: Tuesday, October 04, 2016 8:28 PM
To: "Bryce Harrington" <[hidden email]>;
<[hidden email]>
Subject: Re: [Inkscape-devel] 0.92 release status (volunteers needed)

> ------------------------------------------------------------------------------
> 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
> [hidden email]
> 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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
12