mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suneel Marthi <smar...@apache.org>
Subject Re: [DISCUSSION] Adding labels to PRs
Date Fri, 10 Nov 2017 01:26:48 GMT
When u create a Jira - the jira carries a label of 'New Feature', 'Bug',
'Task' etc..., there's no need to again label each PR individually as long
as the Jira### is referenced in the PR.



On Fri, Nov 10, 2017 at 4:13 AM, Meghna Baijal <meghnabaijal2017@gmail.com>
wrote:

> Hello All,
>
> Currently, there is no process in place to identify the new features that
> go into every release.  All the commits since the previous release are
> manually parsed to find the important changes that go into the release
> notes.
>
>
> In order to improve this process, I want to start a discussion on the
> following options -
>
> 1. *Better PR titles* - if possible, these should be good enough to be
> picked as is into the release notes.
>
> 2. *JIRA Issues* - each commit should be tagged with an associated JIRA
> issue. This issue should describe the problem. JIRA tickets can be used to
> automate the generation of release notes.
>
> 3. *Adding Labels to the PRs/Commits* - There can be a set of 3-5 labels
> such as ‘Bug-Fix’, ‘New Feature’, ‘Docs’, ‘Minor Change’ etc. Atleast
those
> PRs which are important and should be included in the release notes should
> be labeled.
> However, labels can only be added by those with write access to the repo.
> So the committers will have to triage this label addition as they
> review/merge the PRs.
>
>
> Do you think these changes are feasible? Will they help? What other options
> should be considered?
>
> Thanks,
> Meghna Baijal
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message