This will, however, also take precious space in the Commit Title. And some commits might not be about only one clear-cut component.
On Wed, 11 May 2016 at 11:43 Maximilian Michels <m...@apache.org> wrote: > +1 I think it makes it easier to see at a glance to which part of Beam > a commit belongs. We could use the Jira components as tags. > > On Wed, May 11, 2016 at 11:09 AM, Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > Hi Manu, > > > > good idea. Theoretically the component in the corresponding Jira should > give > > the information, but for convenience, we could add a "tag" in the commit > > comment. > > > > Regards > > JB > > > > > > On 05/10/2016 06:27 AM, Manu Zhang wrote: > >> > >> Guys, > >> > >> As I've been developing Gearpump runner for Beam, I've closely watched > the > >> pull requests updates for API changes. Sometimes, it turns out changes > are > >> only to be applied to a specific runner after I go through the codes. > >> Could > >> we add a tag in the pull request title / commit comment to mark whether > >> it's API change or Runner specific change, or something else, like, > >> [BEAM-XXX] [Direct-Java] Comments... ? > >> > >> Thanks, > >> Manu Zhang > >> > > > > -- > > Jean-Baptiste Onofré > > jbono...@apache.org > > http://blog.nanthrax.net > > Talend - http://www.talend.com >
