RE: [Rainbowportal-devel] Releases

[mark m. <mar...@ho...>]

Are your suggestions something each developer should do BEFORE
committing new code?

I have added to item 5, and added a new item 6.

Also here are some documentation notes:
*** Unfortunately, I am leaving on vacation in a few more days so
someone else needs to update the install document.

As I think about the current install document, I probably need to split
it into 2 or more docs, a simple install and an admin manual.  But not
until after my vacation.

Mark


-----Original Message-----
From: rai...@li...
[mailto:rai...@li...] On Behalf Of
manu
Sent: Wednesday, June 25, 2003 2:24 PM
To: 'Rainbow developer'
Subject: [Rainbowportal-devel] Releases


HI,
many people request a more stable and bug free installation.
I think we can freeze features soon.
Anyway before doing that I need some suggestions on a base lit of test
to do before releasing. This for avoiding that little problems that may
discourage a new rainbow user.

Here it is my suggestion:

1) Open solution in Visual studio and rebuild it. This may see trivial
but if you use a different solution as I do you get the point. The
solution that should be open is that in Rainbow folder.  This will
avoid:
 - Unreferenced DLL (Esperantus for example... because I live with
Esperantus project in same solution for example)
- Missing files

2) make it using mk.bat and verify it compiles without errors.

3) Update existing db (if applicable) running web site.

4) Create a new db from scratch and see if all scripts run smoothly.

5) Test msi installation (if applicable)

The .msi type auto install is a great idea, then we don't need an
install document, well almost.  I suggest we make the auto install
program do the simplest type of installation: (i.e. databasename =
websitename = rainbow.  Web server, dev environment, SQL all on the same
machine, forms authentication, ...)   Just give users something that
will allow them to quickly get rainbow up and running quickly without
having to worry about things like SQL Authentication method, or
RemoteOnly custom errors, ...

6) The release also needs to be checked against the installation
document to make sure we don't forget to tell people to do something, or
tell them to do something they should not.


Any other ideas?






------------------------------------
Emmanuele De Andreis
Technical Manager
DUEMETRI
Internet Solutions Provider
RAINBOW PORTAL
Main portal - http://www.rainbowportal.net
Sourceforge CVS - http://sourceforge.net/projects/rainbowportal/
Support Forums - http://www.rainbowportal.net/ASPNetForums


-



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Rainbowportal-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rainbowportal-devel