The first (and hopefully only) pre-release package for the upcoming 0.92.2 release is now available:
https://inkscape.org/en/gallery/=inkscape-package/0922pre0/
The 0.92.x branch should now be considered in Hard Freeze + String Freeze. Code changes to the 0.92.2 branch should be sent to me for review and landing (see below.) Translations can be landed normally up to the 4th of Aug.
---
I intended to get this released last weekend, but the dist process has changed significantly with the git migration and needed a bit of TLC. suv, liam, Eduard, QuLogic, and others have provided much advice and assistance getting things adapted - thank you.
Specifically, we're moved from using `bzr export` to `git archive` for producing the dists. In theory this should be an equivalent move, but please keep your eyes peeled for any missing files or release-specific details that failed to get updated.
While there are more enhancements that could be done(*) to streamline the dist code, in the interest of stability, predictability, and expediency I'm going to postpone those to after the release. The dist modifications also need ported to trunk. If anyone's interested in doing this let me know and I'll explain how it should be done, otherwise I'll try to get it taken care of later.
The release will be in approximately 2 weeks. I'm thinking a release coordination meeting following the upcoming board meeting may make sense; I'll send an invite later. At this time, despite my delay getting pre0 out, I think the schedule outlined below can still be achieved; contact me if you know of any factors that need to be taken into account.
Bryce
* - Notably, QuLogic suggested using gitattributes to substitute the commit hash and date in inkscape-version.cmake, instead of inserting it via set and then temporarily committing. This would be far cleaner than the hack I've added.
------------------------------------------------------------------------
Date: Sat, 15 Jul 2017 22:23:07 -0700 From: Bryce Harrington <bryce@...961...> To: inkscape-devel@...6... Subject: [Inkscape-devel] Proposed schedule for 0.92.2 release
We were holding off for 0.92.2 until the git migration was done. Now with that behind us, I'd like to suggest some plans for doing another point release:
Jul 22: 0.92.x Pre-release + String Freeze (0.92.x branch only) + Packagers package pre0 release as desired + Translators work on translations + Revert changes that introduced regressions + Code changes must be reviewed and landed by Bryce (0.92.x branch only) Aug 4: Final Freeze + Final deadline for all translation work + Only Release Warden may commit (0.92.x branch only) Aug 5: 0.92.x Release Tarball + Packagers package final tarball Aug 7: Announce
Backporting of fixes has been going strong (good work everyone!) Please keep doing as you've been doing for one more week.
After the 22nd, I will be reviewing and landing all further code-changing patches. You can send me merge requests, lists of cherrypickable SHA's from trunk, or patchsets generated via `git format-patch`, as is convenient for you. Stuff I'll be watching for:
☑ Patch is short ☑ Fix is already in trunk ☑ Has been tested and confirmed by at least one other person ☑ References a bug ID or url in commit message ☑ No translatable strings are changed ☑ Bugfix only - no refactoring, no feature changes
On the 22nd, I'll package a pre0 tarball for testing purposes. The switch to git will require updating some release procedures so this will be a good dry run. It would be nice to see packages made.
Testing of the pre-release will be appreciated, however for release purposes we will be principally looking for _regressions_ compared with 0.92.1, so we can revert whatever patch caused the regression. Other bugs are welcome to be filed and worked on, of course, but I'd like to keep on schedule.
For the actual release, please take Aug 5th as a pencilled in date, that may need to change depending on how things go. When the tarball is ready I'll send a private note to the release team (packagers + announcers).
Vector Team, if you would like to take the announcement writing and/or dissemination tasks, let me know - I'd be very appreciative of the help.
Let me know if there is anything else that should be done or accounted for in the above plan.
Bryce