Skip to content
This repository has been archived by the owner on Aug 5, 2020. It is now read-only.

Release v2.0.1 #77

Closed
wants to merge 71 commits into from
Closed

Release v2.0.1 #77

wants to merge 71 commits into from

Conversation

ericawright
Copy link

Status: Ready for Review
Owner: @ericawright
Reviewers: @johnboxall @fractaltheory @MikeKlemarewski @mikenikles @stewartyu

Version 2.0.1 release

Issues Fixed

#66
#65
#60
#51
#49

@kpeatt
Copy link
Contributor

kpeatt commented Mar 18, 2016

Excited that this is still actively developed! Nice work @ericawright.

@jansepar
Copy link

@ericawright do we want to get the changes to bower into this release?

@ericawright
Copy link
Author

@jansepar it seems like it, at least that was what was suggested

@mikenikles
Copy link

I suggested to include the bower changes since this release is already a major upgrade to what's currently public.

@marlowpayne
Copy link

Maybe this is a bit too "blue-sky" for our current resourcing/workload, but it would be cool to see this release of Pikabu bring it up to current best practices like:

  • Purge lib/zeptojs from the repo
  • Prepare Pikabu for publishing on NPM
  • Update JS linting to eslint and rulesets from code-style v2.4.2
  • Update SCSS compilation to libsass through grunt-sass
  • Lint SCSS with sass-lint

I'm happy to answer any questions about these best practices and how to make them happen.

@stewartyu
Copy link

@marlowpayne I agree these are great things to happen eventually, but the scope of this release should be to "release a working Pikabu 2.0" as the original Pikabu 2.0 release was broken. My recommendation would be to publish this release (unless there are functional blockers), and work on your items in 2.0.2.

Erica Wright and others added 10 commits March 28, 2016 11:18
Due to an issue in some browsers, using `@support` breaks the `:not()`
CSS pseudo selector. See here:

https://bugs.chromium.org/p/chromium/issues/detail?id=257695

In particular, this was an issue in our project here:
https://mobify.atlassian.net/browse/CF-105

Also: Removed the Chrome specific fix from before, as I cannot
reproduce that particular issue anymore.
This was here before the original introduction of `@support`, so the
`width: 100%` should be re-added.
change all bower_components to node_modules
@ericawright ericawright closed this Nov 2, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

7 participants