[Dbix-class] PROPOSAL: merging Haarg's patch and making it easier to do simple merges / emergency fixes

[Karen Etheridge]

I vote yes on proposal 1 (https://github.com/dbsrgits/dbix-class/pull/114
should be merged), so long as (as discussed) the documentation is suitably
amended to allow such a merge.

I vote no on proposal 2, to allow immediate merge and release of "obvious"
changes.  I would be more likely to support this proposal if it was amended
to either allow immediate merges but not release, or only allow *trial*
(unindexed) releases. I feel to do an immediate non-trial release requires
more oversight at this point still.

On Fri, Jan 12, 2018 at 8:25 AM, John Napiorkowski <jjn1056 at yahoo.com>
wrote:

> Two proposals for the governing committee
>
> First proposal:
>
> Haarg proposed a small and obvious fix here => https://github.com/
> dbsrgits/dbix-class/pull/114
>
> I think it should be merged.
>
> Second proposal:
>
> Anyone with comaint or first come should be able to merge and release as
> needed trivial or obvious patches (such as the one Haag proposed),
> documentation improvements, or fixes required immediately because of
> security issues or problems with upstream dependencies.  In those cases we
> can allow to skip voting and merge / release code at once.
>
> Regards,
>
> John Napiorkowski
>
> _______________________________________________
> List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
> IRC: irc.perl.org#dbix-class
> SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
> Searchable Archive: http://www.grokbase.com/group/
> dbix-class at lists.scsys.co.uk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scsys.co.uk/pipermail/dbix-class/attachments/20180113/06fe2427/attachment.htm>