Pending releases

[soumak77]

Conversation was started on #1, but the thread has grown to include topics that shouldn't be in the initial release. I want to ensure we are all on the same page in terms expectations for upcoming releases. Here is what I'm thinking so far and will update these requirements as needed:

• Release 1.2.1 (Rebranding)
  • Description
    • Drop in replacement for Foundation for Apps 1.2. No changes should be required to consume this version.
    • Documentation for the release will still leverage Foundation for Apps docs.
  • TODO
    • Merge rebanding branch into master
    • Add gulp task to publish new version of distro files to github and tag them with the version
      • basically copy/paste example from gulp-tag-version and trigger after running build
    • Publish NPM/Bower packages
  • PRs
    • Rebrand from Zurb Foundation for Apps to Base Apps Angular Base #2
    • Browser support #5
    • remove gulp-ruby-sass dependency #8
    • remove gem install from travis #10
    • Feature/rebrand #12
• Release 1.2.2 (Bug Fixes and Documentation)
  • Description
    • Bug fixes on top of the 1.2.1 release. Minimal changes may or may not be required to consume this version.
    • Documentation for this release will be fully migrated to github pages.
  • TODO
    • Discuss changes to documentation: Documentation updates #4
    • Create new PRs for fixes in old fork: https://github.com/zurb/foundation-apps/pulls
• Release 1.2.3 (Bug Fixes)
• Release 1.2.4 (Tabs Fixes)
  • Improved tab functionality and documentation

[tolyo]

Rebranding merged to master

[soumak77]

@tolyo I'm hoping to get back to this in a couple days. I'd like to publish the first release this weekend.

[tolyo]

@soumak77 np

[soumak77]

Version 1.2.1 has been published. Unfortunately the name angular-base is taken in the bower registry by this repo. I've registered the package under angular-base-apps. I originally published the npm package under angular-base, but then switched to angular-base-apps to be consistent with bower.

[tolyo]

Brian, I say we rename the git repo too.

[soumak77]

@tolyo yeah that would probably be for the best. I'll do that now and re-register the new repo with bower and npm.

[soumak77]

I wasn't able to unregister/register the package on bower, so I opened an issue on bower

[tolyo]

@soumak77 Brian, how would we go about other people's pull requests? Is that something we can migrate or is that something we would have to go through one by one?

[soumak77]

@tolyo this has already been completed with #14

[tolyo]

@soumak77 Ok. I guess we still need to monitor for them as people keep creating them for zurb:master

[soumak77]

Version 1.2.2 has been published

[soumak77]

I've creating separate issues for the remaining items so that this can be closed.