-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry for the late reply...I agree, it's probably time for the release cycles of the plugins to be somewhat separated, and driven by the needs of each plugin project.
You got my +1. - -john Brett Porter wrote: | Hi, | | What shall we do for the plugin releases as we lead up to the final? | | I'm thinking: | - get them basically finished first (unless the current betas are | fundamentally flawed) | - fix all bugs in the matrix slated for that plugin, polish up docs | (most have had this done by Allan and Johnny - thanks!) | - release a beta | - fix remaining issues | - release final beta of that plugin | - wait for 2.0 release | - upgrade libs and release "final" of the plugin | - celebrate, and move on to the next version :) | | I'd very much like them to be done one at a time (not 15 releases at the | same time as the core), and driven by those that primarily use them and | work on the issues. | | Sound ok? Any feedback? | | Cheers, | Brett | | --------------------------------------------------------------------- | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDPAP7K3h2CZwO/4URArMWAJ97PgKLBY7Ei3ks/UdfonMpXwt+QwCfY8vq Ec1mLJZM7BFUbcKyCRw8ZfQ= =SAH6 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
