-
Notifications
You must be signed in to change notification settings - Fork 137
Launch compatibility matrix #183
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
Launch compatibility matrix #183
Conversation
I'm going to update this comment with a todo list of things I personally think should be done (or at least discussed) before merging.
|
|
I think I've mentioned this to @bitschmidty but noting it here so it doesn't get dropped:
|
One issue across the data files' RBF Usability sections that I would like to get agreement on is the "prefixes". It has caused confusion and I would like to standardize. Testing RBF involved the following scenarios:
Screenshots were taken for each of these scenarios which became the Usability section screenshots for each wallet. Each screenshot then had the scenario (ex 'Sending RBF Transaction - ' prefixed to the screenshot for context). That’s the history but I realize there is confusion since wallets that cannot send RBF signaling transactions now have this "Sending RBF Transaction" text in the screenshot captions.
@jnewbery @harding looking for feedback before rolling these out to the data files globally. |
@bitschmidty SGTM. Thanks! |
Sounds good to me too! |
Opened #192 for this |
The PRs #178 #179 #180 #181 #182 add a lot of unoptimized/unconpressed png images. I tested it for the png's in /img/compatibility/bitcoin-core and saw that their size could be reduced by around 37% to 43%. This would result in faster loading times for visitors on the compatibility pages. The optimization/compression is lossless. I've used a tool called optipng to optimize png's. Once the PRs are merged Output of Click to expand
|
+1 for optipng. I use it for most of the images I add to this repository and elsewhere (and have been for years). One option is to run it as part of the site build on Netlify via the Makefile. e.g. |
I somehow never looked into the man pages and thus didn't know about Another idea might be a test as a bash script for Travis, which checks if new png's are optimized. Failing when not optimized. However it might be better to open a separate issue for repository wide discussion. I just thought that this PR is the right place raise awareness before the compatibility pages go live. |
I'd prefer not to do something that slows down deploy and preview times.
I much prefer this, since it would only impact PRs that add pngs, and wouldn't slow down the preview sites for any PRs. Agree that we should move this discussion to a separate issue or PR. |
09628d0
to
a75b942
Compare
rebased on master |
pushed a couple commits here related to the Compatibility Matrix naming |
Tested ACK f4fa74f (assuming dependencies are merged first). |
Added a commit that adds more details to the blog post excerpt. |
ACK c272c7f |
This reverts commit 0226f3a.
c272c7f
to
c292640
Compare
rebased on master |
ACK c292640 |
c292640
to
eabc649
Compare
This PR now includes the blog post launching the compatibility matrix and other minor changes for the launch.
Still TODO: