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
Meta: rc branch status / repo cleanup #421
Comments
As you mentioned it has been a few months since I last worked on it, so I can't recall from the top of my head all the unresolved issues with the rc branch, but the few major ones as I recall were:
I'll try and have a closer look at what else might still be missing/broken and make a list of things that need to be done before it can be merged to master. |
Thanks! |
I've merged it to master (to avoid more bug fixes and pull requests on the old version), but the above mentioned issues still remain to be fixed. |
That's progress, anyway--thanks! I guess next step might be ensuring that all test failures are real (i.e. due to missing or broken functionality, not due to broken tests). Once that's done, or maybe even sooner, bug triage could be easily crowdsourced (e.g., on each issue that seems like a valid bug you can ping the author to see if their problem is still present on master, and maybe also add a "please retest" label to get more attention). Getting help implementing gradient support might just be a matter of adding an issue for it with a "help wanted" label or similar and a description of current progress and snags. Thanks again for being so responsive! |
Tests are working now (as in running), so anything failing now is a missing feature. |
Nice! Thanks for all your work on this. |
Tiny other things:
|
Great progress so far, @niklasvh. Any word on the issues mentioned in my previous comment? Notably, the commits missing from master: https://github.com/niklasvh/html2canvas/compare/v0.4 ... Thanks yet again! |
The border-radius commit broke existing border-radius tests, so it was omitted for that reason. For the IE9 issue, the suggested fix had nothing to do with the root problem, which was using incorrect positions for cropping. The contributing readme should get updated. I deleted the old branches. |
Added first prerelease (0.5.0-alpha1) to |
Closing, #1167 |
Hi @niklasvh. Thanks for a great tool! It's really freaking awesome.
I just wanted to know if there's anything we can do to help make the rc branch pass all the build tests, maybe turn the rc branch into the new develop branch (or at least merge it), triage (categorize, close/merge, assign to milestones) all the issues, and get a new version out?
Looks like the last commit was a couple months ago, though it also looks like a bunch of issues have been addressed on the rc branch, even though the build fails. Meanwhile, lots of (possibly-irrelevant) issues against the year-old version continue to be filed.
Do you need collaborators? Or can you make a "helpwanted" label to highlight particular issues that break the build on the rc branch? I know it's not your full-time job, but--whenever you have a chance--feel free to use the crowd to help get everything in ship shape.
Thanks again, and keep up the amazing work!
The text was updated successfully, but these errors were encountered: