Creating Inkscape distributions - Revision history

BryceHarrington: /* Creating the Official Release Package */

2017-08-07T10:33:39Z

Creating the Official Release Package

← Older revision		Revision as of 10:33, 7 August 2017
Line 33:		Line 33:

	<pre>		<pre>
	~~bzr~~ branch RELEASE_0_38_BRANCH		git branch RELEASE_0_38_BRANCH
	~~bzr~~ push		git push
	</pre>		</pre>

Line 40:		Line 40:

	<pre>		<pre>
	~~bzr~~ checkout RELEASE_0_38_BRANCH		git checkout RELEASE_0_38_BRANCH
	</pre>		</pre>

	After establishing the release branch, set the Inkscape version number in trunk to reflect the new future version, 0.91+devel.		After establishing the release branch, set the Inkscape version number in trunk to reflect the new future version, 0.91+devel.


	Once the release is deemed ready a distribution tarball should be created as below.		Once the release is deemed ready a distribution tarball should be created as below.
Line 53:		Line 52:
	# Create a source tarball package (see below)		# Create a source tarball package (see below)
	# GPG sign the source tarball package (see below)		# GPG sign the source tarball package (see below)


	=== Setting the Inkscape version number ===		=== Setting the Inkscape version number ===

BryceHarrington: /* Pre-releases */

2017-08-07T10:33:03Z

Pre-releases

← Older revision		Revision as of 10:33, 7 August 2017
Line 22:		Line 22:
	ON HEAD:		ON HEAD:

	# Update your ~~bzr~~ branch to latest, and check that Inkscape configures, builds, and runs		# Update your git branch to latest, and check that Inkscape configures, builds, and runs
	# Set the pre-release version number (see below) to <major>.<minor>pre<prerelease>. E.g. 0.91pre2		# Set the pre-release version number (see below) to <major>.<minor>pre<prerelease>. E.g. 0.91pre2
	# Create a source tarball package (see below)		# Create a source tarball package (see below)

BryceHarrington: /* Uploading packages to the website */

2017-08-06T20:28:17Z

Uploading packages to the website

