Re: [DISCUSS] Commit tagging

How about we use the components that we also defined for the shepherds as tags? On Mon, Jul 18, 2016 at 3:24 PM, Till Rohrmann wrote: > Then +1 :-) > > On Fri, Jul 15, 2016 at 7:07 PM, Ufuk Celebi wrote: > > > It was intended as Till said... a list of preferred tags. > > > > On Fri, Jul 15, 201

Re: [DISCUSS] Commit tagging

Then +1 :-) On Fri, Jul 15, 2016 at 7:07 PM, Ufuk Celebi wrote: > It was intended as Till said... a list of preferred tags. > > On Fri, Jul 15, 2016 at 6:52 PM, Till Rohrmann > wrote: > > I agree with Robert that it would be a nice to have but not strictly > > required. I think it would help to

Re: [DISCUSS] Commit tagging

It was intended as Till said... a list of preferred tags. On Fri, Jul 15, 2016 at 6:52 PM, Till Rohrmann wrote: > I agree with Robert that it would be a nice to have but not strictly > required. I think it would help to have a list of preferred tags so that > new community members have a place to

Re: [DISCUSS] Commit tagging

I agree with Robert that it would be a nice to have but not strictly required. I think it would help to have a list of preferred tags so that new community members have a place to look them up. Cheers, Till On Fri, Jul 15, 2016 at 11:41 AM, Robert Metzger wrote: > Hi Ufuk, > > I also saw these

Re: [DISCUSS] Commit tagging

Hi Ufuk, I also saw these inconsistencies in the tagging too, but I'm not sure if fixing this is worth the effort. As long as the tag somehow transports the intended message ("a change at the runtime "), its good enou

[DISCUSS] Commit tagging

Hey devs, we currently tag commits with the JIRA issue and component(s), like: [FLINK-3943] [table] Add support for EXCEPT operator I was wondering whether it makes sense to write down a set of common commit tags for new contributors. The set of commit tags is quite unregulated right now and I