Skip to content

Release: copy sizzle to external folder in dist, remove files during dist copy #3116

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

Closed
wants to merge 3 commits into from

Conversation

timmywil
Copy link
Member

@timmywil timmywil commented May 11, 2016

Summary

Fixes a couple release issues. Tested with jquery-release.

Fixes gh-3094
Fixes gh-2945

Checklist

Sorry, something went wrong.

@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @markelog, @scottgonzalez and @bperel to be potential reviewers

@timmywil timmywil changed the title Fix release Release: copy sizzle to external folder in dist, remove files during dist copy May 11, 2016
i = rmIgnore.length;

while ( --i ) {
rmIgnore[ i ] = Release.dir.dist + "/" + rmIgnore[ i ];
Copy link
Member

Choose a reason for hiding this comment

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

Why not

rmIgnore = rmIgnore.map( function( dirname ) {
    return Release.dir.dist + "/" + dirname;
} );

? The i variable would be unnecessary.

Copy link
Member Author

Choose a reason for hiding this comment

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

Do all the nodes we support have map?

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, 0.10 has it. I thought it didn't for some reason. I'll make the switch.

Copy link
Member

@markelog markelog May 12, 2016

Choose a reason for hiding this comment

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

Keep in mind that this code will be used by the maintainers only :)

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, Node.js has been ES5-compatible for a long time now. :)

@mgol
Copy link
Member

mgol commented May 12, 2016

From what I see part of it has already partially landed on 1.12-stable in 59003ae (but not on 2.2-stable or master)?

@timmywil
Copy link
Member Author

Hmm. That's odd. I don't remember pushing that.

@timmywil
Copy link
Member Author

@mgol My mistake. I must have had the commit on that branch locally for a minute. It's been reverted until this PR is merged.

@timmywil timmywil closed this in 95c7ab6 May 13, 2016
@timmywil timmywil deleted the fix-release branch May 13, 2016 15:36
timmywil added a commit that referenced this pull request May 13, 2016
timmywil added a commit that referenced this pull request May 13, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
5 participants