Re: Windows Installer (was: direct object manipulation)
On Apr 1, 2012, at 9:02 AM, Marcus Denker wrote:
> On Apr 1, 2012, at 12:07 AM, Torsten Bergmann wrote:
>>> Yes, and for consistency. Either we go "installer for all three platforms",
>>> or not. Having a one-click for all but windows in addition ist just >confusing.
>> People often provide ZIP or TARs in open source projects for non-Windows
>> and special windows installers for M$ users. Its not uncommmon.
>> So the user can choose which one he wants to use.
> Yes. So now that are two option:
> -> Delay everything until we have that.
> -> Not Delay everything.
> I am always for "Doing while Doing".... and this means:
> -> Finish the one-click build script and activate it for 1.3 and 1.4
+ 1000000 :)
> This is not a lot of work, and then we hat *at least* what we had until know, fully auto-build
> and up to date. *After* that we can improve. But only after that.
> And there are lots of things on the list...
> -> fix the failing test in 1.3Full
> -> fix the remaining 1.4 bugs
> -> do the 1.4 release
> -> run tests on windows besided mac and linux
> -> actually run all tests *before* triggering the build of all depending projects
> -> integrate SSL
> -> merge nativeboost VM with man VM
> -> install Android Dev tools
> -> configure Android build
> -> Look at ARM build of interpreter
> The good news is that we got a bit more manpower lately...
>>> Does it make sense to have a download of 1.2 on the download page?
>> Maybe I'm blind - but on the download page for the 1.2 version - YES:
> Nobody should download 1.2... it's there just for historical reasons.
> Marcus Denker -- http://marcusdenker.de