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

Remove minimize option #741

Closed
wants to merge 1 commit into from
Closed

Remove minimize option #741

wants to merge 1 commit into from

Conversation

ai
Copy link
Contributor

@ai ai commented Jul 4, 2018

What kind of change does this PR introduce?

feature removing

Did you add tests for your changes?

tests were removed

If relevant, did you update the README?

docs were removed

Summary

@evilebottnawi suggested just to remove minimize option to fix problem with old Browserslist #739

Does this PR introduce a breaking change?

yes

@ai
Copy link
Contributor Author

ai commented Jul 4, 2018

Do we need something else for this PR? Or you just don’t want to release at the night?

@alexander-akait
Copy link
Member

Or you just don’t want to release at the night?
yep

Also i remove some other options, I think tomorrow we will do release. I hope I will not be hated for this.

@shellscape
Copy link

For removing features we need very good documentation around why this has to be done. Is this comment (#739 (comment)) the reason why this is being removed? If so, this PR's description should include that statement and also provide direction for users who look at this PR, for how to move to another loader for that feature.

@ai
Copy link
Contributor Author

ai commented Jul 5, 2018

@shellscape you mean add love to ChangeLog?

@shellscape
Copy link

@ai changelog updates for breaking changes is required, yes. but PRs should have good info in them as well. I had to do some digging to find out why this PR was necessary, even with the link the PR description - users should not have to dig. Being verbose is good.

Copy link

@shellscape shellscape left a comment

Choose a reason for hiding this comment

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

The code changes look good, and the feature looks like it is cleanly removed. But in order to approve this PR I would need to see that the README has been updated to explain that the feature has been removed (just removing a section is not good for user experience) and what the migration path is for users who relied on that feature. Adding that information to the CHANGELOG or Github Release would also be helpful. But users are going to turn to the README first, as they always do.

@ai
Copy link
Contributor Author

ai commented Jul 5, 2018

Can I ask you to write docs? I am not native speaker.

@ai
Copy link
Contributor Author

ai commented Jul 6, 2018

@shellscape what section in docs you recommend to describe changes? Seems like all previous changes was not described in docs. And we should just use ChangeLog.

@evilebottnawi can we accept it and write reasons in ChangeLog?

@alexander-akait
Copy link
Member

@ai I think you can close this PR if favor #742, today i will do release

@ai
Copy link
Contributor Author

ai commented Jul 6, 2018

@evilebottnawi are you plan to release 1.0 today?

@alexander-akait
Copy link
Member

@ai yes

@ai
Copy link
Contributor Author

ai commented Jul 6, 2018

@evilebottnawi sure. I think it is better plan.

@ai ai closed this Jul 6, 2018
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.

None yet

3 participants