On 19/6/11 22:11, Josh Andler wrote:
2011/6/19 Jon Cruz <jon@...18...>
For the devlibs, I would very very strongly advise against using experimental unless it had been fully and carefully tested to support our needs. We're already having a lot of issues with tablet users, so it would be good to avoid such breakage. Keep in mind that bumping the devlibs to more unstable versions pushes a very heavy burden onto our lest technically adept yet largest audience. Breaking things in Windows, even in dailies, can really give Inkscape a bad name and hurt adoption.
Okay, but with tablets on Windows, in my experience the current devlibs actually recognize that I have a tablet attached as opposed to 0.48.1 (where it shows nothing). Either way, it's irrelevant because the tablet stuff is nonfunctional for me with either version of devlibs. I question if it's not just something broken within Inkscape as opposed to only being the devlibs at this point. Besides, I don't know any project that advocates using development/nightly builds for anything but testing.
Maybe the devlibs for Windows could be branched into stable and devel:
- stable for (bug-fix) releases - devel for development builds from current trunk
This could ease the release process for the Windows packages without having to delve into reverting to older bzr revisions of the devlibs, while allowing to provide unstable development snapshots with more recent versions of cairo (and possibly Gtk+).
It seems to make sense to me to make a notation of which build is the last nightly to use the current devlibs, so if people do run into issues with newer cairo, we can tell them the last known good one.
The packaging script used for Mac OS X builds does create a text file listing essential data (OS version, compiler, versions of including libs) [1] for each completed build, and the text file gets uploaded to modevia together with the archive (DMG). Maybe something similar could be added to the packaging routines on Windows too, so that for each snapshot build uploaded to modevia [2] there's an accompanying, versioned readme file.
~suv
[1] latest file for today's snapshot: http://inkscape.modevia.com/macosx-snap/Inkscape-r10325-10.5+-UNIVERSAL-info.txt [2] http://inkscape.modevia.com/win32/?C=M;O=D