--- Bruno Postle <bruno@...> wrote:
> There actually are windows binaries on the
> sourceforge site:
> 2. Everything is limited to 160 fisheye FoV.
then the question is: do the developer feel that this
limitation is necessary? if yes, tough luck for those
looking for the unlimited version (though they can
probably find it through unofficial channels or by
compiling themselves with little or no support).
> 3. It is just a zip archive containing the files and
> no installation instructions.
Indeed, and the sourceforge web interface calls it a
"source" file, so many unexperienced users won't even
consider downloading it.
I have some experience with InnoSetup installers and
can volunteer making an installer if the developers
> There is also another windows build system based on
> MSVC, but I have no idea how that works.
The only thing I know about this is that Jim Watters
as an MSVC version on his web page. It says it is
faster but less stable. I personally do not have MSVC
and can't help with that build. As a user, I've been
very satisfied with the MinGW build not to feel the
need to investigate that alternative build which I
guess require Microsoft's Visual C++ which I guess is
not free as MinGW.
> > Maybe what we need is "release management",
> > with an official release following more closely
> > bleeding edge?
> Believe it or not this is what we have.
I believe you have it. I also believe it might need
some communication to deal with the kind of questions
that Erik mentioned. One way or the other.
E.g.: is there a >160° available?
*you* the developer decides if you want to make it
officially available, unofficially available, or not
available at all. What I can help is ask questions and
structure them in an FAQ kind of raster so that when
users ask for information, people willing to support
them know what to answer.
> The bleeding edge is what
> you get from SVN. Each of the last few 'stable'
> releases was tagged in the repository and archives
> uploaded to the sourceforge mirror system.
> > Beyond the officially declared stable release
> > now 2.8.0 as far as I understand it) people should
> > on their own. This is also valid for the <160°
> > Tough luck if the officially released binaries do
> > fulfill user requirements.
> This is exactly how it is, though the most recent
> stable release is
> 2.8.4, and the most recent DLL that works with
> PTStitcher.exe is
This adds a level of complexity. If I was release
manager, I'd put on a website that stable is 2.8.3. I
would not even mention 2.8.4 with its binary
compatibility problems to the general public and if
somebody asks about features that are in 2.8.4 I would
say that these are currently unsupported (they can try
on their own if they want, with no support/help) and
that they can wait for 2.8.5 if they absolutely need
features which are not in 2.8.3.
> You are welcome to take over creating the windows
No intention to "take over" - I will "support" Jim
Watters if he wants my support. I can contribute my
time. I can make the builds in MinGW (though not
MSVC), I can make an InnoSetup installer if instructed
which files to package / install.
> the sourceforge mirror system is still probably the
> best place for them.
then I will either need to pass the file I built to
whoever can put them in the repository (initially I
will anyway be more comfortable if somebody could
review my work before it is published) or access to
the repository itself.
And the general public will have to be made aware that
the files are in the sourceforge mirror system.
The tricky question is: >160° in the sourceforge
mirror, yes or no?
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around