← Older revision		Revision as of 20:28, 6 August 2017
Line 115:		Line 115:
	2. Make a folder for your releases in your 'InkSpace' - Go to https://inkscape.org/gallery/new/ and fill in the name of the folder you want to use, for example "0.92pre2". Set the group to "Developer" to allow other packagers to upload into it, and the category to "Inkscape Package".		2. Make a folder for your releases in your 'InkSpace' - Go to https://inkscape.org/gallery/new/ and fill in the name of the folder you want to use, for example "0.92pre2". Set the group to "Developer" to allow other packagers to upload into it, and the category to "Inkscape Package".

	3. Navigate to the folder you just created, ~~and click~~ the "Upload Resource~~" button~~.		3. Exit this view, by going back to My Galleries (via the resource icon at top right of the screen). Navigate to the folder you just created (it'll be under the Galleries listing on the lower right). This should show the information about the gallery you created, along with a blue Submit Resource button. Click on that button to get to the Upload New Resource dialog for your gallery.

	* Ignore 'External Link'		* Ignore 'External Link'

BryceHarrington: /* Creating a source tarball package */

2017-08-06T19:27:29Z

Creating a source tarball package

← Older revision		Revision as of 19:27, 6 August 2017
Line 76:		Line 76:
	* Run "git status" to check for anything strange (e.g. source files accidentally added or removed)		* Run "git status" to check for anything strange (e.g. source files accidentally added or removed)
	* Run "git commit -am 'Update for ${VERSION} release'" to commit the changed CMakeLists.txt and any other files		* Run "git commit -am 'Update for ${VERSION} release'" to commit the changed CMakeLists.txt and any other files
			* Tag the release in git "git tag. Release tags should be in the form INKSCAPE_<major>_<minor>_<point>. A non-point-release like 0.91 would get the tag INKSCAPE_0_91_0, 0.91.1 would get the tag INKSCAPE_0_91_1, and so on. Pre-releases are tagged like INKSCAPE_0_92_PRE3 and INKSCAPE_0_92_2_PRE0.
	* Run "make dist"		* Run "make dist"
	** This should produce inkscape-${VERSION}.tar.bz2 in the build directory		** This should produce inkscape-${VERSION}.tar.bz2 in the build directory
	** Verify the cmake output shows WITH_PROFILING and all WITH_*_EXPERIMENTAL tags are OFF		** Verify the cmake output shows WITH_PROFILING and all WITH_*_EXPERIMENTAL tags are OFF
	** Verify CMAKE_BUILD_TYPE is set as 'Release'		** Verify CMAKE_BUILD_TYPE is set as 'Release'
	** Run "tar -C /tmp -xjf inkscape-${VERSION}.tar.bz2" and verify the contents at /tmp/inkscape-VERSION/ are as you expect		** Run "tar -C /tmp -xjf inkscape-${VERSION}.tar.bz2" and verify the contents at /tmp/inkscape-${VERSION}/ are as you expect
	* Tag the release in git "git tag. Release tags should be in the form INKSCAPE_<major>_<minor>_<point>. A non-point-release like 0.91 would get the tag INKSCAPE_0_91_0, 0.91.1 would get the tag INKSCAPE_0_91_1, and so on. Pre-releases are tagged like INKSCAPE_0_92_PRE3 and INKSCAPE_0_92_2_PRE0.		* Modify CMakeScripts/inkscape-version.cmake to reset INKSCAPE_REVISION to "unknown" [TODO: Replace this substitution with gitattributes]
	* Modify inkscape-version.cmake to reset INKSCAPE_REVISION to "unknown" [TODO: Replace this substitution with gitattributes]
	* git push		* git push
	* git push origin INKSCAPE_0_92_1_PRE0		* git push origin INKSCAPE_0_92_1_PRE0

BryceHarrington: No need for directions on signing rpms, since we no longer provide them.

2017-07-25T22:08:02Z

No need for directions on signing rpms, since we no longer provide them.

← Older revision		Revision as of 22:08, 25 July 2017
Line 157:		Line 157:
	The article [[CompilingDebian]] provides a makefile to download a tarball and build a debian package therefrom.		The article [[CompilingDebian]] provides a makefile to download a tarball and build a debian package therefrom.


	~~=== Signing your package ===~~

	~~First, you need to have a public/private keypair. This can be generated with gpg using 'gpg --gen-key'.~~

	~~To add a signature to an extisting package, use the command rpm --addsign /path/to/package.rpm To sign in the process of building a package, use rpmbuild -bb --sign~~

	~~To check the signature on a package, use rpm --checksig.~~

BryceHarrington: We no longer produce RPM files (since a long time).

2017-07-25T22:06:15Z

We no longer produce RPM files (since a long time).

← Older revision		Revision as of 22:06, 25 July 2017
Line 156:		Line 156:

	The article [[CompilingDebian]] provides a makefile to download a tarball and build a debian package therefrom.		The article [[CompilingDebian]] provides a makefile to download a tarball and build a debian package therefrom.

	~~=== Creating a distribution RPM ===~~

	~~Method A:~~
	~~# do as above for tarball, or download the release tarball~~
	~~# login as root~~
	~~# rpmbuild -tb inkscape-x.x.tar.gz~~
	~~# Your RPMs will be in /usr/src/rpm[[/RPMS]] (/usr/src/redhat on RH systems)~~
	~~# RPMs should be GPG signed~~

	~~Method B:~~
	~~# do as above for tarball, or download the release tarball~~
	~~# mkdir ~/rpm~~
	~~# Copy the tarball to ~/rpm/SOURCES/~~
	~~# Copy the inkscape.spec from the tarball to ~/rpm/SPECS/inkscape.spec~~
	~~# rpmbuild -ba ~/rpm/SPECS/inkscape.spec~~
	~~# Your RPMs will be in ~/rpm/RPMS and ~/rpm/SRPMS~~
	~~# RPMs should be GPG signed~~

	~~The rpm should be named according to the following pattern:~~

	~~inkscape-$RELEASE-$PKG.$DISTRO.$ARCH.rpm~~

	~~Where:~~

	~~$RELEASE: the Inkscape release number, such as “0.37”, “0.36.2”, etc.~~
	~~The third number should be omitted if it is 0. (I.e., 0.37 instead of 0.37.0)~~

	~~$PKG: A version number for your package. Use a value of 1 for your package, and increment it if you~~
	~~need to update the released package for some reason.~~

	~~$DISTRO: The name and an indicator of the version number for the distro. E.g.,~~
	~~rh71, rh90, mdk91, suse90, fc1, etc. No need to be too exhaustive with the distro versions;~~
	~~for a given brand of distro it's probably enough to have a reasonably “modern” release~~
	~~and an older one for legacy support. For instance, rh71 and rh90.~~

	~~$ARCH: The architecture that the package was built on. E.g., i686, i386, athlon, ppc, etc.~~
	~~Don't bother with i586 - either i386 or i686 is preferred. The i386 packages will run on Cyrix~~
	~~and K-6.~~

	~~Examples:~~

	~~inkscape-0.37-1.mdk80.i386.rpm~~
	~~inkscape-0.37-1.mdk80.i686.rpm~~
	~~inkscape-0.37-1.mdk91.i386.rpm~~
	~~inkscape-0.37-1.mdk91.i686.rpm~~

	~~inkscape-0.37-1.fc1.i386.rpm~~
	~~inkscape-0.37-1.fc1.i686.rpm~~
	~~inkscape-0.37-1.fc1.athlon.rpm~~
	~~inkscape-0.37-1.fc1.ppc.rpm~~

	~~For creating spec files, feel free to list yourself as the packager, but please use~~
	~~inkscape-devel@lists.sourceforge.net as the contact email address, to ensure that~~
	~~questions/complaints about the RPM go to the official support channel.~~

	~~==== Patching RPMs ====~~

	Occasionally, the RPM will not build without some modifications. If the problem is serious enough that it affects every packaging format, this could signal a need to do a point release, but usually you can just add a patch specifically for the RPM. This is what RPM is for, after all. :-)

	~~Here's how to do it:~~

	~~1. Create a copy of the source tree, with the modifications needed to correct the issue.~~
	~~2. Generate a patch like this:~~

	~~$ diff -uNr package-1.0/ package-1.0p/ > ../SOURCES/package-1.0-my.patch~~

	~~3. Next add the patch to the RPM. In the specfile at %_topdir/SPECS/package.spec, add a line like this at the top of the file:~~

	~~Patch0: package-1.0-my.patch~~

	~~Then further down add a line after the %setup section, like this:~~

	~~%prep~~
	~~%setup ...~~
	~~%patch0 -p1~~

	It's a very good idea to split up changes into discrete patches, giving each a different number (they don't have to be consecutively numbered). Also, be sure to upload the patch(es) to the patch tracker so they'll get into the codebase for the next release.

	~~Then rebuild the package like this:~~

	~~rpmbuild -ba SPECS/package.spec~~

