Gacela Roadmap
Uff, I am not sure about that… Although, I would love to. The “problem” is that I don’t have ideas for new features or improvements so far. The range of features and scope of Gacela is pretty well define; plus everything is tested, and the code quality is really high… it’s hard for me to find spots to improve 😆
Currently, I am more focus on developing “Phel” (which uses Gacela in its core), and it’s working crazy good.
That said, from time to time, I find some minor things to improve, but nothing that would change the major version 1.x
😛
Comments
-
"everything is tested, and the code quality is really high… it’s hard for me to find spots to improve"
Famous last words before everything breaks down 😛
0 -
I “wish” to be proven wrong. The code is OSS, so there is nothing to hide 🪂
1
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 69 Spryker News
- 899 Developer Corner
- 760 Spryker Development
- 83 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 24 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 68 Spryker Safari Questions
- 50 Random