Yes, I'm +1 for this. I've seen TrivialFix used for a lot of non-trivial fixes. May be, we need a spec to define what is trivial? ;) Regards, Vikram Hosakote IRC: vhosakot From: Paul Bourke <paul.bourke at oracle.com<mailto:paul.bourke at oracle.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>> Date: Thursday, November 3, 2016 at 6:51 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>> Subject: [openstack-dev] [kolla] Propose removal of TrivialFix requirement Kolleagues, How do people feel above removing the requirement of having TrivialFix in commit messages where a bug/bp is not required? I'm seeing a lot of valid and important commits being held up because of this, in my opinion, unnecessary requirement. It also causes friction for new contributers to the project. Are there any major benefits we're getting from the use of this tag that I'm missing? Cheers, -Paul __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161111/49c5311d/attachment.html>