>From an interopability standpoint I would vote for #1. My only thought is if >you want the PHP/WSAS/MySQL to exist as a download seperate from .NET how >would that be handled?
________________________________________ From: Selvaratnam Uthaiyashankar [[email protected]] Sent: Thursday, April 23, 2009 1:10 AM To: [email protected] Subject: Finalizing Release artifacts for M1 Hi, We have to finalize what are the release artifacts we are going to release. I can think of two options. Option 1 ------------- stonehenge-stocktrader-m1-incubating-src | |- dotnet src | |- php src | |- wsas src stonehenge-stocktrader-m1-incubating | |- dotnet bin | |- php (same as src, packed in both places) | |- wsas bin Here we have only two artifacts, but if somebody needs to check only one of the implementation, still they have to download all the other implementations as well. Option 2 -------------- stonehenge-stocktrader-dotnet-m1-incubating stonehenge-stocktrader-dotnet-m1-incubating-src stonehenge-stocktrader-php-m1-incubating stonehenge-stocktrader-wsas-m1-incubating stonehenge-stocktrader-wsas-m1-incubating-src Here, the number of artifacts are high. But users can download individual implementations. I prefer option 1. What others are thinking? In addition to that, all the artifacts should contain following files: * DISCLAIMER * LICENSE * NOTICE * README * Release-Note NOTICE file will have only Apache Licence. Do we have to add any other information? Also, We can generate pdf from wiki page (installation guide) and include in the release packages. Should any other files be added? Any comments? Regards, Shankar -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - "The Open Source SOA Company"
