-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agent spec process #304
Agent spec process #304
Conversation
Sure, let's do this! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The draft looks good to me 👍
I've created a bash script to batch-create agent issues using https://github.com/cli/cli #!/bin/bash
set -ex
AGENTS=()
while [[ "$#" -gt 0 ]]; do
case $1 in
--all-agents) AGENTS=(dotnet go java nodejs php python ruby rum-js); ;;
-a|--agent) AGENTS+=("$2"); shift ;;
-t|--title) title="$2"; shift ;;
-b|--body) body="$2"; shift ;;
-m|--milestone) milestone="$2"; shift ;;
*) echo "Unknown parameter passed: $1"; exit 1 ;;
esac
shift || true
done
: "${AGENTS:?Variable not set or empty}"
: "${title:?Variable not set or empty}"
: "${body:?Variable not set or empty}"
: "${milestone:?Variable not set or empty}"
echo $AGENTS
for agent in "${AGENTS[@]}" ; do
echo $agent
gh repo clone elastic/apm-agent-$agent || true
pushd apm-agent-$agent
gh issue create --title "$title" --body "$body" --milestone $milestone
popd
done One caveat is that the milestone has to exist in the agent repo. It also clones all repos the first time it's executed. |
Moved to separate PR elastic#306
I've marked this PR as ready for review now. This means one more agent approval and one PM approval is required. After that, everyone's got 1 week to object by requesting changes. After that the PR will be merged and the changes are effective. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks excellent. One request below. But overall I'm very excited about this process change, it will make it much clearer when a spec is final.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love it 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++ for this proposal. I'd suggest adding another table that identifies if we plan to implement a change/addition to all other agents as a part of the spec PR. It'll make it easy to track if all/some agents plan to implement that feature(with a rough milestone) or if its not applicable at all.
As the total deadline is 1 week, a reminder after 2 days doesn't seem sensible
We have approval from at least two agents and from PM now. So normally, there would be one more week for agent teams to object. However, since all agent teams have already approved the PR, I think we can proceed. I'll merge the PR tomorrow so this is the last call for objections. |
Let's make this PR an example of the process it describes.
@gregkalapos would you volunteer to be the reviewer of the draft?
supersedes #192
The agent table, not very useful in this case as there's nothing to implement but still useful for showcasing the process this PR proposes.