Feature tracking repo for Skygear releases
This repo only contains issues. Each issue track a new feature might be added to Skygear. Features can be voted by 👍 on the issue. Feel free to suggest new feature but please looks for existing one before opening new issue.
A feature is anything that:
- a blog post would be written about after its release
- requires multiple SDKs/components changes
- needs significant effort or changes Skygear in a significant way (ex. something that would take 10 person-weeks to implement, introduce or redesign a system component, or introduces API changes)
- users will notice and come to rely on
It is unlikely a feature if it is:
- fix a unit test or bugs
- refactoring code
- performance improvements
- adding error messages
Create an issue here once you:
- have written (or plan to write) the specification or design of the feature
- (optionally) have done a prototype in your own fork
Please comment on the feature issue to:
- request a review or clarification on the process
- update status of the feature effort
- link to relevant issues in other repos
For discussion of details of the design or specification. Please update the issue description once it is concluded.
Feature issue with "meta" label are Meta Feature Issue. It is usually when a few related requests are seen together and it span across multiple features completion to provide a workable solutions for Skygear users.
- For Meta Feature issues:
- Add
meta
label if an issue is about multiple features
- Add
- For Feature issues:
- Add the appropriate
area/
labels for which components it is related with. - Add
new/client
ornew/gear
labels for new features that require building a new services (gear) or client SDK, or both - Add
section/Core
orsection/Docs
if the features are expected to require work on development (Core), or documentation (Docs) - Add
section/Portal
if the feature include changes from Skygear.io portal, and require UI/UX design.
- Add the appropriate