-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Next release after v2.7.5 #1383
Comments
Now send as #1487 |
PR #1408 - Have minify() and tests use figure_out_scope() as uglifyjs CLI does |
Sorry for the huge delay… Moving house and the holidays have taken up way more time than I had anticipated. We should definitely start thinking about setting up an UglifyJS organization on Github, to make the project more manageable. @mishoo: thoughts? |
PR #1426 - add missing LHS cases which |
#1408 might warrant the next release to be 2.8.0. |
PR #1425 - augment evaluate to extract within objects |
PR #1427 - optimise binary operands with evaluate() |
PR #1431 - fix mangling collision with keep_fnames |
#1366 - Move minify api to portable api |
#1437 - Slightly improve a |
|
#1445 - fix corner case in keep_fnames |
#1446 - enable typeof "undefined" for general use |
#1450 - drop unused: toplevel, assign-only |
#1453 - fixes and improvements to [].join() |
#1452 - tweak do-while loops |
#1457 - fix sequences_limit |
#1454 - improve string concatenation |
#1451 - clean up |
I think there's more than enough in the PR queue for a 2.8.0 release. New patches may start to conflict soon. |
|
#1476 - improve keep_fargs & keep_fnames |
#1473 - improve reduce_vars |
#1477 - evaluate AST_SymbolRef as parameter |
Queue is getting large |
Maybe I should do a premerge some day |
@avdg I can help with any merge conflicts / test failures 😅 |
You already took over the whole project :p Well thanks anyway, as I seem to be specialized in tokenizer only atm... :-) |
Actually I'm thinking about this (it's git/github related)
git is just a collection of scripts (well, it's a bit optimized). So this would make life so much easier if a script called |
#1469 - enhance |
#1479 - add benchmark & JetStream tests |
|
#1483 - improve |
@avdg not sure if this is related to what you said in #1383 (comment) |
Unless I'm mistaken that tool gives you an easy way to set up a local branch for each PR, rather than mixing a select number of PRs together on one branch. I don't think there's a silver bullet for that other than merging all the PRs into a single branch. Normally that branch is called |
@kzc yes, you'll still have to merge each branch yourself. But from the looks of it you don't have to go into each PR's web page to work out where the repository/branch is, which I thought was what @avdg asked about. Edit: this one is from GitHub https://help.github.com/articles/checking-out-pull-requests-locally/ |
If you want to patch a bunch of PRs into your current branch for testing (no commits) you could use this bash script: $ cat pr-patch.sh
sample usage:
It assumes you are in the source root. |
I'm having some fun with this batch file on Windows:
Need to manually edit the commit message, but otherwise seems pretty automatic. |
This command will commit a github PR to your local branch with original date, author attribution and comments:
|
#1488 - remove extraneous spaces between ++/+/--/- |
#1491 - introduce |
#1494 - fix |
#1496 - clean up |
I think this Issue should closed in favor of: #1485 2.8.0 staging |
This can be closed. |
@kzc thanks for keeping track 😉 |
No description provided.
The text was updated successfully, but these errors were encountered: