> In order to release the incidence of newbie problems, I'd like to propose > that all concerned developers agree on a checklist to be followed. [...] > I guess the most controversial point is with stipulating the use of MS > Visual C++. I do this because MSVC++ is as common in Windows as gcc is in > Linux, and has (unfortunately) won acceptance as the de-facto standard > Windows C/C++ compiler.
Agreed. However the freenet tray icon builds successfully using either MSVC++ or Cygwin (I made sure of that!) But picking a single test scenario is general practice and anyway the rest of the Windows tools probably _require_ MSVC++. Other Windows developers to confirm? > ( ) 0.5 At least two of the testers should have MS Visual C++ v6.0 or > later, plus NullSoft 'MakeNSIS' installer generator v1.2c or later, > installed Ok, shall we go with "MSVC++ v5.0 or later", since that's what *I* have :) > ( ) 1.4 Open a file called 'freenet.dsw' at the top level within the > wininstall tree (this should be present in CVS), which will start up MS > Visual C++ Errrrr, how do you figure that? There is no .DSW in CVS (developers don't need one, they just load the individual .DSPs) However, we could add one, purely for the purposes of this testing (in which case - good idea). But I wouldn't recommend the developers using it because opening up umpteen projects in Dev Studio makes it run _real_slow_ > ( ) 1.5 Without selecting any MSVC project to be 'active', click on the > 'build' function with MS Visual C++, and verify that *all* components build > successfully without errors. What version of MSVC are you using? On mine I need to click on "Batch Build" and then click "Rebuild All" to build all the projects in the workspace. As far as I know there is no way to NOT select any project to be active. > ( ) 1.6 Right-click on the installer script file, 'freenet.nsi', choose > 'compile nsi', and verify that the script file produces a Freenet installer > without errors Doesn't this require that the tester also has the Nullsoft Install Builder tool fully installed and configured on their system? Sebastian or someone will be able to advise here - I've never used the thing. > ( ) 2.3 Open any available internet connection ? Is this a dial-up speciality? > ( ) 2.4 Double-click on the Freenet 'hops' tray icon, and wait for the tray > icon to appear, without any error indications Doesn't the install script ask if you want to load freenet itself? Need to say explicitly that the tester needs to NOT load freenet here, and to run Freenet from the desktop icon, else you don't have a verifiable test procedure. (Or alternatively, the tester needs to select "run freenet" from the installation jobby, whichever) > If these steps are successfully executed by the quota of test personnel, > machines and operating systems specified above, then the generated version > of Freenet for Windows can be deemed worthy of release. ... Providing you also do: ( ) 2.11 Right click the hops icon and select Configure - and confirm that the Java Configurator appears (or is the config.dll now the 'official' configurator? I forget) ( ) 2.12 (Add something here about changing a setting) and click OK. Confirm that the hops icon briefly changes to a green circle and then returns to normal, to indicate that the settings have been applied. ( ) 2.13 Click on Configure again and confirm that the setting has indeed changed to what you picked in 2.12 ( ) 2.14 Change a different setting to something else. This time click Cancel ( ) 2.15 Confirm you get the green circle. Then click on Configure again and check that the setting is as it was before, i.e. that Cancel prevent the change from being applied. Something like that anyway. Any more? Dave _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
