You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Christian Lenz <ch...@gmx.net> on 2018/09/18 12:25:11 UTC
Ticket, Sub-Tasks and PRs
Dear Devs,
I created a new ticket, for a new feature, which I want to implement: https://issues.apache.org/jira/browse/NETBEANS-1262
This ticket Needs 2 implementations. One Action to create a shortcut (One Sub-Task) and create a new searchfield to filter the list inside the Show opened documents list popup (Second Sub-Task).
First I want to know, whether it is correct to create for each Little feature, which depends on the Overall feature, a sub ticket or not and second how should I handle the PR? Should I create a new branch (In my fork or directly in the incubator repo?) for each Sub ticket or a PR for the Ticket itself and not for the Sub Tasks?
Cheers
Chris
Re: Ticket, Sub-Tasks and PRs
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Do whatever is simplest, I think.
Gj
On Thu, Sep 20, 2018 at 4:59 PM, Christian Lenz <ch...@gmx.net>
wrote:
> Any suggestions to this Topic? I read the Guidelines for that:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681408
> but no proposals for Sub-tasks.
>
> Ok here is my proposal, I think it depends on the feature but if you have
> an amount of small Sub Tasks it could be separate commits for each Sub Task
> in one PR. If you have a lot of work, it would make much more sense to have
> one PR for each Sub Task.
>
> In my Situation, of Course both are 2 new Features/improvements, which
> could be 2 separate stories but both are a bit connected to each other,
> because I want to use a shortcut to open the Thing and type into a search
> field.
>
> Do you have any other suggestions for that? I’m also fine to split my
> ticket into 2 tickets instead of having 2 sub Tasks of 1 ticket.
>
>
> Cheers
>
> Chris
>
>
>
> Von: Christian Lenz
> Gesendet: Dienstag, 18. September 2018 14:25
> An: dev@netbeans.incubator.apache.org
> Betreff: Ticket, Sub-Tasks and PRs
>
> Dear Devs,
>
> I created a new ticket, for a new feature, which I want to implement:
> https://issues.apache.org/jira/browse/NETBEANS-1262
>
> This ticket Needs 2 implementations. One Action to create a shortcut (One
> Sub-Task) and create a new searchfield to filter the list inside the Show
> opened documents list popup (Second Sub-Task).
>
> First I want to know, whether it is correct to create for each Little
> feature, which depends on the Overall feature, a sub ticket or not and
> second how should I handle the PR? Should I create a new branch (In my fork
> or directly in the incubator repo?) for each Sub ticket or a PR for the
> Ticket itself and not for the Sub Tasks?
>
>
> Cheers
>
> Chris
>
>
AW: AW: Ticket, Sub-Tasks and PRs
Posted by Christian Lenz <ch...@gmx.net>.
Hey Lazlo,
thx for your Suggestion. Yeah it makes sense to me too. 😊
Cheers
Chris
Von: Laszlo Kishalmi
Gesendet: Samstag, 22. September 2018 01:24
An: dev@netbeans.incubator.apache.org
Betreff: Re: AW: Ticket, Sub-Tasks and PRs
I'd create two separate stories linked together.
These two improvements stands on their own and probably small enough to
implement. Of course they are more powerful if delivered together, but
we could deliver them independently bringing some value to the platform,
and often bite sized stories are the best.
On 09/20/2018 07:59 AM, Christian Lenz wrote:
> Any suggestions to this Topic? I read the Guidelines for that: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681408 but no proposals for Sub-tasks.
>
> Ok here is my proposal, I think it depends on the feature but if you have an amount of small Sub Tasks it could be separate commits for each Sub Task in one PR. If you have a lot of work, it would make much more sense to have one PR for each Sub Task.
>
> In my Situation, of Course both are 2 new Features/improvements, which could be 2 separate stories but both are a bit connected to each other, because I want to use a shortcut to open the Thing and type into a search field.
>
> Do you have any other suggestions for that? I’m also fine to split my ticket into 2 tickets instead of having 2 sub Tasks of 1 ticket.
>
>
> Cheers
>
> Chris
>
>
>
> Von: Christian Lenz
> Gesendet: Dienstag, 18. September 2018 14:25
> An: dev@netbeans.incubator.apache.org
> Betreff: Ticket, Sub-Tasks and PRs
>
> Dear Devs,
>
> I created a new ticket, for a new feature, which I want to implement: https://issues.apache.org/jira/browse/NETBEANS-1262
>
> This ticket Needs 2 implementations. One Action to create a shortcut (One Sub-Task) and create a new searchfield to filter the list inside the Show opened documents list popup (Second Sub-Task).
>
> First I want to know, whether it is correct to create for each Little feature, which depends on the Overall feature, a sub ticket or not and second how should I handle the PR? Should I create a new branch (In my fork or directly in the incubator repo?) for each Sub ticket or a PR for the Ticket itself and not for the Sub Tasks?
>
>
> Cheers
>
> Chris
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: AW: Ticket, Sub-Tasks and PRs
Posted by Laszlo Kishalmi <la...@gmail.com>.
I'd create two separate stories linked together.
These two improvements stands on their own and probably small enough to
implement. Of course they are more powerful if delivered together, but
we could deliver them independently bringing some value to the platform,
and often bite sized stories are the best.
On 09/20/2018 07:59 AM, Christian Lenz wrote:
> Any suggestions to this Topic? I read the Guidelines for that: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681408 but no proposals for Sub-tasks.
>
> Ok here is my proposal, I think it depends on the feature but if you have an amount of small Sub Tasks it could be separate commits for each Sub Task in one PR. If you have a lot of work, it would make much more sense to have one PR for each Sub Task.
>
> In my Situation, of Course both are 2 new Features/improvements, which could be 2 separate stories but both are a bit connected to each other, because I want to use a shortcut to open the Thing and type into a search field.
>
> Do you have any other suggestions for that? I’m also fine to split my ticket into 2 tickets instead of having 2 sub Tasks of 1 ticket.
>
>
> Cheers
>
> Chris
>
>
>
> Von: Christian Lenz
> Gesendet: Dienstag, 18. September 2018 14:25
> An: dev@netbeans.incubator.apache.org
> Betreff: Ticket, Sub-Tasks and PRs
>
> Dear Devs,
>
> I created a new ticket, for a new feature, which I want to implement: https://issues.apache.org/jira/browse/NETBEANS-1262
>
> This ticket Needs 2 implementations. One Action to create a shortcut (One Sub-Task) and create a new searchfield to filter the list inside the Show opened documents list popup (Second Sub-Task).
>
> First I want to know, whether it is correct to create for each Little feature, which depends on the Overall feature, a sub ticket or not and second how should I handle the PR? Should I create a new branch (In my fork or directly in the incubator repo?) for each Sub ticket or a PR for the Ticket itself and not for the Sub Tasks?
>
>
> Cheers
>
> Chris
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
AW: Ticket, Sub-Tasks and PRs
Posted by Christian Lenz <ch...@gmx.net>.
Any suggestions to this Topic? I read the Guidelines for that: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681408 but no proposals for Sub-tasks.
Ok here is my proposal, I think it depends on the feature but if you have an amount of small Sub Tasks it could be separate commits for each Sub Task in one PR. If you have a lot of work, it would make much more sense to have one PR for each Sub Task.
In my Situation, of Course both are 2 new Features/improvements, which could be 2 separate stories but both are a bit connected to each other, because I want to use a shortcut to open the Thing and type into a search field.
Do you have any other suggestions for that? I’m also fine to split my ticket into 2 tickets instead of having 2 sub Tasks of 1 ticket.
Cheers
Chris
Von: Christian Lenz
Gesendet: Dienstag, 18. September 2018 14:25
An: dev@netbeans.incubator.apache.org
Betreff: Ticket, Sub-Tasks and PRs
Dear Devs,
I created a new ticket, for a new feature, which I want to implement: https://issues.apache.org/jira/browse/NETBEANS-1262
This ticket Needs 2 implementations. One Action to create a shortcut (One Sub-Task) and create a new searchfield to filter the list inside the Show opened documents list popup (Second Sub-Task).
First I want to know, whether it is correct to create for each Little feature, which depends on the Overall feature, a sub ticket or not and second how should I handle the PR? Should I create a new branch (In my fork or directly in the incubator repo?) for each Sub ticket or a PR for the Ticket itself and not for the Sub Tasks?
Cheers
Chris