[
https://issues.apache.org/jira/browse/KNOX-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-3373:
--------------------------------
Description:
In order to enable faster iteration on the knox_idf feature branch, we
discussed making early commits closer to a CTR approach. Each PR needs to have
some sort of review but if a certain area requires another look or someone else
to look prior to merge to master, we can file a follow up Jira and approve the
short term commit.
We can also use this for follow up tasks that are noted as good to change about
a PR but we can address later.
When it comes to merge knox_idf to master, we will need to burn down or move to
a new Post-merge Jira prior to the actual merge.
This will allow us to move faster and not lose track of required changes and
reviews.
+*Update (14 Aug 2026):*+ this work item serves as the parent for sub-tasks
revealed after PR #1351 merged to {{master}} (so we are not targeting
{{knox_idf}} after that merge happened).
was:
In order to enable faster iteration on the knox_idf feature branch, we
discussed making early commits closer to a CTR approach. Each PR needs to have
some sort of review but if a certain area requires another look or someone else
to look prior to merge to master, we can file a follow up Jira and approve the
short term commit.
We can also use this for follow up tasks that are noted as good to change about
a PR but we can address later.
When it comes to merge knox_idf to master, we will need to burn down or move to
a new Post-merge Jira prior to the actual merge.
This will allow us to move faster and not lose track of required changes and
reviews.
> KnoxIDF Feature Branch Merge to Main Burndown
> ---------------------------------------------
>
> Key: KNOX-3373
> URL: https://issues.apache.org/jira/browse/KNOX-3373
> Project: Apache Knox
> Issue Type: Improvement
> Components: JWT
> Reporter: Larry McCay
> Priority: Major
> Fix For: 3.1.0
>
>
> In order to enable faster iteration on the knox_idf feature branch, we
> discussed making early commits closer to a CTR approach. Each PR needs to
> have some sort of review but if a certain area requires another look or
> someone else to look prior to merge to master, we can file a follow up Jira
> and approve the short term commit.
> We can also use this for follow up tasks that are noted as good to change
> about a PR but we can address later.
> When it comes to merge knox_idf to master, we will need to burn down or move
> to a new Post-merge Jira prior to the actual merge.
> This will allow us to move faster and not lose track of required changes and
> reviews.
>
> +*Update (14 Aug 2026):*+ this work item serves as the parent for sub-tasks
> revealed after PR #1351 merged to {{master}} (so we are not targeting
> {{knox_idf}} after that merge happened).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