BryceHarrington: We no longer release files to Sourceforge

2017-07-25T22:05:12Z

We no longer release files to Sourceforge

← Older revision		Revision as of 22:05, 25 July 2017
Line 247:		Line 247:

	To check the signature on a package, use rpm --checksig.		To check the signature on a package, use rpm --checksig.

	~~=== Releasing Dists on the [[SourceForge]] File Release Tool ===~~

	~~To release a file: (You need Release Tech permission for your Inkscape account)~~

	* ftp upload.sf.net (anonymous/anonymous)
	* cd incoming
	* mput filename
	* go to Admin -> File Releases
	* scroll to the bottom and click [Add Release] to the inkscape item
	* Enter 0.35 in the box & click “Create this Release”
	* Fill in the form, checkbox the file you uploaded in (c)
	* It won't give you a clear “success” message, but you can check it got in right by going to the Files list. You can then edit any of the info you entered, to make it more correct.

	~~Also see [[CVSNamingConventions]] if you are making a release.~~

BryceHarrington at 19:08, 25 July 2017

2017-07-25T19:08:07Z

← Older revision		Revision as of 19:08, 25 July 2017
Line 82:		Line 82:
	** Run "tar -C /tmp -xjf inkscape-${VERSION}.tar.bz2" and verify the contents at /tmp/inkscape-VERSION/ are as you expect		** Run "tar -C /tmp -xjf inkscape-${VERSION}.tar.bz2" and verify the contents at /tmp/inkscape-VERSION/ are as you expect
	* Tag the release in git "git tag. Release tags should be in the form INKSCAPE_<major>_<minor>_<point>. A non-point-release like 0.91 would get the tag INKSCAPE_0_91_0, 0.91.1 would get the tag INKSCAPE_0_91_1, and so on. Pre-releases are tagged like INKSCAPE_0_92_PRE3 and INKSCAPE_0_92_2_PRE0.		* Tag the release in git "git tag. Release tags should be in the form INKSCAPE_<major>_<minor>_<point>. A non-point-release like 0.91 would get the tag INKSCAPE_0_91_0, 0.91.1 would get the tag INKSCAPE_0_91_1, and so on. Pre-releases are tagged like INKSCAPE_0_92_PRE3 and INKSCAPE_0_92_2_PRE0.
			* Modify inkscape-version.cmake to reset INKSCAPE_REVISION to "unknown" [TODO: Replace this substitution with gitattributes]
	* git push		* git push
	* git push origin INKSCAPE_0_92_1_PRE0		* git push origin INKSCAPE_0_92_1_PRE0
