You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Antonio <an...@vieiro.net> on 2017/11/16 20:05:55 UTC
Kanban / Scrum / Boards
Do we want to try out Jira's Kanban/Scrum boards like these [1] in
Apache Mesos?
Maybe the icon/splash/about dialog set of issues is a small project we
could use to give Jira's boards a spin.
Cheers,
Antonio
[1]
- Apache Mesos Kanban
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
- Apache Mesos Sprint 68
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
Re: Xmas IDE Release Plan Proposal (was Re: Kanban / Scrum / Boards)
Posted by John McDonnell <mc...@gmail.com>.
New Kanban Board setup for the tasks/tickets relating to a Java 9 IDE release:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=219
It's currently empty, for ANY tickets that should be worked on related
to this Release can we put in a label 'Java9-IDE' as the filter for
the board uses the following query:
project = NETBEANS AND labels = 'Java9-IDE' ORDER BY Rank ASC
Regards
John
On 23 November 2017 at 18:35, Jan Lahoda <la...@gmail.com> wrote:
> Hi,
>
> On Thu, Nov 23, 2017 at 7:03 PM, Antonio <an...@vieiro.net> wrote:
>
>> Hi all,
>>
>> For the "2017 Xmas NetBeans Java 9 IDE" (long name? right date?) I think
>> we could have the following Kanban stages in an IDE specific Kanban board.
>>
>
> I suspect the timing may be about right (I doubt we can plan for a much
> sooner release).
>
>
>>
>> I think we could think of these as an empowered version of the old
>> NetBeans' bugzilla "plan" and "umbrella" keywords that have been used over
>> the years, but with a visual interface (as in [1]).
>>
>> For the IDE we could set up a Kanban board with the following stages, for
>> example:
>>
>> 0. Find all offenders
>> I think Jan Lahoda has done a great job detecting offending licensed
>> modules (Hibernate, Beans Binding, etc.). But, are there any others? Maybe
>> our first stage could be to identify which are the offenders. After all we
>> wouldn't want to find offenders later on and start all over again.
>>
>
> I think "ant verify-libs-and-licenses" is the tool for this. It will
> (should) report binaries without licenses; malformed files with licenses,
> GPL dependencies (with exceptions). If we find a problem, we should at
> least try to add a check for it to this task, so that the checks run for us
> automatically.
>
> (See also:
> https://github.com/apache/incubator-netbeans/pull/285
> )
>
> Jan
>
>
>> 1. Evaluate the damage
>> Do a second "dependency analysys" phase, where we determine what the
>> dependencies are with Hibernate, Beans Binding and other offending modules.
>> Evaluate the damage among us. This could contain one or more issues (one
>> issue for hibernate dependencies, another for beans binding, etc.).
>>
>> 2. Get rid of offenders
>> We could then think about trimming the "ide" cluster as Emilian suggested
>> in another email. Offending modules could be set up somewhere else at
>> github, with some plugin download URL. Issues here could be "cluster
>> trimming", "github setup", "github move", and "create plugin url to
>> download offending modules". Is this just one stage or two?
>>
>> 3. Prepare the website (specific Kanban board for this?)
>> We could then start preparing the website. Wade Chandler has done a superb
>> job and we have 1.5Gb of web pages to classify and organize in sections.
>> This is so huge that I think we'll need a specific board for this to get
>> done. Just classifying the web site into sections seems dauntling to me
>> (tutorials/arch.xml links/javadoc/branding...).
>>
>> 4. Prepare the IDE release.
>> Build the resulting cluster and start with tests and QA Testing.
>>
>> 5. Xmas party
>>
>> I assume we can add/remove stages and fine tune the board as we move
>> along. Opinions? Ideas?
>>
>> Cheers,
>> Antonio
>>
>> [1] https://docs.microsoft.com/en-us/vsts/work/kanban/add-columns
>>
>> P.S.:
>>
>> Some time in the future we could use Kanban boards for documenting/running
>> existing NetBeans workflows.
>>
>> The workflow described at http://wiki.netbeans.org/APIDevelopment
>> describes what was required to submit a new NetBeans module. I find these
>> workflows very valuable because they have worked well over the years, and I
>> wouldn't like losing these in the transition.
>>
>>
>> El 23/11/17 a las 18:19, John McDonnell escribió:
>>
>>> Very easy to create, I think the catch here will be making sure
>>> tickets are marked with a label or something and we only include those
>>> labelled items.
>>>
>>>
>>> Regards
>>>
>>> John
>>>
>>> On 23 November 2017 at 17:13, Antonio <an...@vieiro.net> wrote:
>>>
>>>> What about a "NetBeans 2017 Java 9 IDE" board we can use for releasing
>>>> the
>>>> Java IDE by Xmas?
>>>>
>>>> Cheers,
>>>> Antonio
>>>>
>>>> El 23/11/17 a las 18:10, John McDonnell escribió:
>>>>
>>>> It's very slow to load...
>>>>>
>>>>> Probably due to the number of sections. What we might do is setup a
>>>>> Kanban board per cluster maybe and have then smaller groups in each
>>>>> board if that improves the performance of the board...
>>>>>
>>>>> On 23 November 2017 at 17:02, Antonio <an...@vieiro.net> wrote:
>>>>>
>>>>>>
>>>>>> Hi John,
>>>>>>
>>>>>> This is great news! I'll take an in-dept look later on. It seems to me
>>>>>> the
>>>>>> page is very slow, isn't it? Or is it just me?
>>>>>>
>>>>>> Thanks,
>>>>>> Antonio
>>>>>>
>>>>>> El 23/11/17 a las 17:25, John McDonnell escribió:
>>>>>>
>>>>>> So the Kanban board is now visible here to all:
>>>>>>>
>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>>>>
>>>>>>> I still need to kick off the change in ticket types with the Infra
>>>>>>> team, in order to enable epics.
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> On 18 November 2017 at 08:24, Antonio <an...@vieiro.net> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> So I played the "find the differences" game at [1] and I think that
>>>>>>>> this
>>>>>>>> holds:
>>>>>>>>
>>>>>>>> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
>>>>>>>> (documentation,
>>>>>>>> task, Sub-task).
>>>>>>>>
>>>>>>>> I don't know the differences between "Task" and "Technical task",
>>>>>>>> maybe
>>>>>>>> we
>>>>>>>> can go with the simplest one, the "Agile Scrum Issue Type" and decide
>>>>>>>> whether a task is "Technical" or not by adding a prefix in the task
>>>>>>>> name.
>>>>>>>>
>>>>>>>> So +1 for the "Agile Scrum Issue Type".
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Antonio
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> Find the differences game:
>>>>>>>>
>>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue
>>>>>>>> +Type+Schemes
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 17/11/17 17:46, John McDonnell wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Had a quick look before I created the INFRA ticket, and it seems
>>>>>>>>> that
>>>>>>>>> there are 4 possible settings for Apache's JIRA:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue
>>>>>>>>> +Type+Schemes
>>>>>>>>>
>>>>>>>>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>>>>>>>>> When we raise a ticket, we should probably know which scheme we want
>>>>>>>>> to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
>>>>>>>>> logical to me, but I'm just one person.
>>>>>>>>>
>>>>>>>>> Anyone see any need for any of the other schemes?
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>> John
>>>>>>>>>
>>>>>>>>> On 17 November 2017 at 08:45, John McDonnell
>>>>>>>>> <mc...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Wade,
>>>>>>>>>>
>>>>>>>>>> While I wait for the INFRA ticket to be looked at, I've added you
>>>>>>>>>> to
>>>>>>>>>> the board's admin list, so I believe you should be able to see it
>>>>>>>>>> now.
>>>>>>>>>> I've created swimlanes for all top-level components that came from
>>>>>>>>>> BugZilla.
>>>>>>>>>>
>>>>>>>>>> As for epics, I've not seen this listed in the admin portal, seems
>>>>>>>>>> we
>>>>>>>>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>>>>>>>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to
>>>>>>>>>> be
>>>>>>>>>> created. I assume this might require an INFRA ticket as well?
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>> John
>>>>>>>>>>
>>>>>>>>>> On 17 November 2017 at 04:00, Wade Chandler <
>>>>>>>>>> wadechandler@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> +1 for Kanban
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Nov 16, 2017, at 17:07, John McDonnell
>>>>>>>>>>>> <mc...@gmail.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> I created a basic Kanban board there to get a starting point,
>>>>>>>>>>>> I’ll
>>>>>>>>>>>> look
>>>>>>>>>>>> to clean it up next week.
>>>>>>>>>>>>
>>>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
>>>>>>>>>>>> iew=216
>>>>>>>>>>>>
>>>>>>>>>>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapid
>>>>>>>>>>>> View=216>
>>>>>>>>>>>>
>>>>>>>>>>>> I’ll also need to make it visible to others, since its restricted
>>>>>>>>>>>> at
>>>>>>>>>>>> the moment - Think this needs an INFRA ticket…
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>>
>>>>>>>>>>>> John
>>>>>>>>>>>>
>>>>>>>>>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1]
>>>>>>>>>>>>> in
>>>>>>>>>>>>> Apache Mesos?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Maybe the icon/splash/about dialog set of issues is a small
>>>>>>>>>>>>> project
>>>>>>>>>>>>> we
>>>>>>>>>>>>> could use to give Jira's boards a spin.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cheers,
>>>>>>>>>>>>> Antonio
>>>>>>>>>>>>>
>>>>>>>>>>>>> [1]
>>>>>>>>>>>>>
>>>>>>>>>>>>> - Apache Mesos Kanban
>>>>>>>>>>>>>
>>>>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
>>>>>>>>>>>>> iew=111
>>>>>>>>>>>>>
>>>>>>>>>>>>> - Apache Mesos Sprint 68
>>>>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
>>>>>>>>>>>>> iew=62
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
Re: Xmas IDE Release Plan Proposal (was Re: Kanban / Scrum / Boards)
Posted by Jan Lahoda <la...@gmail.com>.
Hi,
On Thu, Nov 23, 2017 at 7:03 PM, Antonio <an...@vieiro.net> wrote:
> Hi all,
>
> For the "2017 Xmas NetBeans Java 9 IDE" (long name? right date?) I think
> we could have the following Kanban stages in an IDE specific Kanban board.
>
I suspect the timing may be about right (I doubt we can plan for a much
sooner release).
>
> I think we could think of these as an empowered version of the old
> NetBeans' bugzilla "plan" and "umbrella" keywords that have been used over
> the years, but with a visual interface (as in [1]).
>
> For the IDE we could set up a Kanban board with the following stages, for
> example:
>
> 0. Find all offenders
> I think Jan Lahoda has done a great job detecting offending licensed
> modules (Hibernate, Beans Binding, etc.). But, are there any others? Maybe
> our first stage could be to identify which are the offenders. After all we
> wouldn't want to find offenders later on and start all over again.
>
I think "ant verify-libs-and-licenses" is the tool for this. It will
(should) report binaries without licenses; malformed files with licenses,
GPL dependencies (with exceptions). If we find a problem, we should at
least try to add a check for it to this task, so that the checks run for us
automatically.
(See also:
https://github.com/apache/incubator-netbeans/pull/285
)
Jan
> 1. Evaluate the damage
> Do a second "dependency analysys" phase, where we determine what the
> dependencies are with Hibernate, Beans Binding and other offending modules.
> Evaluate the damage among us. This could contain one or more issues (one
> issue for hibernate dependencies, another for beans binding, etc.).
>
> 2. Get rid of offenders
> We could then think about trimming the "ide" cluster as Emilian suggested
> in another email. Offending modules could be set up somewhere else at
> github, with some plugin download URL. Issues here could be "cluster
> trimming", "github setup", "github move", and "create plugin url to
> download offending modules". Is this just one stage or two?
>
> 3. Prepare the website (specific Kanban board for this?)
> We could then start preparing the website. Wade Chandler has done a superb
> job and we have 1.5Gb of web pages to classify and organize in sections.
> This is so huge that I think we'll need a specific board for this to get
> done. Just classifying the web site into sections seems dauntling to me
> (tutorials/arch.xml links/javadoc/branding...).
>
> 4. Prepare the IDE release.
> Build the resulting cluster and start with tests and QA Testing.
>
> 5. Xmas party
>
> I assume we can add/remove stages and fine tune the board as we move
> along. Opinions? Ideas?
>
> Cheers,
> Antonio
>
> [1] https://docs.microsoft.com/en-us/vsts/work/kanban/add-columns
>
> P.S.:
>
> Some time in the future we could use Kanban boards for documenting/running
> existing NetBeans workflows.
>
> The workflow described at http://wiki.netbeans.org/APIDevelopment
> describes what was required to submit a new NetBeans module. I find these
> workflows very valuable because they have worked well over the years, and I
> wouldn't like losing these in the transition.
>
>
> El 23/11/17 a las 18:19, John McDonnell escribió:
>
>> Very easy to create, I think the catch here will be making sure
>> tickets are marked with a label or something and we only include those
>> labelled items.
>>
>>
>> Regards
>>
>> John
>>
>> On 23 November 2017 at 17:13, Antonio <an...@vieiro.net> wrote:
>>
>>> What about a "NetBeans 2017 Java 9 IDE" board we can use for releasing
>>> the
>>> Java IDE by Xmas?
>>>
>>> Cheers,
>>> Antonio
>>>
>>> El 23/11/17 a las 18:10, John McDonnell escribió:
>>>
>>> It's very slow to load...
>>>>
>>>> Probably due to the number of sections. What we might do is setup a
>>>> Kanban board per cluster maybe and have then smaller groups in each
>>>> board if that improves the performance of the board...
>>>>
>>>> On 23 November 2017 at 17:02, Antonio <an...@vieiro.net> wrote:
>>>>
>>>>>
>>>>> Hi John,
>>>>>
>>>>> This is great news! I'll take an in-dept look later on. It seems to me
>>>>> the
>>>>> page is very slow, isn't it? Or is it just me?
>>>>>
>>>>> Thanks,
>>>>> Antonio
>>>>>
>>>>> El 23/11/17 a las 17:25, John McDonnell escribió:
>>>>>
>>>>> So the Kanban board is now visible here to all:
>>>>>>
>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>>>
>>>>>> I still need to kick off the change in ticket types with the Infra
>>>>>> team, in order to enable epics.
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> John
>>>>>>
>>>>>> On 18 November 2017 at 08:24, Antonio <an...@vieiro.net> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> So I played the "find the differences" game at [1] and I think that
>>>>>>> this
>>>>>>> holds:
>>>>>>>
>>>>>>> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
>>>>>>> (documentation,
>>>>>>> task, Sub-task).
>>>>>>>
>>>>>>> I don't know the differences between "Task" and "Technical task",
>>>>>>> maybe
>>>>>>> we
>>>>>>> can go with the simplest one, the "Agile Scrum Issue Type" and decide
>>>>>>> whether a task is "Technical" or not by adding a prefix in the task
>>>>>>> name.
>>>>>>>
>>>>>>> So +1 for the "Agile Scrum Issue Type".
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Antonio
>>>>>>>
>>>>>>> [1]
>>>>>>> Find the differences game:
>>>>>>>
>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue
>>>>>>> +Type+Schemes
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 17/11/17 17:46, John McDonnell wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Had a quick look before I created the INFRA ticket, and it seems
>>>>>>>> that
>>>>>>>> there are 4 possible settings for Apache's JIRA:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue
>>>>>>>> +Type+Schemes
>>>>>>>>
>>>>>>>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>>>>>>>> When we raise a ticket, we should probably know which scheme we want
>>>>>>>> to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
>>>>>>>> logical to me, but I'm just one person.
>>>>>>>>
>>>>>>>> Anyone see any need for any of the other schemes?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> John
>>>>>>>>
>>>>>>>> On 17 November 2017 at 08:45, John McDonnell
>>>>>>>> <mc...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Wade,
>>>>>>>>>
>>>>>>>>> While I wait for the INFRA ticket to be looked at, I've added you
>>>>>>>>> to
>>>>>>>>> the board's admin list, so I believe you should be able to see it
>>>>>>>>> now.
>>>>>>>>> I've created swimlanes for all top-level components that came from
>>>>>>>>> BugZilla.
>>>>>>>>>
>>>>>>>>> As for epics, I've not seen this listed in the admin portal, seems
>>>>>>>>> we
>>>>>>>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>>>>>>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to
>>>>>>>>> be
>>>>>>>>> created. I assume this might require an INFRA ticket as well?
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>> John
>>>>>>>>>
>>>>>>>>> On 17 November 2017 at 04:00, Wade Chandler <
>>>>>>>>> wadechandler@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> +1 for Kanban
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Nov 16, 2017, at 17:07, John McDonnell
>>>>>>>>>>> <mc...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> I created a basic Kanban board there to get a starting point,
>>>>>>>>>>> I’ll
>>>>>>>>>>> look
>>>>>>>>>>> to clean it up next week.
>>>>>>>>>>>
>>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
>>>>>>>>>>> iew=216
>>>>>>>>>>>
>>>>>>>>>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapid
>>>>>>>>>>> View=216>
>>>>>>>>>>>
>>>>>>>>>>> I’ll also need to make it visible to others, since its restricted
>>>>>>>>>>> at
>>>>>>>>>>> the moment - Think this needs an INFRA ticket…
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>>
>>>>>>>>>>> John
>>>>>>>>>>>
>>>>>>>>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1]
>>>>>>>>>>>> in
>>>>>>>>>>>> Apache Mesos?
>>>>>>>>>>>>
>>>>>>>>>>>> Maybe the icon/splash/about dialog set of issues is a small
>>>>>>>>>>>> project
>>>>>>>>>>>> we
>>>>>>>>>>>> could use to give Jira's boards a spin.
>>>>>>>>>>>>
>>>>>>>>>>>> Cheers,
>>>>>>>>>>>> Antonio
>>>>>>>>>>>>
>>>>>>>>>>>> [1]
>>>>>>>>>>>>
>>>>>>>>>>>> - Apache Mesos Kanban
>>>>>>>>>>>>
>>>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
>>>>>>>>>>>> iew=111
>>>>>>>>>>>>
>>>>>>>>>>>> - Apache Mesos Sprint 68
>>>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
>>>>>>>>>>>> iew=62
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>>>
>>>
Xmas IDE Release Plan Proposal (was Re: Kanban / Scrum / Boards)
Posted by Antonio <an...@vieiro.net>.
Hi all,
For the "2017 Xmas NetBeans Java 9 IDE" (long name? right date?) I think
we could have the following Kanban stages in an IDE specific Kanban board.
I think we could think of these as an empowered version of the old
NetBeans' bugzilla "plan" and "umbrella" keywords that have been used
over the years, but with a visual interface (as in [1]).
For the IDE we could set up a Kanban board with the following stages,
for example:
0. Find all offenders
I think Jan Lahoda has done a great job detecting offending licensed
modules (Hibernate, Beans Binding, etc.). But, are there any others?
Maybe our first stage could be to identify which are the offenders.
After all we wouldn't want to find offenders later on and start all over
again.
1. Evaluate the damage
Do a second "dependency analysys" phase, where we determine what the
dependencies are with Hibernate, Beans Binding and other offending
modules. Evaluate the damage among us. This could contain one or more
issues (one issue for hibernate dependencies, another for beans binding,
etc.).
2. Get rid of offenders
We could then think about trimming the "ide" cluster as Emilian
suggested in another email. Offending modules could be set up somewhere
else at github, with some plugin download URL. Issues here could be
"cluster trimming", "github setup", "github move", and "create plugin
url to download offending modules". Is this just one stage or two?
3. Prepare the website (specific Kanban board for this?)
We could then start preparing the website. Wade Chandler has done a
superb job and we have 1.5Gb of web pages to classify and organize in
sections. This is so huge that I think we'll need a specific board for
this to get done. Just classifying the web site into sections seems
dauntling to me (tutorials/arch.xml links/javadoc/branding...).
4. Prepare the IDE release.
Build the resulting cluster and start with tests and QA Testing.
5. Xmas party
I assume we can add/remove stages and fine tune the board as we move
along. Opinions? Ideas?
Cheers,
Antonio
[1] https://docs.microsoft.com/en-us/vsts/work/kanban/add-columns
P.S.:
Some time in the future we could use Kanban boards for
documenting/running existing NetBeans workflows.
The workflow described at http://wiki.netbeans.org/APIDevelopment
describes what was required to submit a new NetBeans module. I find
these workflows very valuable because they have worked well over the
years, and I wouldn't like losing these in the transition.
El 23/11/17 a las 18:19, John McDonnell escribió:
> Very easy to create, I think the catch here will be making sure
> tickets are marked with a label or something and we only include those
> labelled items.
>
>
> Regards
>
> John
>
> On 23 November 2017 at 17:13, Antonio <an...@vieiro.net> wrote:
>> What about a "NetBeans 2017 Java 9 IDE" board we can use for releasing the
>> Java IDE by Xmas?
>>
>> Cheers,
>> Antonio
>>
>> El 23/11/17 a las 18:10, John McDonnell escribió:
>>
>>> It's very slow to load...
>>>
>>> Probably due to the number of sections. What we might do is setup a
>>> Kanban board per cluster maybe and have then smaller groups in each
>>> board if that improves the performance of the board...
>>>
>>> On 23 November 2017 at 17:02, Antonio <an...@vieiro.net> wrote:
>>>>
>>>> Hi John,
>>>>
>>>> This is great news! I'll take an in-dept look later on. It seems to me
>>>> the
>>>> page is very slow, isn't it? Or is it just me?
>>>>
>>>> Thanks,
>>>> Antonio
>>>>
>>>> El 23/11/17 a las 17:25, John McDonnell escribió:
>>>>
>>>>> So the Kanban board is now visible here to all:
>>>>>
>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>>
>>>>> I still need to kick off the change in ticket types with the Infra
>>>>> team, in order to enable epics.
>>>>>
>>>>> Regards
>>>>>
>>>>> John
>>>>>
>>>>> On 18 November 2017 at 08:24, Antonio <an...@vieiro.net> wrote:
>>>>>>
>>>>>>
>>>>>> So I played the "find the differences" game at [1] and I think that
>>>>>> this
>>>>>> holds:
>>>>>>
>>>>>> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
>>>>>> (documentation,
>>>>>> task, Sub-task).
>>>>>>
>>>>>> I don't know the differences between "Task" and "Technical task", maybe
>>>>>> we
>>>>>> can go with the simplest one, the "Agile Scrum Issue Type" and decide
>>>>>> whether a task is "Technical" or not by adding a prefix in the task
>>>>>> name.
>>>>>>
>>>>>> So +1 for the "Agile Scrum Issue Type".
>>>>>>
>>>>>> Cheers,
>>>>>> Antonio
>>>>>>
>>>>>> [1]
>>>>>> Find the differences game:
>>>>>>
>>>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 17/11/17 17:46, John McDonnell wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Had a quick look before I created the INFRA ticket, and it seems that
>>>>>>> there are 4 possible settings for Apache's JIRA:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>>>>>
>>>>>>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>>>>>>> When we raise a ticket, we should probably know which scheme we want
>>>>>>> to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
>>>>>>> logical to me, but I'm just one person.
>>>>>>>
>>>>>>> Anyone see any need for any of the other schemes?
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> On 17 November 2017 at 08:45, John McDonnell
>>>>>>> <mc...@gmail.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Wade,
>>>>>>>>
>>>>>>>> While I wait for the INFRA ticket to be looked at, I've added you to
>>>>>>>> the board's admin list, so I believe you should be able to see it
>>>>>>>> now.
>>>>>>>> I've created swimlanes for all top-level components that came from
>>>>>>>> BugZilla.
>>>>>>>>
>>>>>>>> As for epics, I've not seen this listed in the admin portal, seems we
>>>>>>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>>>>>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
>>>>>>>> created. I assume this might require an INFRA ticket as well?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> John
>>>>>>>>
>>>>>>>> On 17 November 2017 at 04:00, Wade Chandler <wa...@apache.org>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> +1 for Kanban
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On Nov 16, 2017, at 17:07, John McDonnell
>>>>>>>>>> <mc...@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> I created a basic Kanban board there to get a starting point, I’ll
>>>>>>>>>> look
>>>>>>>>>> to clean it up next week.
>>>>>>>>>>
>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>>>>>>>
>>>>>>>>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>>>>>>>>>>
>>>>>>>>>> I’ll also need to make it visible to others, since its restricted
>>>>>>>>>> at
>>>>>>>>>> the moment - Think this needs an INFRA ticket…
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>> John
>>>>>>>>>>
>>>>>>>>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in
>>>>>>>>>>> Apache Mesos?
>>>>>>>>>>>
>>>>>>>>>>> Maybe the icon/splash/about dialog set of issues is a small
>>>>>>>>>>> project
>>>>>>>>>>> we
>>>>>>>>>>> could use to give Jira's boards a spin.
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>> Antonio
>>>>>>>>>>>
>>>>>>>>>>> [1]
>>>>>>>>>>>
>>>>>>>>>>> - Apache Mesos Kanban
>>>>>>>>>>>
>>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>>>>>>>>>>
>>>>>>>>>>> - Apache Mesos Sprint 68
>>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>
>>
Re: Kanban / Scrum / Boards
Posted by John McDonnell <mc...@gmail.com>.
Very easy to create, I think the catch here will be making sure
tickets are marked with a label or something and we only include those
labelled items.
Regards
John
On 23 November 2017 at 17:13, Antonio <an...@vieiro.net> wrote:
> What about a "NetBeans 2017 Java 9 IDE" board we can use for releasing the
> Java IDE by Xmas?
>
> Cheers,
> Antonio
>
> El 23/11/17 a las 18:10, John McDonnell escribió:
>
>> It's very slow to load...
>>
>> Probably due to the number of sections. What we might do is setup a
>> Kanban board per cluster maybe and have then smaller groups in each
>> board if that improves the performance of the board...
>>
>> On 23 November 2017 at 17:02, Antonio <an...@vieiro.net> wrote:
>>>
>>> Hi John,
>>>
>>> This is great news! I'll take an in-dept look later on. It seems to me
>>> the
>>> page is very slow, isn't it? Or is it just me?
>>>
>>> Thanks,
>>> Antonio
>>>
>>> El 23/11/17 a las 17:25, John McDonnell escribió:
>>>
>>>> So the Kanban board is now visible here to all:
>>>>
>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>
>>>> I still need to kick off the change in ticket types with the Infra
>>>> team, in order to enable epics.
>>>>
>>>> Regards
>>>>
>>>> John
>>>>
>>>> On 18 November 2017 at 08:24, Antonio <an...@vieiro.net> wrote:
>>>>>
>>>>>
>>>>> So I played the "find the differences" game at [1] and I think that
>>>>> this
>>>>> holds:
>>>>>
>>>>> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
>>>>> (documentation,
>>>>> task, Sub-task).
>>>>>
>>>>> I don't know the differences between "Task" and "Technical task", maybe
>>>>> we
>>>>> can go with the simplest one, the "Agile Scrum Issue Type" and decide
>>>>> whether a task is "Technical" or not by adding a prefix in the task
>>>>> name.
>>>>>
>>>>> So +1 for the "Agile Scrum Issue Type".
>>>>>
>>>>> Cheers,
>>>>> Antonio
>>>>>
>>>>> [1]
>>>>> Find the differences game:
>>>>>
>>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>>>
>>>>>
>>>>>
>>>>> On 17/11/17 17:46, John McDonnell wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Had a quick look before I created the INFRA ticket, and it seems that
>>>>>> there are 4 possible settings for Apache's JIRA:
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>>>>
>>>>>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>>>>>> When we raise a ticket, we should probably know which scheme we want
>>>>>> to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
>>>>>> logical to me, but I'm just one person.
>>>>>>
>>>>>> Anyone see any need for any of the other schemes?
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> John
>>>>>>
>>>>>> On 17 November 2017 at 08:45, John McDonnell
>>>>>> <mc...@gmail.com>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi Wade,
>>>>>>>
>>>>>>> While I wait for the INFRA ticket to be looked at, I've added you to
>>>>>>> the board's admin list, so I believe you should be able to see it
>>>>>>> now.
>>>>>>> I've created swimlanes for all top-level components that came from
>>>>>>> BugZilla.
>>>>>>>
>>>>>>> As for epics, I've not seen this listed in the admin portal, seems we
>>>>>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>>>>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
>>>>>>> created. I assume this might require an INFRA ticket as well?
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> On 17 November 2017 at 04:00, Wade Chandler <wa...@apache.org>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> +1 for Kanban
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Nov 16, 2017, at 17:07, John McDonnell
>>>>>>>>> <mc...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I created a basic Kanban board there to get a starting point, I’ll
>>>>>>>>> look
>>>>>>>>> to clean it up next week.
>>>>>>>>>
>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>>>>>>
>>>>>>>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>>>>>>>>>
>>>>>>>>> I’ll also need to make it visible to others, since its restricted
>>>>>>>>> at
>>>>>>>>> the moment - Think this needs an INFRA ticket…
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>> John
>>>>>>>>>
>>>>>>>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>>>>>>>
>>>>>>>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in
>>>>>>>>>> Apache Mesos?
>>>>>>>>>>
>>>>>>>>>> Maybe the icon/splash/about dialog set of issues is a small
>>>>>>>>>> project
>>>>>>>>>> we
>>>>>>>>>> could use to give Jira's boards a spin.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Antonio
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>>
>>>>>>>>>> - Apache Mesos Kanban
>>>>>>>>>>
>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>>>>>>>>>
>>>>>>>>>> - Apache Mesos Sprint 68
>>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>
>>>
>
Re: Kanban / Scrum / Boards
Posted by Antonio <an...@vieiro.net>.
What about a "NetBeans 2017 Java 9 IDE" board we can use for releasing
the Java IDE by Xmas?
Cheers,
Antonio
El 23/11/17 a las 18:10, John McDonnell escribió:
> It's very slow to load...
>
> Probably due to the number of sections. What we might do is setup a
> Kanban board per cluster maybe and have then smaller groups in each
> board if that improves the performance of the board...
>
> On 23 November 2017 at 17:02, Antonio <an...@vieiro.net> wrote:
>> Hi John,
>>
>> This is great news! I'll take an in-dept look later on. It seems to me the
>> page is very slow, isn't it? Or is it just me?
>>
>> Thanks,
>> Antonio
>>
>> El 23/11/17 a las 17:25, John McDonnell escribió:
>>
>>> So the Kanban board is now visible here to all:
>>>
>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>
>>> I still need to kick off the change in ticket types with the Infra
>>> team, in order to enable epics.
>>>
>>> Regards
>>>
>>> John
>>>
>>> On 18 November 2017 at 08:24, Antonio <an...@vieiro.net> wrote:
>>>>
>>>> So I played the "find the differences" game at [1] and I think that this
>>>> holds:
>>>>
>>>> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
>>>> (documentation,
>>>> task, Sub-task).
>>>>
>>>> I don't know the differences between "Task" and "Technical task", maybe
>>>> we
>>>> can go with the simplest one, the "Agile Scrum Issue Type" and decide
>>>> whether a task is "Technical" or not by adding a prefix in the task name.
>>>>
>>>> So +1 for the "Agile Scrum Issue Type".
>>>>
>>>> Cheers,
>>>> Antonio
>>>>
>>>> [1]
>>>> Find the differences game:
>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>>
>>>>
>>>>
>>>> On 17/11/17 17:46, John McDonnell wrote:
>>>>>
>>>>>
>>>>> Had a quick look before I created the INFRA ticket, and it seems that
>>>>> there are 4 possible settings for Apache's JIRA:
>>>>>
>>>>>
>>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>>>
>>>>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>>>>> When we raise a ticket, we should probably know which scheme we want
>>>>> to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
>>>>> logical to me, but I'm just one person.
>>>>>
>>>>> Anyone see any need for any of the other schemes?
>>>>>
>>>>> Regards
>>>>>
>>>>> John
>>>>>
>>>>> On 17 November 2017 at 08:45, John McDonnell <mc...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Hi Wade,
>>>>>>
>>>>>> While I wait for the INFRA ticket to be looked at, I've added you to
>>>>>> the board's admin list, so I believe you should be able to see it now.
>>>>>> I've created swimlanes for all top-level components that came from
>>>>>> BugZilla.
>>>>>>
>>>>>> As for epics, I've not seen this listed in the admin portal, seems we
>>>>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>>>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
>>>>>> created. I assume this might require an INFRA ticket as well?
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> John
>>>>>>
>>>>>> On 17 November 2017 at 04:00, Wade Chandler <wa...@apache.org>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>> +1 for Kanban
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Nov 16, 2017, at 17:07, John McDonnell <mc...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> I created a basic Kanban board there to get a starting point, I’ll
>>>>>>>> look
>>>>>>>> to clean it up next week.
>>>>>>>>
>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>>>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>>>>>>>>
>>>>>>>> I’ll also need to make it visible to others, since its restricted at
>>>>>>>> the moment - Think this needs an INFRA ticket…
>>>>>>>>
>>>>>>>> Regards
>>>>>>>>
>>>>>>>> John
>>>>>>>>
>>>>>>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>>>>>>
>>>>>>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in
>>>>>>>>> Apache Mesos?
>>>>>>>>>
>>>>>>>>> Maybe the icon/splash/about dialog set of issues is a small project
>>>>>>>>> we
>>>>>>>>> could use to give Jira's boards a spin.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Antonio
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>>
>>>>>>>>> - Apache Mesos Kanban
>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>>>>>>>>
>>>>>>>>> - Apache Mesos Sprint 68
>>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>
>>
Re: Kanban / Scrum / Boards
Posted by John McDonnell <mc...@gmail.com>.
It's very slow to load...
Probably due to the number of sections. What we might do is setup a
Kanban board per cluster maybe and have then smaller groups in each
board if that improves the performance of the board...
On 23 November 2017 at 17:02, Antonio <an...@vieiro.net> wrote:
> Hi John,
>
> This is great news! I'll take an in-dept look later on. It seems to me the
> page is very slow, isn't it? Or is it just me?
>
> Thanks,
> Antonio
>
> El 23/11/17 a las 17:25, John McDonnell escribió:
>
>> So the Kanban board is now visible here to all:
>>
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>
>> I still need to kick off the change in ticket types with the Infra
>> team, in order to enable epics.
>>
>> Regards
>>
>> John
>>
>> On 18 November 2017 at 08:24, Antonio <an...@vieiro.net> wrote:
>>>
>>> So I played the "find the differences" game at [1] and I think that this
>>> holds:
>>>
>>> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
>>> (documentation,
>>> task, Sub-task).
>>>
>>> I don't know the differences between "Task" and "Technical task", maybe
>>> we
>>> can go with the simplest one, the "Agile Scrum Issue Type" and decide
>>> whether a task is "Technical" or not by adding a prefix in the task name.
>>>
>>> So +1 for the "Agile Scrum Issue Type".
>>>
>>> Cheers,
>>> Antonio
>>>
>>> [1]
>>> Find the differences game:
>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>
>>>
>>>
>>> On 17/11/17 17:46, John McDonnell wrote:
>>>>
>>>>
>>>> Had a quick look before I created the INFRA ticket, and it seems that
>>>> there are 4 possible settings for Apache's JIRA:
>>>>
>>>>
>>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>>
>>>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>>>> When we raise a ticket, we should probably know which scheme we want
>>>> to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
>>>> logical to me, but I'm just one person.
>>>>
>>>> Anyone see any need for any of the other schemes?
>>>>
>>>> Regards
>>>>
>>>> John
>>>>
>>>> On 17 November 2017 at 08:45, John McDonnell <mc...@gmail.com>
>>>> wrote:
>>>>>
>>>>>
>>>>> Hi Wade,
>>>>>
>>>>> While I wait for the INFRA ticket to be looked at, I've added you to
>>>>> the board's admin list, so I believe you should be able to see it now.
>>>>> I've created swimlanes for all top-level components that came from
>>>>> BugZilla.
>>>>>
>>>>> As for epics, I've not seen this listed in the admin portal, seems we
>>>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
>>>>> created. I assume this might require an INFRA ticket as well?
>>>>>
>>>>> Regards
>>>>>
>>>>> John
>>>>>
>>>>> On 17 November 2017 at 04:00, Wade Chandler <wa...@apache.org>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> +1 for Kanban
>>>>>>
>>>>>>
>>>>>>
>>>>>>> On Nov 16, 2017, at 17:07, John McDonnell <mc...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> I created a basic Kanban board there to get a starting point, I’ll
>>>>>>> look
>>>>>>> to clean it up next week.
>>>>>>>
>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>>>>>>>
>>>>>>> I’ll also need to make it visible to others, since its restricted at
>>>>>>> the moment - Think this needs an INFRA ticket…
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>>>>>
>>>>>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in
>>>>>>>> Apache Mesos?
>>>>>>>>
>>>>>>>> Maybe the icon/splash/about dialog set of issues is a small project
>>>>>>>> we
>>>>>>>> could use to give Jira's boards a spin.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Antonio
>>>>>>>>
>>>>>>>> [1]
>>>>>>>>
>>>>>>>> - Apache Mesos Kanban
>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>>>>>>>
>>>>>>>> - Apache Mesos Sprint 68
>>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>
>
Re: Kanban / Scrum / Boards
Posted by Antonio <an...@vieiro.net>.
Hi John,
This is great news! I'll take an in-dept look later on. It seems to me
the page is very slow, isn't it? Or is it just me?
Thanks,
Antonio
El 23/11/17 a las 17:25, John McDonnell escribió:
> So the Kanban board is now visible here to all:
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>
> I still need to kick off the change in ticket types with the Infra
> team, in order to enable epics.
>
> Regards
>
> John
>
> On 18 November 2017 at 08:24, Antonio <an...@vieiro.net> wrote:
>> So I played the "find the differences" game at [1] and I think that this
>> holds:
>>
>> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" + (documentation,
>> task, Sub-task).
>>
>> I don't know the differences between "Task" and "Technical task", maybe we
>> can go with the simplest one, the "Agile Scrum Issue Type" and decide
>> whether a task is "Technical" or not by adding a prefix in the task name.
>>
>> So +1 for the "Agile Scrum Issue Type".
>>
>> Cheers,
>> Antonio
>>
>> [1]
>> Find the differences game:
>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>
>>
>>
>> On 17/11/17 17:46, John McDonnell wrote:
>>>
>>> Had a quick look before I created the INFRA ticket, and it seems that
>>> there are 4 possible settings for Apache's JIRA:
>>>
>>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>>
>>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>>> When we raise a ticket, we should probably know which scheme we want
>>> to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
>>> logical to me, but I'm just one person.
>>>
>>> Anyone see any need for any of the other schemes?
>>>
>>> Regards
>>>
>>> John
>>>
>>> On 17 November 2017 at 08:45, John McDonnell <mc...@gmail.com>
>>> wrote:
>>>>
>>>> Hi Wade,
>>>>
>>>> While I wait for the INFRA ticket to be looked at, I've added you to
>>>> the board's admin list, so I believe you should be able to see it now.
>>>> I've created swimlanes for all top-level components that came from
>>>> BugZilla.
>>>>
>>>> As for epics, I've not seen this listed in the admin portal, seems we
>>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
>>>> created. I assume this might require an INFRA ticket as well?
>>>>
>>>> Regards
>>>>
>>>> John
>>>>
>>>> On 17 November 2017 at 04:00, Wade Chandler <wa...@apache.org>
>>>> wrote:
>>>>>
>>>>> +1 for Kanban
>>>>>
>>>>>
>>>>>
>>>>>> On Nov 16, 2017, at 17:07, John McDonnell <mc...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> I created a basic Kanban board there to get a starting point, I’ll look
>>>>>> to clean it up next week.
>>>>>>
>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>>>>>>
>>>>>> I’ll also need to make it visible to others, since its restricted at
>>>>>> the moment - Think this needs an INFRA ticket…
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> John
>>>>>>
>>>>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>>>>
>>>>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in
>>>>>>> Apache Mesos?
>>>>>>>
>>>>>>> Maybe the icon/splash/about dialog set of issues is a small project we
>>>>>>> could use to give Jira's boards a spin.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Antonio
>>>>>>>
>>>>>>> [1]
>>>>>>>
>>>>>>> - Apache Mesos Kanban
>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>>>>>>
>>>>>>> - Apache Mesos Sprint 68
>>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>>>>>
>>>>>>
>>>>>
>>
Re: Kanban / Scrum / Boards
Posted by John McDonnell <mc...@gmail.com>.
So the Kanban board is now visible here to all:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
I still need to kick off the change in ticket types with the Infra
team, in order to enable epics.
Regards
John
On 18 November 2017 at 08:24, Antonio <an...@vieiro.net> wrote:
> So I played the "find the differences" game at [1] and I think that this
> holds:
>
> "Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" + (documentation,
> task, Sub-task).
>
> I don't know the differences between "Task" and "Technical task", maybe we
> can go with the simplest one, the "Agile Scrum Issue Type" and decide
> whether a task is "Technical" or not by adding a prefix in the task name.
>
> So +1 for the "Agile Scrum Issue Type".
>
> Cheers,
> Antonio
>
> [1]
> Find the differences game:
> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>
>
>
> On 17/11/17 17:46, John McDonnell wrote:
>>
>> Had a quick look before I created the INFRA ticket, and it seems that
>> there are 4 possible settings for Apache's JIRA:
>>
>> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>>
>> We're currently on the top left, 'Apache Default Issue Type Scheme'
>> When we raise a ticket, we should probably know which scheme we want
>> to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
>> logical to me, but I'm just one person.
>>
>> Anyone see any need for any of the other schemes?
>>
>> Regards
>>
>> John
>>
>> On 17 November 2017 at 08:45, John McDonnell <mc...@gmail.com>
>> wrote:
>>>
>>> Hi Wade,
>>>
>>> While I wait for the INFRA ticket to be looked at, I've added you to
>>> the board's admin list, so I believe you should be able to see it now.
>>> I've created swimlanes for all top-level components that came from
>>> BugZilla.
>>>
>>> As for epics, I've not seen this listed in the admin portal, seems we
>>> are using an 'Apache Default Issue Type Scheme', which allows for
>>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
>>> created. I assume this might require an INFRA ticket as well?
>>>
>>> Regards
>>>
>>> John
>>>
>>> On 17 November 2017 at 04:00, Wade Chandler <wa...@apache.org>
>>> wrote:
>>>>
>>>> +1 for Kanban
>>>>
>>>>
>>>>
>>>>> On Nov 16, 2017, at 17:07, John McDonnell <mc...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> I created a basic Kanban board there to get a starting point, I’ll look
>>>>> to clean it up next week.
>>>>>
>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216
>>>>> <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>>>>>
>>>>> I’ll also need to make it visible to others, since its restricted at
>>>>> the moment - Think this needs an INFRA ticket…
>>>>>
>>>>> Regards
>>>>>
>>>>> John
>>>>>
>>>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>>>
>>>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in
>>>>>> Apache Mesos?
>>>>>>
>>>>>> Maybe the icon/splash/about dialog set of issues is a small project we
>>>>>> could use to give Jira's boards a spin.
>>>>>>
>>>>>> Cheers,
>>>>>> Antonio
>>>>>>
>>>>>> [1]
>>>>>>
>>>>>> - Apache Mesos Kanban
>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>>>>>
>>>>>> - Apache Mesos Sprint 68
>>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>>>>
>>>>>
>>>>
>
Re: Kanban / Scrum / Boards
Posted by Antonio <an...@vieiro.net>.
So I played the "find the differences" game at [1] and I think that this
holds:
"Mesos Agile Scrum Issue Type" = "Agile Scrum Issue Type" +
(documentation, task, Sub-task).
I don't know the differences between "Task" and "Technical task", maybe
we can go with the simplest one, the "Agile Scrum Issue Type" and decide
whether a task is "Technical" or not by adding a prefix in the task name.
So +1 for the "Agile Scrum Issue Type".
Cheers,
Antonio
[1]
Find the differences game:
https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
On 17/11/17 17:46, John McDonnell wrote:
> Had a quick look before I created the INFRA ticket, and it seems that
> there are 4 possible settings for Apache's JIRA:
>
> https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
>
> We're currently on the top left, 'Apache Default Issue Type Scheme'
> When we raise a ticket, we should probably know which scheme we want
> to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
> logical to me, but I'm just one person.
>
> Anyone see any need for any of the other schemes?
>
> Regards
>
> John
>
> On 17 November 2017 at 08:45, John McDonnell <mc...@gmail.com> wrote:
>> Hi Wade,
>>
>> While I wait for the INFRA ticket to be looked at, I've added you to
>> the board's admin list, so I believe you should be able to see it now.
>> I've created swimlanes for all top-level components that came from
>> BugZilla.
>>
>> As for epics, I've not seen this listed in the admin portal, seems we
>> are using an 'Apache Default Issue Type Scheme', which allows for
>> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
>> created. I assume this might require an INFRA ticket as well?
>>
>> Regards
>>
>> John
>>
>> On 17 November 2017 at 04:00, Wade Chandler <wa...@apache.org> wrote:
>>> +1 for Kanban
>>>
>>>
>>>
>>>> On Nov 16, 2017, at 17:07, John McDonnell <mc...@gmail.com> wrote:
>>>>
>>>> I created a basic Kanban board there to get a starting point, I’ll look to clean it up next week.
>>>>
>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216 <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>>>>
>>>> I’ll also need to make it visible to others, since its restricted at the moment - Think this needs an INFRA ticket…
>>>>
>>>> Regards
>>>>
>>>> John
>>>>
>>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>>
>>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in Apache Mesos?
>>>>>
>>>>> Maybe the icon/splash/about dialog set of issues is a small project we could use to give Jira's boards a spin.
>>>>>
>>>>> Cheers,
>>>>> Antonio
>>>>>
>>>>> [1]
>>>>>
>>>>> - Apache Mesos Kanban
>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>>>>
>>>>> - Apache Mesos Sprint 68
>>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>>>
>>>
Re: Kanban / Scrum / Boards
Posted by John McDonnell <mc...@gmail.com>.
Had a quick look before I created the INFRA ticket, and it seems that
there are 4 possible settings for Apache's JIRA:
https://cwiki.apache.org/confluence/display/INFRA/Jira+Issue+Type+Schemes
We're currently on the top left, 'Apache Default Issue Type Scheme'
When we raise a ticket, we should probably know which scheme we want
to go with going forward. The 'Agile Scrum Issue Type Scheme' seems
logical to me, but I'm just one person.
Anyone see any need for any of the other schemes?
Regards
John
On 17 November 2017 at 08:45, John McDonnell <mc...@gmail.com> wrote:
> Hi Wade,
>
> While I wait for the INFRA ticket to be looked at, I've added you to
> the board's admin list, so I believe you should be able to see it now.
> I've created swimlanes for all top-level components that came from
> BugZilla.
>
> As for epics, I've not seen this listed in the admin portal, seems we
> are using an 'Apache Default Issue Type Scheme', which allows for
> Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
> created. I assume this might require an INFRA ticket as well?
>
> Regards
>
> John
>
> On 17 November 2017 at 04:00, Wade Chandler <wa...@apache.org> wrote:
>> +1 for Kanban
>>
>>
>>
>>> On Nov 16, 2017, at 17:07, John McDonnell <mc...@gmail.com> wrote:
>>>
>>> I created a basic Kanban board there to get a starting point, I’ll look to clean it up next week.
>>>
>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216 <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>>>
>>> I’ll also need to make it visible to others, since its restricted at the moment - Think this needs an INFRA ticket…
>>>
>>> Regards
>>>
>>> John
>>>
>>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>>
>>>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in Apache Mesos?
>>>>
>>>> Maybe the icon/splash/about dialog set of issues is a small project we could use to give Jira's boards a spin.
>>>>
>>>> Cheers,
>>>> Antonio
>>>>
>>>> [1]
>>>>
>>>> - Apache Mesos Kanban
>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>>>
>>>> - Apache Mesos Sprint 68
>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>>
>>
Re: Kanban / Scrum / Boards
Posted by John McDonnell <mc...@gmail.com>.
Hi Wade,
While I wait for the INFRA ticket to be looked at, I've added you to
the board's admin list, so I believe you should be able to see it now.
I've created swimlanes for all top-level components that came from
BugZilla.
As for epics, I've not seen this listed in the admin portal, seems we
are using an 'Apache Default Issue Type Scheme', which allows for
Bugs, Improvements, New Features, Task, Test Wish and Sub Tasks to be
created. I assume this might require an INFRA ticket as well?
Regards
John
On 17 November 2017 at 04:00, Wade Chandler <wa...@apache.org> wrote:
> +1 for Kanban
>
>
>
>> On Nov 16, 2017, at 17:07, John McDonnell <mc...@gmail.com> wrote:
>>
>> I created a basic Kanban board there to get a starting point, I’ll look to clean it up next week.
>>
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216 <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>>
>> I’ll also need to make it visible to others, since its restricted at the moment - Think this needs an INFRA ticket…
>>
>> Regards
>>
>> John
>>
>>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>>
>>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in Apache Mesos?
>>>
>>> Maybe the icon/splash/about dialog set of issues is a small project we could use to give Jira's boards a spin.
>>>
>>> Cheers,
>>> Antonio
>>>
>>> [1]
>>>
>>> - Apache Mesos Kanban
>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>>
>>> - Apache Mesos Sprint 68
>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>>
>
Re: Kanban / Scrum / Boards
Posted by Wade Chandler <wa...@apache.org>.
+1 for Kanban
> On Nov 16, 2017, at 17:07, John McDonnell <mc...@gmail.com> wrote:
>
> I created a basic Kanban board there to get a starting point, I’ll look to clean it up next week.
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216 <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>
> I’ll also need to make it visible to others, since its restricted at the moment - Think this needs an INFRA ticket…
>
> Regards
>
> John
>
>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>
>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in Apache Mesos?
>>
>> Maybe the icon/splash/about dialog set of issues is a small project we could use to give Jira's boards a spin.
>>
>> Cheers,
>> Antonio
>>
>> [1]
>>
>> - Apache Mesos Kanban
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>
>> - Apache Mesos Sprint 68
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>
Re: Kanban / Scrum / Boards
Posted by Wade Chandler <wa...@apache.org>.
John,
Do you know if we can also create Epics?
Thanks,
Wade
> On Nov 16, 2017, at 17:07, John McDonnell <mc...@gmail.com> wrote:
>
> I created a basic Kanban board there to get a starting point, I’ll look to clean it up next week.
>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216 <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
>
> I’ll also need to make it visible to others, since its restricted at the moment - Think this needs an INFRA ticket…
>
> Regards
>
> John
>
>> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>>
>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in Apache Mesos?
>>
>> Maybe the icon/splash/about dialog set of issues is a small project we could use to give Jira's boards a spin.
>>
>> Cheers,
>> Antonio
>>
>> [1]
>>
>> - Apache Mesos Kanban
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>
>> - Apache Mesos Sprint 68
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
>
Re: Kanban / Scrum / Boards
Posted by John McDonnell <mc...@gmail.com>.
I created a basic Kanban board there to get a starting point, I’ll look to clean it up next week.
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216 <https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216>
I’ll also need to make it visible to others, since its restricted at the moment - Think this needs an INFRA ticket…
Regards
John
> On 16 Nov 2017, at 20:05, Antonio <an...@vieiro.net> wrote:
>
> Do we want to try out Jira's Kanban/Scrum boards like these [1] in Apache Mesos?
>
> Maybe the icon/splash/about dialog set of issues is a small project we could use to give Jira's boards a spin.
>
> Cheers,
> Antonio
>
> [1]
>
> - Apache Mesos Kanban
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>
> - Apache Mesos Sprint 68
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
Re: Kanban / Scrum / Boards
Posted by Antonio <an...@vieiro.net>.
Cool. I'll keep on working on that small NetBeans Platform demo app.
El 16/11/17 a las 21:53, John McDonnell escribió:
> I think that's a good idea.
>
> Initially, we could have a grouping for tickets that are required for
> an Apache NetBeans release, maybe even create Jira tickets for any
> outstanding issues from the lists here:
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
>
> We could also look at creating groups per components as well, it might
> give people looking at planning a release an idea what tickets per
> component exist, and an easy way to see what can/cant/should go into a
> next release.
>
> If this was wanted I could look to set something like this up next
> week (off on a long weekend now for a wedding so won't be in any state
> for this until next week).
>
>
> Regards
>
> John
>
> On 16 November 2017 at 20:05, Antonio <an...@vieiro.net> wrote:
>> Do we want to try out Jira's Kanban/Scrum boards like these [1] in Apache
>> Mesos?
>>
>> Maybe the icon/splash/about dialog set of issues is a small project we could
>> use to give Jira's boards a spin.
>>
>> Cheers,
>> Antonio
>>
>> [1]
>>
>> - Apache Mesos Kanban
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>>
>> - Apache Mesos Sprint 68
>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
Re: Kanban / Scrum / Boards
Posted by John McDonnell <mc...@gmail.com>.
I think that's a good idea.
Initially, we could have a grouping for tickets that are required for
an Apache NetBeans release, maybe even create Jira tickets for any
outstanding issues from the lists here:
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
We could also look at creating groups per components as well, it might
give people looking at planning a release an idea what tickets per
component exist, and an easy way to see what can/cant/should go into a
next release.
If this was wanted I could look to set something like this up next
week (off on a long weekend now for a wedding so won't be in any state
for this until next week).
Regards
John
On 16 November 2017 at 20:05, Antonio <an...@vieiro.net> wrote:
> Do we want to try out Jira's Kanban/Scrum boards like these [1] in Apache
> Mesos?
>
> Maybe the icon/splash/about dialog set of issues is a small project we could
> use to give Jira's boards a spin.
>
> Cheers,
> Antonio
>
> [1]
>
> - Apache Mesos Kanban
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>
> - Apache Mesos Sprint 68
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62
Re: Kanban / Scrum / Boards
Posted by Wade Chandler <wa...@apache.org>.
I would very much be in favor of this. See the email I sent in November with the Subject “Jira Epics, Boards, and Agile Management, and What Other Projects Are Doing”. At the moment, we also can not create Epics, and I think some of these big picture things would benefit from them. When we create issues we have an option to choose an Epic, but I could not create one. I can help with the boards if I have access to manage them too. I prefer Kanban, and I think Kanban will suite not only the notion of “flow”, but also the way we work distributed and our timelines. Scrum will require sprints, if we are practicing it, and I’m not sure that cadence will match our community.
Thanks,
Wade
> On Nov 16, 2017, at 15:05, Antonio <an...@vieiro.net> wrote:
>
> Do we want to try out Jira's Kanban/Scrum boards like these [1] in Apache Mesos?
>
> Maybe the icon/splash/about dialog set of issues is a small project we could use to give Jira's boards a spin.
>
> Cheers,
> Antonio
>
> [1]
>
> - Apache Mesos Kanban
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=111
>
> - Apache Mesos Sprint 68
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=62