Hi,
preview: do you object on the grounds of this being against established process rules, or do you really think it was too early quality-wise (which is a slippery slope, surely, because quality will always get better if one waits some more...)?
both, but mainly the process. First preview not contained only two cwses mixed together, but also hack patches that were never integrated (like enabling native filepicker by default for all platforms) etc. This was a huge problem in the future because people reported issues in filepicker, but filepicker was NOT integrated at that time yet, so we spent lot of time hunting non-existing bugs.
I'm not against regularly building/uploading development snapshots of aquavcl02 or similar cwses based builds.
But I'm against making hack-builds available to general public. It should be very clear what the build contains when we release it to general public so we are able to process incoming stream of bugs properly/effectively.
For general public, only master builds should be used (e.g. SRC680_m221). For developers/active community testers, we could also produce cws builds (like aquavcl02 build). But we should not announce such builds as Macport as "Preview XI", we should only use master builds for this purpose.
But ok, it happened. I'm now talking about the future. -- Pavel Janík --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
