Hey, So if you're on these mailing list, you know the deal :-) There are a couple build fixes in this update. Sourceforge: http://sourceforge.net/projects/inkscape/files/inkscape/0.48.3.1/ Launchpad: https://launchpad.net/inkscape/0.48.x/0.48.3.1 MD5 Sums f0fcc02088cc643634806064e7ab4ec3 inkscape-0.48.3.1.tar.bz2 3e956cd9cf6cf0a22b64a821f5a4084d inkscape-0.48.3.1.tar.bz2.asc ccf8ccd9e66199badb8c35ea3851a888 inkscape-0.48.3.1.tar.gz aded57e1a851a5f3d763fd892c085fe1 inkscape-0.48.3.1.tar.gz.asc b1bbe021af4eab8a4c6bb2e4833c6eaf inkscape-0.48.3.1.zip d9f81d36f1e5a9679911dbc12d53d2b9 inkscape-0.48.3.1.zip.asc SHA1 Sums 23344555a1b5cc7909ad01d926cfaddb67bfbde9 inkscape-0.48.3.1.tar.bz2 780bf43ce5148df35420926702b05afadfade239 inkscape-0.48.3.1.tar.bz2.asc 9a09a97d184e09c2ee7f9956bfe073b7313e919e inkscape-0.48.3.1.tar.gz c8b963d43f56fb7bf42e9474b1b0de7d91be3433 inkscape-0.48.3.1.tar.gz.asc b6de562e8c11442afb3d67a59d4d6f82f0c6edd6 inkscape-0.48.3.1.zip a17c423b151110d2dab6fd770beb20aaf134caa4 inkscape-0.48.3.1.zip.asc --Ted ------------------------------------------------------------------------------ Virtualization& Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

What's it waiting for? Sent from my iPhone On 15 Jun 2012, at 17:15, Johan Engelen <jbc.engelen@...2592...> wrote: > 4 months and counting... > > > > :( >  Johan > > > > On 19-2-2012 4:11, Ted Gould wrote: >> Hey, >> >> So if you're on these mailing list, you know the deal :-)  There are a >> couple build fixes in this update. >> >> Sourceforge: >> >>   http://sourceforge.net/projects/inkscape/files/inkscape/0.48.3.1/ >> >> Launchpad: >> >>   https://launchpad.net/inkscape/0.48.x/0.48.3.1 >> >> MD5 Sums >> >> f0fcc02088cc643634806064e7ab4ec3  inkscape-0.48.3.1.tar.bz2 >> 3e956cd9cf6cf0a22b64a821f5a4084d  inkscape-0.48.3.1.tar.bz2.asc >> ccf8ccd9e66199badb8c35ea3851a888  inkscape-0.48.3.1.tar.gz >> aded57e1a851a5f3d763fd892c085fe1  inkscape-0.48.3.1.tar.gz.asc >> b1bbe021af4eab8a4c6bb2e4833c6eaf  inkscape-0.48.3.1.zip >> d9f81d36f1e5a9679911dbc12d53d2b9  inkscape-0.48.3.1.zip.asc >> >> SHA1 Sums >> >> 23344555a1b5cc7909ad01d926cfaddb67bfbde9  inkscape-0.48.3.1.tar.bz2 >> 780bf43ce5148df35420926702b05afadfade239  inkscape-0.48.3.1.tar.bz2.asc >> 9a09a97d184e09c2ee7f9956bfe073b7313e919e  inkscape-0.48.3.1.tar.gz >> c8b963d43f56fb7bf42e9474b1b0de7d91be3433  inkscape-0.48.3.1.tar.gz.asc >> b6de562e8c11442afb3d67a59d4d6f82f0c6edd6  inkscape-0.48.3.1.zip >> a17c423b151110d2dab6fd770beb20aaf134caa4  inkscape-0.48.3.1.zip.asc >> >>        --Ted >> >> >> >> >> ------------------------------------------------------------------------------ >> Virtualization&  Cloud Management Using Capacity Planning >> Cloud computing makes use of virtualization - but cloud computing >> also focuses on allowing computing to be delivered as a service. >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> >> >> >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Okay... Well, this issue clearly demonstrates the danger of the bus factor. We have one rather experienced packager on OSX who has been unavailable. We also have ~suv, who wants to learn more about it (has proposed modifications and questions) but the "mentor" in this situation has been unavailable in that context as well. Hopefully at some point Michael can write in-depth on the wiki about making the super-awesome packages and how to set up a build machine akin to the one he had which I believe died on him. As the Release Warden I am very torn in this situation. In the past there has been community backlash when we've announced a release and packages have been unavailable for a specific platform. They effectively feel like they're second class citizens. Knowing this, I really feel like I need to hold a hard line about not making any announcement. However, given that this is an open and community project, as well as at this point a substantial amount of time has passed, I'm putting it up to a vote. This vote applies only to core contributors (devs, translators,& bug mavens) and will be open for 1 week. Option 1: Do nothing until we can get proper packages for OSX. Option 2: Do not make announcements and quietly update links where possible. Option 3: Make announcements and apologize and explain why we have left out a group of our users. Please do take into consideration that for Option 3, if you do not help users daily (whether via IRC, forums, twitter, or various other methods) you are putting others on the front line for to deal with upset users. However, it may also lessen their burden of having to repeatedly tell users in bug reports that their bug is fixed and where to get the update. (please think of ~suv and others)

