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

Let's release Reek 5 #1305

Closed
troessner opened this issue May 17, 2018 · 14 comments
Closed

Let's release Reek 5 #1305

troessner opened this issue May 17, 2018 · 14 comments

Comments

@troessner
Copy link
Owner

Here's my suggestion list:

Afterwards we should release a new version on CodeClimate to fix the problems with the Syntax smell

Thoughts? :)

@mvz
Copy link
Collaborator

mvz commented May 18, 2018

Ideally, I'd like to include all of the breaking changes. Any that we don't include should be closed.

@mvz
Copy link
Collaborator

mvz commented May 18, 2018

I'm going to pick up some of those breaking changes over the weekend.

@troessner
Copy link
Owner Author

troessner commented May 18, 2018

Ideally, I'd like to include all of the breaking changes. Any that we don't include should be closed.

Good point.

I'm going to pick up some of those breaking changes over the weekend.

Me too probably. Let's make sure we always assign the issue to ourselves and write a comment that we're working on it to not duplicate work :)

@troessner
Copy link
Owner Author

Almost there <3 ;)

@troessner
Copy link
Owner Author

troessner commented Jun 10, 2018

Status:

Recently done:

* Finish:
  * #1322 
  * If its not too much effort, sneak in #1319 

Left to do:

Release v5

Post release

@troessner
Copy link
Owner Author

Now that #1322 is out i'd like to give #1319 a quick shot just to make sure that in the scope of the pull request we do not need any other breaking change. That is something I'll look into today.

@troessner
Copy link
Owner Author

troessner commented Jun 17, 2018

Ok, it looks like #1317 won't add anything breaking so we don't have to wait for this to finish to release Reek 5 ;)
Let's continue with #1324

@troessner
Copy link
Owner Author

Ready to roll, let's go!

@mvz
Copy link
Collaborator

mvz commented Jun 19, 2018

#1343 may introduce a breaking change to Examiner so we should probably wait for that.

@troessner
Copy link
Owner Author

Right, good point!

@mvz
Copy link
Collaborator

mvz commented Jun 20, 2018

We also need to actually add Syntax.md or remove the detector to really fix #1291.

@troessner
Copy link
Owner Author

Let's finish and merge all PR's labeled with breaking changes and then release v5 ;)

@mvz
Copy link
Collaborator

mvz commented Jun 28, 2018

All breaking changes were merged 🎉!

@troessner
Copy link
Owner Author

Wait, one more! 😆
Source: click

What a coincidence 🌈

@mvz mvz closed this as completed in #1324 Jun 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants