Skip to content
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

Merge ActionSource2 back into ActionSource and deprecate ActionSource2 related classes #5326

Merged

Conversation

BalusC
Copy link
Contributor

@BalusC BalusC commented Oct 1, 2023

@BalusC BalusC marked this pull request as ready for review October 1, 2023 15:00
*/
@Deprecated(since = "4.1", forRemoval = true)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I doubt a 4.1 release will be done. Can you retarget it for 5.0?

Copy link
Contributor Author

@BalusC BalusC Oct 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure but 4.1 branch still exist. Will do when 4.1 will be officially skipped and merged into 5.0 because it's easier to find&replace 4.1 / 4_1 by 5.0 / 5_0 in one go. The 4.1 branch has in its current form already a good couple of these.

Copy link
Contributor

@mnriem mnriem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BalusC Can you make sure you also file an implementation issue for this as well so we can tie the 2 PRs you will need. One targeting the 4.1 branch (this PR) 2. Another targeting the 5.0 branch? And link the implementation issue back to the spec issue? And set the 4.1 and 5.0 label on the implementation issue. Thanks!

@BalusC
Copy link
Contributor Author

BalusC commented Oct 7, 2023

ok but not sure I understand why .. github is capable of linking to issue in another repo as you can see in all previous tickets/prs/merges.

@BalusC BalusC merged commit 23654f6 into 4.1 Oct 7, 2023
1 of 2 checks passed
@BalusC BalusC deleted the faces_issue_1832_merge_ActionSource2_back_into_ActionSource branch October 7, 2023 21:40
@mnriem
Copy link
Contributor

mnriem commented Oct 8, 2023

ok but not sure I understand why .. github is capable of linking to issue in another repo as you can see in all previous tickets/prs/merges.

Ease of generating release notes and later on ease of finding for the issue in which branches it was fixed by having a common ancestor. Similary API issues do not show up as release notes issues in Mojarra.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants