On Thu, Sep 9, 2010 at 10:39 AM, Martin Sustrik <[email protected]> wrote:
> I would rather say the distinction is between common day-by-day patches > and big codebase changes. For the former, the mailing list process is > sufficient. And there's no real reason why the maintainer should not > follow the process. I guess the maintainer can use the list to solicit review of patches, that's a nice idea. That's especially valuable when we're fixing issues people have been worrying about. If there are no "clients" for a change (yet), it's a bit pointless to announce it. Remember, though, that the process for the maintainer is different than the process for contributors, for good reasons, and there's no benefit in trying to make these a single process. -Pieter -- - Pieter Hintjens iMatix - www.imatix.com _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
