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

Roadmap v6.0.0 #686

Closed
9 tasks done
yannickcr opened this issue Jul 17, 2016 · 24 comments
Closed
9 tasks done

Roadmap v6.0.0 #686

yannickcr opened this issue Jul 17, 2016 · 24 comments

Comments

@yannickcr
Copy link
Member

yannickcr commented Jul 17, 2016

So here's what I have in mind for now:

Do you see anything else that could be good to change/improve?

@ljharb
Copy link
Member

ljharb commented Jul 18, 2016

That seems good to me.

lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Jul 18, 2016
This has been deprecated for a while. We have decided to remove it
entirely for 6.0.0 (jsx-eslint#686).

Fixes jsx-eslint#549.
lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Jul 18, 2016
This has been deprecated for a while. We have decided to remove it
entirely for 6.0.0 (jsx-eslint#686).

Fixes jsx-eslint#549.
lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Jul 18, 2016
This rule is JSX-specific, not React-specific. Changing its name makes
this clearer. I've kept the old one around as deprecated. We can remove
it at the next major version bump.

Addresses jsx-eslint#668 and jsx-eslint#686.
lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Jul 18, 2016
This rule is JSX-specific, not React-specific. Changing its name makes
this clearer. I've kept the old one around as deprecated. We can remove
it at the next major version bump.

Addresses jsx-eslint#668 and jsx-eslint#686.
lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Jul 18, 2016
This rule is JSX-specific, not React-specific. Changing its name makes
this clearer. I've kept the old one around as deprecated. We can remove
it at the next major version bump.

Addresses jsx-eslint#686. Fixes jsx-eslint#668.
lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Jul 20, 2016
This rule is JSX-specific, not React-specific. Changing its name makes
this clearer. I've kept the old one around as deprecated. We can remove
it at the next major version bump.

Addresses jsx-eslint#668 and jsx-eslint#686.
lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Jul 20, 2016
This rule is JSX-specific, not React-specific. Changing its name makes
this clearer. I've kept the old one around as deprecated. We can remove
it at the next major version bump.

Addresses jsx-eslint#668 and jsx-eslint#686.
lencioni added a commit to lencioni/eslint-plugin-react that referenced this issue Jul 20, 2016
This rule is JSX-specific, not React-specific. Changing its name makes
this clearer. I've kept the old one around as deprecated. We can remove
it at the next major version bump.

Addresses jsx-eslint#686. Fixes jsx-eslint#668.
@ljharb
Copy link
Member

ljharb commented Jul 22, 2016

5 down, 4 to go!

@lencioni
Copy link
Collaborator

On this roadmap, you have

Enable allow-in-func mode by default in no-did-mount-set-state and no-did-update-set-state rules

I'm not entirely sure what you want done here? Does this amount to removing the option and just having it always be the case, or should this be the case by default and there would be a new option like disallow-in-func?

@yannickcr
Copy link
Member Author

should this be the case by default and there would be a new option like disallow-in-func

I was more thinking about something like this.

@ljharb
Copy link
Member

ljharb commented Jul 25, 2016

It looks like the last 3 issues all have PRs up - how quickly do you think we could get to a v6?

@yannickcr
Copy link
Member Author

@ljharb I hope to publish an RC before friday and the final this week-end if there is no major issue.

@ljharb
Copy link
Member

ljharb commented Jul 27, 2016

@yannickcr there's still one unchecked item on the list - is that punted to v7?

@petersendidit
Copy link
Contributor

I just rebased #699 so it should be able to be merged cleanly.

@yannickcr
Copy link
Member Author

@ljharb no, still planned for v6 :)

@ljharb
Copy link
Member

ljharb commented Jul 27, 2016

Should this be reopened until that's merged?

@yannickcr
Copy link
Member Author

Yep

@yannickcr yannickcr reopened this Jul 27, 2016
@ljharb
Copy link
Member

ljharb commented Jul 29, 2016

@yannickcr any more things to add to the above checklist, or are we good for a final release? :-)

@yannickcr
Copy link
Member Author

Still a few changes and I think I'll be good to push an RC in the coming hours.

@yannickcr
Copy link
Member Author

yannickcr commented Jul 29, 2016

v6.0.0-rc.0 is now published on npm.

You can install it with npm install eslint-plugin-react@next

@ljharb
Copy link
Member

ljharb commented Aug 1, 2016

I see rc.1 is out. Is there a planned time to release v6?

@nwhitmont
Copy link

nwhitmont commented Aug 1, 2016

What's the timeline on v6.0.0 release? Appears to be blocking airbnb eslint config installation --airbnb/javascript#936

@yannickcr
Copy link
Member Author

@ljharb @nwhitmont v6.0.0 should be released in the coming hours.

@yannickcr
Copy link
Member Author

v6.0.0 is now published on npm

@lencioni
Copy link
Collaborator

lencioni commented Aug 1, 2016

Thanks for all of your hard work on this plugin @yannickcr! This plugin has greatly helped me and my teams over the past couple of years, and I just wanted to make sure you feel appreciated for the effort you put in here. This is such an valuable tool that you've built. 👏 👏 👏

Thinking ahead to future major version bumps, I'm wondering--is there anything that I (or others who are interested) can do to help make sure that things continue to run smoothly? I don't want you to feel like you are running this thing all by yourself.

@nwhitmont
Copy link

Thank you @yannickcr !

@yannickcr
Copy link
Member Author

Thank you all for your support 😍 , and thanks for your contributions @lencioni 😃

Thinking ahead to future major version bumps, I'm wondering--is there anything that I (or others who are interested) can do to help make sure that things continue to run smoothly? I don't want you to feel like you are running this thing all by yourself.

Well, there is more and more open issues and PRs to review/validate and I have some difficulties to keep up with all of this. I added @ljharb as a contributor a few months ago and he made a really great work on issues triage, PRs validation and responding to users questions ❤️ . So I'm now thinking about adding more people as contributors.

Would you be interested to be added as contributor @lencioni?

@ljharb
Copy link
Member

ljharb commented Aug 2, 2016

I'm biased because I work with @lencioni, but I highly endorse his being added!

@lencioni
Copy link
Collaborator

lencioni commented Aug 2, 2016

Would you be interested to be added as contributor @lencioni?

Sure!

@yannickcr
Copy link
Member Author

Done :)

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

No branches or pull requests

5 participants