Line 112:		Line 113:
	* Make sure you have a public gpg key recorded - Go to https://inkscape.org/user/edit/ and fill in the right boxes, the GPG Public Key box is expecting a pasted public key (not private key!) and hit submit when done.		* Make sure you have a public gpg key recorded - Go to https://inkscape.org/user/edit/ and fill in the right boxes, the GPG Public Key box is expecting a pasted public key (not private key!) and hit submit when done.

	2. Make a folder for your releases in your 'InkSpace' - Go to https://inkscape.org/gallery/new/ and fill in the name of the folder you want to use, for example "0.92pre2". Set the group to "Developer" to allow other packagers to upload into it, and the category to "Inkscape Package". ~~[I don't actually know how to PUT files into the created gallery, so this step may be pointless...]~~		2. Make a folder for your releases in your 'InkSpace' - Go to https://inkscape.org/gallery/new/ and fill in the name of the folder you want to use, for example "0.92pre2". Set the group to "Developer" to allow other packagers to upload into it, and the category to "Inkscape Package".

	3. Upload ~~your released file at https://inkscape~~.~~org/en/gallery/upload/~~		3. Navigate to the folder you just created, and click the "Upload Resource" button.

	* Ignore 'External Link'		* Ignore 'External Link'
Line 120:		Line 121:
	* Select 'Inkscape Package' from the category drop down.		* Select 'Inkscape Package' from the category drop down.
	* Upload the gpg sig file using the 'Choose File' button under Signature/Checksum.		* Upload the gpg sig file using the 'Choose File' button under Signature/Checksum.
	* Select 'GPLv2' from the Licenses drop down.		* Select 'GPLv2' (or 'GPLv3' if appropriate) from the Licenses drop down.
	* Check 'Mirror' checkbox (optional; not used presently)		* Check 'Mirror' checkbox (optional; not used presently)
	* Check 'Visible' checkbox
	* Submit this form.		* Submit this form.

	5. Verify and copy link - If everything's gone well you should now see your released file with a ~~green padlock~~ indicating the gpg signature has been verified against your account public key. ~~(Error: No such padlock...?)~~		5. Verify and copy link - If everything's gone well you should now see your released file with a blue ribbon icon indicating the gpg signature has been verified against your account public key.
	* Download the release by clicking on the down-arrow icon. Confirm it's the file you intended.		* Download the release by clicking on the down-arrow icon. Confirm it's the file you intended.
	* Copy this download link.		* Copy this download link.

BryceHarrington: Undo revision 106001 by BryceHarrington (talk)

2017-07-25T17:01:02Z

Undo revision 106001 by BryceHarrington (talk)

