Okay. Let's try this to see if it help us.
I am going to merge https://github.com/apache/bookkeeper/pull/437 so
committers can start use it on merging pull requests.
Please provide any feedback on this tool. We can together improve the tool.
- Sijie
On Fri, Aug 11, 2017 at 4:55 AM, Enrico Olive
Thank you. Good idea
I hope I will be able to use it soon
Enrico
Il ven 11 ago 2017, 13:45 Jia Zhai ha scritto:
> Since it may not easy to change the permissions for contributor, This PR is
> a good alternative to make it easy. Thanks a lot to make it happen.
>
> On Fri, Aug 11, 2017 at 7:07 P
Since it may not easy to change the permissions for contributor, This PR is
a good alternative to make it easy. Thanks a lot to make it happen.
On Fri, Aug 11, 2017 at 7:07 PM, Sijie Guo wrote:
> I've played around github API and come up a change to the merge script. It
> handles adding milesto
I've played around github API and come up a change to the merge script. It
handles adding milestone, labels (area, type and release) when merging pull
requests. If a change is cherry-pick to a branch for bug fixes, a bug fix
release is required to add as well.
this is the pull request - https://gi
Il ven 11 ago 2017, 04:15 Sijie Guo ha scritto:
> On Thu, Aug 10, 2017 at 6:48 PM, Jia Zhai wrote:
>
> > The work flow sounds great.
> > Currently, One problem is that contributor do not have permissions to
> > change the Assignees, Labels, projects and Milestone for both issue and
> > PR. It w
On Thu, Aug 10, 2017 at 6:48 PM, Jia Zhai wrote:
> The work flow sounds great.
> Currently, One problem is that contributor do not have permissions to
> change the Assignees, Labels, projects and Milestone for both issue and
> PR. It would be better if contributor could do that.
>
I am not sure
The work flow sounds great.
Currently, One problem is that contributor do not have permissions to
change the Assignees, Labels, projects and Milestone for both issue and
PR. It would be better if contributor could do that.
On Fri, Aug 11, 2017 at 8:42 AM, Sijie Guo wrote:
> Hi all,
>
> Currentl
Hi all,
Currently we are using Milestone for feature release on Github. However it
will become difficult on doing bug releases, because an issue can only be
assigned to one milestone. So I am proposing:
- add labels for `release/x.y.z` for a given release. for example, if we
need to 4.5.1 release
