Here are my thoughts on how we should handle all these different projects going forward. Hopefully, this will lead to a good discussion and we'll end up with decisions quickly.
Cool Stack ----------- The last release of Cool Stack was done on March 1 and we are desperately due for another update. It would be great to put out a Cool Stack 1.1.1 as a bugfix/minor release. This will be the last release under the "Cool Stack" name and will serve as a means to bring over the Cool Stack community to the opensolaris Web Stack project. We put the release out on SDLC with a link to the download from the Web Stack project and a note on the CoolTools forum announcing the move to Web Stack and that all future discussions/help will be via the webstack-discuss list. More justification for this release at the end of this email. I will circulate the proposed list of stuff to go into 1.1.1 in a separate email and we can have a discussion on the contents of 1.1.1, build process etc. on that thread. Web Stack --------- We should continue to update the Web Stack project components in the repository as we see fit. I have the OSR approved for lighttpd and have another one pending for pcre. As soon as this is approved, lighttpd can go in. (I mention this just as an example). The community can help in identifying other components that they'd like to see in this project. NOTE: In future, while filing OSR's for sfw, we should also mention the Web Stack project as another distribution mechanism, so we can save time on OSR's. The big question of course revolves around the components that also exist in sfw. After the SXDE 12/07 release, we should work on re-arranging the Web Stack repository to avoid duplication. There are several issues : a) We need to have the flexibility to try out new things without affecting sfw. Examples are : apache dtrace module (which is still in the works), MySQL optimizations, additional PHP extensions (that may not make it into SXDE 12/07 or new ones that are just emerging), more recent versions of AMP that have critical bug fixes etc. b) Build processes for Web Stack need to be worked out. If we want this to help bleeding edge developers/deployers, then we should probably consider using different compilers, more rigorous optimization flags (for e.g Cool Stack currently uses -fast which is probably unacceptable for sfw builds) etc. c) Packaging mechanism - do we have identical packages of AMP as sfw or do we want to stick with the "pre-configured, single download" principle of the Cool Stack AMP stack ? As can be seen, these are issues that will need some time to be worked out and that's the reason for my proposal that we put out the Cool Stack 1.1.1 release without worrying about these issues for now i.e. the release targets current Cool Stack customers and the primary purpose is to provide bug fixes and move the community over to Web Stack. Comments ? Shanti
