Inkscape 0.48 tagged and rolled -- Please don't announce
Howdy,
So I've tagged and rolled the 0.48 release. Just as a reminder, please don't announce this widely as we want to let binary packagers get a chance to have binaries ready when people start rushing to pull down a copy.
== Downloads ==
https://sourceforge.net/projects/inkscape/files/inkscape/0.48/
== SHA1 Sums ==
a2ab9b34937cc4f2b482c9b3720d8fd4dc7b12e8 inkscape-0.48.0.tar.bz2 220ade981069a91d3afab9cbff75f65c75119da2 inkscape-0.48.0.tar.gz df32c39dfdb2072bf32ff71e7293c6bb84a53e26 inkscape-0.48.0.zip
== MD5 Sums ==
fd8b17a3f06668603807176a77167bb9 inkscape-0.48.0.tar.bz2 bb94543b813157d83281657a89465d46 inkscape-0.48.0.tar.gz 26318c26b056be7813e3ea06a8244b88 inkscape-0.48.0.zip
This is a pretty cool release, I'm excited about it. Thanks to everyone who contributed!
--Ted
2010/8/13 Ted Gould <ted@...11...>:
Howdy,
So I've tagged and rolled the 0.48 release. Just as a reminder, please don't announce this widely as we want to let binary packagers get a chance to have binaries ready when people start rushing to pull down a copy.
Is there a chance of amending the tarball (maybe 0.48.0.1?) to get this fix in? I think it could cause a lot of hair loss among our users :/ https://bugs.launchpad.net/inkscape/+bug/591986
Regards, Krzysztof
On Fri, 2010-08-13 at 23:15 +0200, Krzysztof Kosiński wrote:
2010/8/13 Ted Gould <ted@...11...>:
So I've tagged and rolled the 0.48 release. Just as a reminder, please don't announce this widely as we want to let binary packagers get a chance to have binaries ready when people start rushing to pull down a copy.
Is there a chance of amending the tarball (maybe 0.48.0.1?) to get this fix in? I think it could cause a lot of hair loss among our users :/ https://bugs.launchpad.net/inkscape/+bug/591986
I don't really want to amend a tarball, but I'm okay with finding a few bugs and throwing together a 0.48.1.
--Ted
Hi altogether,
On Fri, Aug 13, 2010 at 11:15:09PM +0200, Krzysztof Kosiński wrote:
2010/8/13 Ted Gould <ted@...11...>:
Howdy,
So I've tagged and rolled the 0.48 release. Just as a reminder, please don't announce this widely as we want to let binary packagers get a chance to have binaries ready when people start rushing to pull down a copy.
Is there a chance of amending the tarball (maybe 0.48.0.1?) to get this fix in? I think it could cause a lot of hair loss among our users :/ https://bugs.launchpad.net/inkscape/+bug/591986
I just sent a package containing your fix to my sponsor, so inkscape 0.48.0 should appear in debian experimental soon :-)
Even if squeeze is frozen now, I'll ask the release team to accept 0.48.0 for squeeze.
If you update the NEWS file until then, this would be great. Otherwise, i'll just copy over the wiki.
Thanks for all your work,
Wolfi
Regards, Krzysztof
This SF.net email is sponsored by
Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Fri, 2010-08-13 at 10:57 -0500, Ted Gould wrote:
So I've tagged and rolled the 0.48 release.
Uhg, so it seems I forgot to update the NEWS file. Personally, I feel that NEWS is an outdated file and the release notes in the Wiki are more useful. But, what does everyone else think? Rebuild tarballs? Wait for 0.48.1?
--Ted
participants (3)
-
Krzysztof Kosiński -
Ted Gould -
Wolfram Quester