On Wed, 30 Nov 2005, Heikki Toivonen wrote:
I think we are now ready to decide what to do about this, so I am presenting the following options for a vote: 1) Keep developer (debug) release and end user release. Scrub end user release of all tests and tools. Tell developers, including parcel developers, that they need to use the developer release. Tell QA/testers who want to run unit tests or functional tests that they need to use developer release. Change all documentation to make this clear. Need to change download links on chandler.osafoundation.org to help people find the right release. Note that it won't be possible to run performance tests with releases, one needs to build Chandler for that (either make install or full build).
if the developer is release is 'DEBUG=1' only, then a definite -1 !!
2) Put everything in the end user release, and drop developer release.
If the differential in download size is reasonable, why not ? This proposal seems the most reasonable, +1
3) Make developer and end user releases identical (except for the fact that one has debug binaries and one optimized).
-1, equating 'developer' with 'DEBUG=1' is a mistake.
4) Something else. Please describe.
Do nothing. +1 as well although my preference would be for 2) if it is reasonable.
Andi.. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
