[
https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817371#comment-17817371
]
Rich Bowen commented on COMDEV-543:
---
These are all good, but I am *very* concerned that
[
https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817389#comment-17817389
]
Justin Mclean commented on COMDEV-543:
--
I agree guiding projects on what to do in th
rbowen opened a new pull request, #2:
URL: https://github.com/apache/comdev-working-groups/pull/2
Adds list of red flags contributed by Justin in
https://issues.apache.org/jira/browse/COMDEV-543
We should work towards 1) categorizing these and 2) linking from each to
constructive way
rbowen merged PR #2:
URL: https://github.com/apache/comdev-working-groups/pull/2
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@communi
[
https://issues.apache.org/jira/browse/COMDEV-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817400#comment-17817400
]
Rich Bowen commented on COMDEV-543:
---
Added to doc in https://github.com/apache/comdev-w
tisonkun opened a new pull request, #3:
URL: https://github.com/apache/comdev-working-groups/pull/3
Mainly for the `jira_options` that I hope it works well to link with JIRA
tickets.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
tisonkun opened a new pull request, #158:
URL: https://github.com/apache/comdev-site/pull/158
I remember the default email title has been changed months ago.
Also for `jira_options` config.
--
This is an automated message from the Apache Git Service.
To respond to the message, pleas
rbowen merged PR #3:
URL: https://github.com/apache/comdev-working-groups/pull/3
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@communi
I guess I am too late here, but fwiw, I agree strongly with Rich's
comment. I would much rather see the checklisty stuff incorporated into
either the use cases or the main doc somewhere and not presented as "things
'we' are looking for". I do not like at all the statement in the intro to
the new
To be clear Justin’s red flags are here:
https://github.com/apache/comdev-working-groups/blob/main/wg-sharpeners/red-flags.md
> On Feb 14, 2024, at 11:46 AM, Phil Steitz wrote:
>
> I guess I am too late here, but fwiw, I agree strongly with Rich's
> comment. I would much rather see the checkli
On Feb 14, 2024, at 2:46 PM, Phil Steitz wrote:
>
> I guess I am too late here, but fwiw, I agree strongly with Rich's
> comment. I would much rather see the checklisty stuff incorporated into
> either the use cases or the main doc somewhere and not presented as "things
> 'we' are looking for".
On 2/14/24 21:33, Rich Bowen wrote:
On Feb 14, 2024, at 2:46 PM, Phil Steitz wrote:
I guess I am too late here, but fwiw, I agree strongly with Rich's
comment. I would much rather see the checklisty stuff incorporated into
either the use cases or the main doc somewhere and not presented as "t
Hi,
I added the list because I had it at hand so it could be used to improve the
existing document; if I had time at the moment, I would have written it in the
style of the existing document, but sadly, I do not at the moment.
Re “too many release candidates”, one thing I have observed is that
Hi,
Repost this thread and cc Swapnil for more visibility.
I'm reviewing and patching related repos now and noticed that this
request is pending. Since active committers are reviewing patches,
this is not in a rush. But I'm afraid that this email gets
overwhelmed.
Rich Bowen wrote:
> Meanwhile,
14 matches
Mail list logo