← Older revision		Revision as of 17:01, 25 July 2017
Line 57:		Line 57:
	=== Setting the Inkscape version number ===		=== Setting the Inkscape version number ===

	Set the version name in ~~these files~~:		Set the version name and number in CMakeList.txt. For example:
	* configure.ac in the AC_INIT() ~~macro~~
	* CMakeList.txt		set(INKSCAPE_VERSION_MAJOR 0)
	* src/inkscape.rc		set(INKSCAPE_VERSION_MINOR 92)
	* src/inkview.rc		set(INKSCAPE_VERSION_PATCH 1)
	* src/inkscape-x64.rc		set(INKSCAPE_VERSION_SUFFIX "pre0")
	* src/inkview-x64.rc

	=== Update the translation files ===		=== Update the translation files ===
Line 74:		Line 73:

	* Run `perl packaging/mkNEWS 0.92 > NEWS` to add the release notes into the NEWS file in the release branch. This command requires perl and w3m. Don't forget to replace 0.91 with the correct version number. The NEWS file may need some manual cleanup, so do a quick review of it.		* Run `perl packaging/mkNEWS 0.92 > NEWS` to add the release notes into the NEWS file in the release branch. This command requires perl and w3m. Don't forget to replace 0.91 with the correct version number. The NEWS file may need some manual cleanup, so do a quick review of it.
	* mkdir build; cd build; cmake ..; make		* mkdir build; cd build; cmake ..; make -j4
	* (Obsolete?) Run "cd src && make helper/sp-marshal.h helper/sp-~~marshal.cpp; cd ..", then do~~		* Run "git status" to check for anything strange (e.g. source files accidentally added or removed)
	* Run "~~bzr~~ status" to check for anything strange (e.g. source files accidentally added or removed)		* Run "git commit -am 'Update for ${VERSION} release'" to commit the changed CMakeLists.txt and any other files
	* Run "~~bzr~~ commit -m '~~update~~ for release'" to commit the changed ~~configure~~.ac and other files
	* Run "make dist"		* Run "make dist"
	* This should produce inkscape-VERSION.tar.bz2 in the build directory		** This should produce inkscape-${VERSION}.tar.bz2 in the build directory
	* Run "tar -C /tmp -xjf inkscape-VERSION.tar.bz2" and verify the contents at /tmp/inkscape-VERSION/ are as you expect		** Verify the cmake output shows WITH_PROFILING and all WITH_*_EXPERIMENTAL tags are OFF
			** Verify CMAKE_BUILD_TYPE is set as 'Release'
			** Run "tar -C /tmp -xjf inkscape-${VERSION}.tar.bz2" and verify the contents at /tmp/inkscape-VERSION/ are as you expect
			* Tag the release in git "git tag. Release tags should be in the form INKSCAPE_<major>_<minor>_<point>. A non-point-release like 0.91 would get the tag INKSCAPE_0_91_0, 0.91.1 would get the tag INKSCAPE_0_91_1, and so on. Pre-releases are tagged like INKSCAPE_0_92_PRE3 and INKSCAPE_0_92_2_PRE0.
			* git push
			* git push origin INKSCAPE_0_92_1_PRE0
	* GPG sign the packages (see below)		* GPG sign the packages (see below)
	* Upload the package and sig to the website. (see below)		* Upload the package and sig to the website. (see below)
	* Tag the release in bzr. Release tags should be in the form INKSCAPE_<major>_<minor>_<point>. A non-point-release like 0.91 would get the tag INKSCAPE_0_91_0, 0.91.1 would get the tag INKSCAPE_0_91_1, and so on. Pre-releases are tagged like INKSCAPE_0_91_PRE0.
	* bzr push

	=== GPG signing Tarballs ===		=== GPG signing Tarballs ===
