Re: Moving Celix issue management to GitHub

2019-09-29 Thread Pepijn Noltes
Hi Roy, On Sat, Sep 28, 2019 at 7:46 PM Roy Lenferink wrote: > > This is finished now. For all open jira issues matching GitHub issues have > been created which we can use for further development. Probably not all > issues are valid anymore but that's something we still need to have a look > at.

Re: Moving Celix issue management to GitHub

2019-09-28 Thread Roy Lenferink
This is finished now. For all open jira issues matching GitHub issues have been created which we can use for further development. Probably not all issues are valid anymore but that's something we still need to have a look at. The milestone page [1] lists the tasks we still need to do for release 2.

Re: Moving Celix issue management to GitHub

2019-09-25 Thread Roy Lenferink
Issue created: https://issues.apache.org/jira/browse/INFRA-19153 Op zo 22 sep. 2019 om 21:12 schreef Pepijn Noltes : > Hi All, > > On Sun, Sep 22, 2019 at 4:38 PM Roy Lenferink > wrote: > > > > Everyone, > > > > Since Apache now grants write access to GitHub repos I think > > it's time to drop J

Re: Moving Celix issue management to GitHub

2019-09-22 Thread Pepijn Noltes
Hi All, On Sun, Sep 22, 2019 at 4:38 PM Roy Lenferink wrote: > > Everyone, > > Since Apache now grants write access to GitHub repos I think > it's time to drop Jira as issue tracker and move our issue management > to GitHub issues. > > GitHub issues supports: > - Labels, which we can use to deter

Moving Celix issue management to GitHub

2019-09-22 Thread Roy Lenferink
Everyone, Since Apache now grants write access to GitHub repos I think it's time to drop Jira as issue tracker and move our issue management to GitHub issues. GitHub issues supports: - Labels, which we can use to determine the type of an issue (e.g. a 'bug' or 'enhancement') - Milestones, which w