As the Release Warden I am very torn in this situation. In the past there has been community backlash when we've announced a release and packages have been unavailable for a specific platform. They effectively feel like they're second class citizens. Knowing this, I really feel like I need to hold a hard line about not making any announcement. However, given that this is an open and community project, as well as at this point a substantial amount of time has passed, I'm putting it up to a vote. This vote applies only to core contributors (devs, translators, & bug mavens) and will be open for 1 week. Option 1: Do nothing until we can get proper packages for OSX. Option 2: Do not make announcements and quietly update links where possible. Option 3: Make announcements and apologize and explain why we have left out a group of our users.

On Fri, Jun 15, 2012 at 9:33 PM, Josh Andler wrote: > As the Release Warden I am very torn in this situation. In the past > there has been community backlash when we've announced a release and > packages have been unavailable for a specific platform. They > effectively feel like they're second class citizens. Knowing this, I > really feel like I need to hold a hard line about not making any > announcement. However, given that this is an open and community > project, as well as at this point a substantial amount of time has > passed, I'm putting it up to a vote. > > This vote applies only to core contributors (devs, translators,& bug > mavens) and will be open for 1 week. > > Option 1: Do nothing until we can get proper packages for OSX. > Option 2: Do not make announcements and quietly update links where possible. > Option 3: Make announcements and apologize and explain why we have > left out a group of our users. 1 is unacceptable in terms of delivering. 2 is likely to lead to confusions. 3 gets my vote. It _will_ lead to extra work, but among the three options it's the only way you can both deliver and stay in touch with the community.

P.S. The Windows packages are not complete for 0.48.3.1 either: no zip|7z archives nor debug files.

On Thu, Jun 21, 2012 at 1:11 PM, ~suv <suv-sf@...58...> wrote: > P.S. The Windows packages are not complete for 0.48.3.1 either: no > zip|7z archives nor debug files. Are there plans to upload a second set > of packages (including the installer) based on the current devlibs - > before making an announcement? IIUC there have been a few changes since > the first installer build for 0.48.3.1 was created in late February. Thanks for bringing this up. Win32 devs and ~suv, how do you feel about using current devlibs with the release as opposed to based on the rev the existing installer used? I'm not sure if any regressions were introduced or anything.

On 22/06/2012 16:30, ~suv wrote: > On 22/06/2012 02:46, Josh Andler wrote: >> On Thu, Jun 21, 2012 at 1:11 PM, ~suv <suv-sf@...58...> wrote: >>> P.S. The Windows packages are not complete for 0.48.3.1 either: no >>> zip|7z archives nor debug files. Are there plans to upload a second set >>> of packages (including the installer) based on the current devlibs - >>> before making an announcement? IIUC there have been a few changes since >>> the first installer build for 0.48.3.1 was created in late February. >> >> Thanks for bringing this up. Win32 devs and ~suv, how do you feel >> about using current devlibs with the release as opposed to based on >> the rev the existing installer used? I'm not sure if any regressions >> were introduced or anything. > > I'm not aware we had regressions (based on recent trunk builds) reported > in the bug tracker which seem related to the latest changes in the > devlibs (r29-r31 primarily fixed build failures of current trunk). > > Whether the update of cairomm from 1.8.10 to 1.10.0 has any positive (or > negative) side-effects for 0.48.x builds I can't tell. Correction (typo): cairomm was updated from 1.8.4 to 1.10.0 (r30) ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

I compiled the 48.3.1 win32 on my system. - with following changes to the original version - I changed the version info in the inkscape.rc and inkview.ec files in order to match the correct version - I used the latest devlibs, having new cairomm but the binaries diverge somehow. size of INkscape.exe original from sf: 12862464 bytes and my one's 13380096 bytes I could create complete sets of packages: installer, 7zip and debug-info and push those to sf. This will replace a Inkscape-0.48.3.1-1.exe installer by Inkscape-0.48.3.1-2.exe Do you want me to do that? regrads, Adib. -- On Fri, Jun 22, 2012 at 4:32 PM, ~suv <suv-sf@...58...> wrote: > On 22/06/2012 16:30, ~suv wrote: >> On 22/06/2012 02:46, Josh Andler wrote: >>> On Thu, Jun 21, 2012 at 1:11 PM, ~suv <suv-sf@...58...> wrote: >>>> P.S. The Windows packages are not complete for 0.48.3.1 either: no >>>> zip|7z archives nor debug files. Are there plans to upload a second set >>>> of packages (including the installer) based on the current devlibs - >>>> before making an announcement? IIUC there have been a few changes since >>>> the first installer build for 0.48.3.1 was created in late February. >>> >>> Thanks for bringing this up. Win32 devs and ~suv, how do you feel >>> about using current devlibs with the release as opposed to based on >>> the rev the existing installer used? I'm not sure if any regressions >>> were introduced or anything. >> >> I'm not aware we had regressions (based on recent trunk builds) reported >> in the bug tracker which seem related to the latest changes in the >> devlibs (r29-r31 primarily fixed build failures of current trunk). >> >> Whether the update of cairomm from 1.8.10 to 1.10.0 has any positive (or >> negative) side-effects for 0.48.x builds I can't tell. > > Correction (typo): > > cairomm was updated from 1.8.4 to 1.10.0 (r30) > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

This vote applies only to core contributors (devs, translators, & bug mavens) and will be open for 1 week. Option 1: Do nothing until we can get proper packages for OSX. Option 2: Do not make announcements and quietly update links where possible. Option 3: Make announcements and apologize and explain why we have left out a group of our users. Please do take into consideration that for Option 3, if you do not help users daily (whether via IRC, forums, twitter, or various other methods) you are putting others on the front line for to deal with upset users. However, it may also lessen their burden of having to repeatedly tell users in bug reports that their bug is fixed and where to get the update. (please think of ~suv and others) Cheers, Josh