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

Consider moving WaitStrategy along WQP and TP #1052

Closed
smaldini opened this issue Feb 1, 2018 · 0 comments
Closed

Consider moving WaitStrategy along WQP and TP #1052

smaldini opened this issue Feb 1, 2018 · 0 comments
Labels
warn/api-change Breaking change with compilation errors
Milestone

Comments

@smaldini
Copy link
Contributor

smaldini commented Feb 1, 2018

Linked to #1051 . If the two processors move, we could just remove that strategy altogether from MonoProcessor by providing an alternative in reactor-extra.

@smaldini smaldini added the warn/api-change Breaking change with compilation errors label Feb 1, 2018
@smaldini smaldini added this to the 3.2.0.RELEASE milestone Feb 1, 2018
@simonbasle simonbasle added status/declined We feel we shouldn't currently apply this change/suggestion and removed status/need-decision This needs a decision from the team labels May 17, 2018
@simonbasle simonbasle modified the milestones: 3.2.0.RELEASE, [icebox] May 31, 2018
@simonbasle simonbasle removed this from the Backburner milestone Apr 19, 2019
@smaldini smaldini reopened this May 7, 2019
@smaldini smaldini removed the status/declined We feel we shouldn't currently apply this change/suggestion label May 7, 2019
@smaldini smaldini added this to the 3.3.0.M1 milestone May 7, 2019
smaldini pushed a commit that referenced this issue May 7, 2019
# Conflicts:
#	reactor-test/build.gradle
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
warn/api-change Breaking change with compilation errors
Projects
None yet
Development

No branches or pull requests

2 participants