Line 111:		Line 112:
	* Make sure you have a public gpg key recorded - Go to https://inkscape.org/user/edit/ and fill in the right boxes, the GPG Public Key box is expecting a pasted public key (not private key!) and hit submit when done.		* Make sure you have a public gpg key recorded - Go to https://inkscape.org/user/edit/ and fill in the right boxes, the GPG Public Key box is expecting a pasted public key (not private key!) and hit submit when done.

	2. Make a folder for your releases in your 'InkSpace' - Go to https://inkscape.org/gallery/new/ and fill in the name of the folder you want to use, for example "0.92pre2". Set the ~~type~~ to "Developer" to allow other packagers to upload into it, ~~but otherwise this folder is only for your own organization~~ and ~~won~~'t ~~be seen by users.~~		2. Make a folder for your releases in your 'InkSpace' - Go to https://inkscape.org/gallery/new/ and fill in the name of the folder you want to use, for example "0.92pre2". Set the group to "Developer" to allow other packagers to upload into it, and the category to "Inkscape Package". [I don't actually know how to PUT files into the created gallery, so this step may be pointless...]

	~~3. Upload your released file - Go to https://inkscape.org/user/ and drag your file~~ to the ~~new~~ gallery ~~folder created above. The upload~~ may ~~take some time but you should~~ be ~~able to see a progress bar as it uploads~~. ~~(if you don't have javascript enabled, you can click on the folder and then click add and follow the manual form)~~.

	4. ~~Enter all the details - Go into~~ your ~~folder and click on the newly uploaded item~~. ~~It should have a red border indicating it's not yet published (if you used the drag+drop method)~~		3. Upload your released file at https://inkscape.org/en/gallery/upload/

	* Ignore 'External Link'		* Ignore 'External Link'
	* Going into the editor section you should be able to fill in the title for the released file. E.g. "Inkscape 0.92pre2 Source Tarball"		* Going into the editor section you should be able to fill in the title for the released file. E.g. "Inkscape 0.92pre2 Source Tarball"
	* Paste in the release notes (i.e. NEWS) into the description.
	* Select 'Inkscape Package' from the category drop down.		* Select 'Inkscape Package' from the category drop down.
	* Upload the gpg sig file using the 'Choose File' button under Signature/Checksum.		* Upload the gpg sig file using the 'Choose File' button under Signature/Checksum.

BryceHarrington: Reverted edits by BryceHarrington (talk) to last revision by Eduard

2017-07-25T16:58:53Z

Reverted edits by BryceHarrington (talk) to last revision by Eduard

← Older revision		Revision as of 16:58, 25 July 2017
Line 57:		Line 57:
	=== Setting the Inkscape version number ===		=== Setting the Inkscape version number ===

	Set the version name ~~and number~~ in CMakeList.txt. ~~For example:~~		Set the version name in these files:
			* configure.ac in the AC_INIT() macro
	~~set(INKSCAPE_VERSION_MAJOR 0)~~		* CMakeList.txt
	~~set(INKSCAPE_VERSION_MINOR 92)~~		* src/inkscape.rc
	~~set(INKSCAPE_VERSION_PATCH 1)~~		* src/inkview.rc
	~~set(INKSCAPE_VERSION_SUFFIX "pre0")~~		* src/inkscape-x64.rc
			* src/inkview-x64.rc

	=== Update the translation files ===		=== Update the translation files ===
Line 73:		Line 74:

	* Run `perl packaging/mkNEWS 0.92 > NEWS` to add the release notes into the NEWS file in the release branch. This command requires perl and w3m. Don't forget to replace 0.91 with the correct version number. The NEWS file may need some manual cleanup, so do a quick review of it.		* Run `perl packaging/mkNEWS 0.92 > NEWS` to add the release notes into the NEWS file in the release branch. This command requires perl and w3m. Don't forget to replace 0.91 with the correct version number. The NEWS file may need some manual cleanup, so do a quick review of it.
	* mkdir build; cd build; cmake ..; make -j4		* mkdir build; cd build; cmake ..; make
	* Run "~~git~~ status" to check for anything strange (e.g. source files accidentally added or removed)		* (Obsolete?) Run "cd src && make helper/sp-marshal.h helper/sp-marshal.cpp; cd ..", then do
	* Run "~~git~~ commit -am '~~Update~~ for ~~${VERSION}~~ release'" to commit the changed ~~CMakeLists~~.~~txt~~ and ~~any~~ other files		* Run "bzr status" to check for anything strange (e.g. source files accidentally added or removed)
			* Run "bzr commit -m 'update for release'" to commit the changed configure.ac and other files
	* Run "make dist"		* Run "make dist"
	** This should produce inkscape-${VERSION}.tar.bz2 in the build directory		* This should produce inkscape-VERSION.tar.bz2 in the build directory
	** Verify the cmake output shows WITH_PROFILING and all WITH_*_EXPERIMENTAL tags are OFF		* Run "tar -C /tmp -xjf inkscape-VERSION.tar.bz2" and verify the contents at /tmp/inkscape-VERSION/ are as you expect
	** Verify CMAKE_BUILD_TYPE is set as 'Release'
	** Run "tar -C /tmp -xjf inkscape-${VERSION}.tar.bz2" and verify the contents at /tmp/inkscape-VERSION/ are as you expect
	* Tag the release in git "git tag. Release tags should be in the form INKSCAPE_<major>_<minor>_<point>. A non-point-release like 0.91 would get the tag INKSCAPE_0_91_0, 0.91.1 would get the tag INKSCAPE_0_91_1, and so on. Pre-releases are tagged like INKSCAPE_0_92_PRE3 and INKSCAPE_0_92_2_PRE0.
	* git push
	* git push origin INKSCAPE_0_92_1_PRE0
	* GPG sign the packages (see below)		* GPG sign the packages (see below)
	* Upload the package and sig to the website. (see below)		* Upload the package and sig to the website. (see below)
			* Tag the release in bzr. Release tags should be in the form INKSCAPE_<major>_<minor>_<point>. A non-point-release like 0.91 would get the tag INKSCAPE_0_91_0, 0.91.1 would get the tag INKSCAPE_0_91_1, and so on. Pre-releases are tagged like INKSCAPE_0_91_PRE0.
			* bzr push

	=== GPG signing Tarballs ===		=== GPG signing Tarballs ===
Line 112:		Line 111:
	* Make sure you have a public gpg key recorded - Go to https://inkscape.org/user/edit/ and fill in the right boxes, the GPG Public Key box is expecting a pasted public key (not private key!) and hit submit when done.		* Make sure you have a public gpg key recorded - Go to https://inkscape.org/user/edit/ and fill in the right boxes, the GPG Public Key box is expecting a pasted public key (not private key!) and hit submit when done.

	2. Make a folder for your releases in your 'InkSpace' - Go to https://inkscape.org/gallery/new/ and fill in the name of the folder you want to use, for example "0.92pre2". Set the ~~group~~ to "Developer" to allow other packagers to upload into it, and ~~the category~~ to ~~"Inkscape Package"~~. ~~[I don't actually know how~~ to ~~PUT files into~~ the created ~~gallery, so this step~~ may be ~~pointless.~~..]		2. Make a folder for your releases in your 'InkSpace' - Go to https://inkscape.org/gallery/new/ and fill in the name of the folder you want to use, for example "0.92pre2". Set the type to "Developer" to allow other packagers to upload into it, but otherwise this folder is only for your own organization and won't be seen by users.

			3. Upload your released file - Go to https://inkscape.org/user/ and drag your file to the new gallery folder created above. The upload may take some time but you should be able to see a progress bar as it uploads. (if you don't have javascript enabled, you can click on the folder and then click add and follow the manual form).

	3. ~~Upload~~ your ~~released file at https://inkscape~~.~~org/en/gallery/upload/~~		4. Enter all the details - Go into your folder and click on the newly uploaded item. It should have a red border indicating it's not yet published (if you used the drag+drop method)

	* Ignore 'External Link'		* Ignore 'External Link'
	* Going into the editor section you should be able to fill in the title for the released file. E.g. "Inkscape 0.92pre2 Source Tarball"		* Going into the editor section you should be able to fill in the title for the released file. E.g. "Inkscape 0.92pre2 Source Tarball"
			* Paste in the release notes (i.e. NEWS) into the description.
	* Select 'Inkscape Package' from the category drop down.		* Select 'Inkscape Package' from the category drop down.
	* Upload the gpg sig file using the 'Choose File' button under Signature/Checksum.		* Upload the gpg sig file using the 'Choose File' button under Signature/Checksum.