Chameleon Overview
FAQ Questions
- What is Chameleon?
- Where can I get Chameleon?
- What is Chameleon's licensing policy?
- How are Chameleon releases managed?
- What do you mean by the various release states (like BETA, TECHNICAL RELEASE, ...)?
FAQ Answers
Q: What is Chameleon?
A: Chameleon is an easy-to-use, highly configurable, distributed environment for developing Web-mapping applications. It is built on OpenGIS Consortium standards for Web Mapping Services (WMS) and WMT Viewer Contexts. To learn more about Chameleon, please go to the MapTools.org Chameleon home page.
Q: Where can I get Chameleon?
A: Standard source code packages for Chameleon can be found at the Chameleon download page. A pre-configured Chameleon package for Windows platforms can also be found on the MS4W (MapServer for Windows) download page.
Q: What is Chameleon's licensing policy?
A: To put it simply, Chameleon is free! You can download and distribute the Chameleon software to as many CPUs as you like. Chameleon is an Open Source product with a very positive and growing community of actively sharing users. For further details on the Chameleon copyright and licensing terms, please look at the chameleon license page in "Docs".
Q: How are Chameleon releases managed?
A: All tasks related to Chameleon are tracked in Bugzilla. Tasks include feature requests and bugs related to various technical (code) and non-technical (documentation) parts of Chameleon. We use a feature in Bugzilla called 'Target Milestone' to associate tasks with various releases. The product managers review all bugs on a regular basis and decide which features and bugs will be included in the next release by creating a milestone and then targetting those bugs to that milestone. The developers (including those that work on documentation) then have a list of tasks to complete before Chameleon can be released. Once all the bugs for a particular milestone are resolved (fixed, invalid, wontfix etc), an internal package is built for testing. QA then queries the bug database for all resolved bugs for the given milestone and then begins the (sometimes lengthy) process of verifying every bug. Once every bug has been verified, the release is ready for the public and we make an announcement.
This process happens for every release, including alpha, beta, release candidate, technical release and product release.
Q: What do you mean by the various release states (like BETA, TECHNICAL RELEASE, ...)?
A:
|
