Hi Yuv, thanks for the feedback. just a few things:
1 which version did you test? I changed the licence.txt from what it was before, and I removed the URL (the page you refer to does not exist and I don't plan on making it because I never like it if installers start opening web pages, but if you want to make that page I have no problems putting it in the installer). 2 I used the one currently in the SDK. Solving this is way out of my current capabilities and I dont see myself making the time for learning that in the near future. We'll need help here. I guess it's quite common in the open source world that the majority of (potential) users is on a different platform than most of the developments. 3&4 Point taken. But it doesn't have to be perfect. Whining is feedback too. We can always release a 0.8.1 (or whatever you'd call that). I think that even if I did use Dutch Windows I would prefer a fast preview in English to a slow one in Dutch. cheers, allard On Aug 4, 8:20 am, Yuval Levy <[email protected]> wrote: > Hi Allard, > > allard wrote: > > Who else except Henk have tried my builds and Ad's as well? I've had > > around 50 downloads from my site, and there's probable some more from > > panotools.org. Please respond, because IMHO we need to get this > > release out there. The lag between the release of the linux and > > windows versions has been long enough I think. > > I see five issues and we're good to go: > > 1) TEXT > > I've only tested the installer, yesterday, and my feedback [0] to the > text and the URL called on install > (http://hugin.sourceforge.net/installed/0.8.0.shtml) still stands. > > The files license.txt and url.txt, which you can change just before > running InnoSetup, in the INSTALL folder IIRC. > > easy. > > 2) ENBLEND-ENFUSE > > I'll try to run one of the large projects that would kill enblend / > enfuse today and will get back to you here. I wish others who reported > enblend-enfuse problems would do too. > > This is one can be solved before running InnoSetup to compile the > installer. And it should. > > IMO there are three possible solutions: > 1. replace the enblend and enfuse binaries with older ones known to work. > 2. use the ones currently in the SDK. > 3. get the build of the staging branch working and use that one. > > On Ubuntu: the staging branch performs very well; the official v3.2 > fails repeatedly; the last known status from CVS fails repeatedly; the > mercurial repo has at least two branches, and the status of the staging > branch there is incomplete. > > On Windows: the current staging branch does not build yet. I contributed > one fix that improves (but does not solve) the problem. Christoph Spiel > has no access to Windows and does not know MSVC. I need help from > somebody who is more experienced with that compiler. I'll post about > this later. > > 3) TIMING OF RELEASE > > I understand the pressure to release for Windows, but you have to > understand that it is not the same as releasing a tarball or even > releasing a binary for Linux. > > To be on par with the Linux release > > a) remove from your installer: > * all the control point generators > * enblend-enfuse > * libpano > > in Linux these comes as separate tools / installers. In Windows, we > depend on cleaning those up too because shipping them separately would > be a disservice to the users. > > b) distribute the source code only - this is what the 0.8.0 tarball > that's on Sourceforge. Common Ubuntu users are still served with 0.7.0. > You can't expect binaries - whether for Linux, Windows, or OSX, to be > released simultaneously as the tarballs. Not with our current > organization (or lack thereof). > > c) add the superior way of distributing binaries / packages in Linux > distros (which BTW are also not yet at 0.8.0). > > Because in Windows the installer is stand-alone. Once in the world, you > can't take it back. In Linux, you just issue a tarball with a higher > version number and the update trickles down the automatic channels for > the majority of the users. > > I prefer to release later and to have a clean release, than to release > now and get the whiners going. > > 4) QUALITY OF RELEASE > > There are serious issues introduced very recently: a recent change in > libpano causes Hugin to switch locale. All of a sudden your Dutch texts > become English. That's not release quality IMO. Has somebody tested > this? I have English-only Windows and can't. > > In Linux this does not seriously affect the release of Hugin-0.8.0 > because of the above described mechanism. In Windows this will flood us > with complaints. > > Hence: we need more testing. For OS X, Ippei and a few others have been > doing this kind of testing and tweaking off-list. This is why there is > an OS X installer up on SourceForge, and the OSX Hugin users community > deserves applause for this. If Windows users want an installer up on > SourceForge, they have to do a similar effort. There is only so much the > developers can help. > > 5) ACCESS > > Allard, can you please provide me with your SourceForge handle? I want > to give you access to the repository so you can save your changes there > / save them for the future. And maybe even upload the installer, once > it's ready? > > Yuv > > [0] <http://groups.google.com/group/hugin-ptx/msg/3297f6e345105d30> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
