Greyd.Suite is updated on a regular schedule, with new versions typically released every two weeks. Each update includes all available bugfixes and minor improvements completed since the last release. Critical fixes may be delivered sooner in a separate patch release. Major features are released less frequently and follow longer development and testing phases.
Updates may include changes to one or more components: the main Greyd Plugin, Greyd.Forms, Greyd Global Content, and the Greyd Theme. Smaller updates usually focus on resolving reported issues, improving stability, and adding minor enhancements. Major releases introduce larger features, structural changes, and broader improvements to compatibility, performance, or accessibility.
All public updates are documented in detail in the Greyd changelog, where each release lists the version number, release date, affected components, and categorized changes under Features, Improvements, Bugfixes, and occasionally Deprecations or Breaking Changes.
Development and Release Process
Bug reports, feature requests, and other feedback can be submitted via . Smaller requests or bugfixes that can be implemented quickly are usually integrated into one of the upcoming bi-weekly updates.
Once a fix or feature is implemented, it goes through the following steps:
- A merge request is created.
- The change is reviewed by another team member.
- Once approved, the code is merged into the main development branches.
- Merged changes are bundled into the next scheduled update.
In urgent cases, such as critical bugs, a dedicated patch release may be created. Customers can also request ZIP patch files for specific plugins or themes via the support portal, even before the next regular update.
Feature Development and Alpha/Beta Access
Larger features are planned as part of a long-term roadmap and often take several weeks to develop. Customer input is actively considered during planning, and features are frequently based on real project requirements and feedback.
The process for major features includes:
- Initial briefing and development based on requirements.
- Early alpha versions provided to selected customers for testing.
- Feedback collection through documented review processes.
- Refinement and stability testing in a beta phase.
Alpha and beta features can be made available in the public plugin or theme using internal constants:
IS_GREYD_ALPHA– Enables unfinished alpha features.IS_GREYD_BETA– Enables beta features in public releases.
From the first alpha release to a public launch, the timeframe is typically four to eight weeks, depending on complexity. Features are only made generally available after passing internal quality assurance, code review, and stability checks.