Spree Commerce development roadmap 2016

Damian Legawiec edited this page Mar 8, 2016 · 5 revisions

Public roadmap

Vote & comment on features you want to include in future Spree Open Source releases. Every vote counts!

Goals

  1. Support the current contributor community and businesses running Spree
  2. Send a clear message - Spree 3.0 will be supported for at least 2 years from the initial release with next versions to follow
  3. Release 3.1 as fast as we can with already great new features plus some more
  4. Start working on Spree 3.2 compatible with the current Rails/Ruby tech stack for new developers / projects
  5. Create a simple demo of Spree on Heroku for new developers via Heroku Button
  6. Create migration guides (3.0->3.1->3.2->3.3 and so on)
  7. Stimulate the community around Spree for more active participating in Spree development
    • feature requests from community (polls, discussions)
    • quickly review all incoming pull requests (leave no commit behind.. if it's acceptable)
    • work with the community on future roadmaps

Project Management

  1. Day to day communication on Slack (with integrated Github, CircleCI and other tools)
  2. GitHub issues for every new feature:
  3. Weekly core team video calls
  4. GitFlow approach
    • no code pushed directly to master
    • every pull request must be reviewed by a minimum of two Core Team members
    • every pull request must pass tests on CI

Community Management

  1. Total transparency of our work
    • roadmaps
    • development status
    • Core Team discussions
  2. Public communication
    • anyone can take a look at Core Team work
      • GitHub notifications
      • CircleCi notifications
    • anyone can communicate with the Core Team
    • anyone can start a discussion on any topic related to Spree development & future
  3. Slack public channels: http://slack.spreecommerce.com/
  4. Spree Mailing List: https://groups.google.com/forum/#!forum/spree-user
    • official announcements
    • helpdesk
  5. GitHub issues: https://github.com/spree/spree/issues
    • official announcements
    • feature request discussions
    • roadmap discussions
  6. GitHub Pull Requests
    • on reject - give a reason not to merge this and what should the author fix to proceed (unless it’s a total fubar)
    • quickly review pending PR as the highest priority

Strategy

  1. Only 3.x onward development
  2. Update all extensions in Spree Contrib to support 3.0, 3.1, 3.2 and so on
  3. Lean core features - every new feature as an extension maintained by Core Team, fewer major releases
  4. Spree 3.0.x
    • bugfixes
    • security patches
    • adding missing specs and fixing current ones
  5. Spree 3.1
  6. Spree 3.2
    • Rails 5 support
    • Ruby 2.3 support
    • other dependencies update
    • backward-compatible with Spree 3.0 in most cases (for gems/extensions developers - easy transition)
    • multiple codes per promotion - code generator
    • roles / permissions management for admin
    • RWD admin panel
  7. Spree 3.3
    • API migration from Rabl to Active Model Serializers - Solidus team already started this one (https://github.com/wildcardlabs/solidus_json_api) - maybe some cooperation?
      • AMS will be standard for any Rails 5+ apps
      • Rabl is not popular and it’s really hard to work with (that’s the general agreement)
    • Bootstrap 4 for frontend and backend
    • new RWD layout for frontend

Timeline

  1. Q1 2016
    • 3.0 further support
      • fix failing specs
      • review of all pending pull requests / issues currently in the GH repo
      • review of all code in master (what can be backported to 3-0-stable as a new minor versions 3.0.6, 3.0.7, 3.0.8)
      • bugfixes
      • security fixes
    • 3.1 public release
    • update most of the spree-contrib gems to support spree 3.1
    • 3.2 start of development
  2. Q2 2016
    • 3.0 further support (minor versions with security & bug fixes)
    • 3.1 further support (minor versions with security & bug fixes)
    • 3.2 public beta release (june)
  3. Q3 2016
    • 3.0 further support (minor versions with security & bug fixes)
    • 3.1 further support (minor versions with security & bug fixes)
    • 3.2 public release
    • update most of the spree-contrib gems to support spree 3.2
  4. Q4 2016
    • 3.0 further support (minor versions with security & bug fixes)
    • 3.1 further support (minor versions with security & bug fixes)
    • 3.3 start of development

For general discussion and support inquiries please use:

In the spirit of free software, everyone is encouraged to help improve this project. New Core Team members are welcome. You too can make history and join the Core Team.