Absolutely! Frequent changes may be made to both bundled and non-bundled addons. Bundled addons will be updated via the upgrader. For non-bundled addons, you will have to update them through the addons management screen (Admin Zone > Structure > Addons). You will be informed which ones need updated.

Once version 11 reaches release candidate, we do not expect frequent updates to non-bundled addons anymore. But it is still good practice to check after every update.

Yes, for basic non-custom v10 sites. However, expect some issues to arise in the process. And please report those issues to the tracker.

For v10 sites with non-bundled addons or customisations, upgrading to v11 will likely break the site until you update the non-bundled addons or temporarily remove the customisations.

We aim to have the upgrader fully functional for a large majority of types of sites and for sites using non-bundled addons by the time version 11 reaches release candidate stage.

We do not recommend upgrading production v10 sites at this time until v11 reaches stable.

Yes (probably). Always remember especially during alpha and beta phases that things can break. Please make backups first. And let us know on the issue tracker if an issue occurs.
 

Note: You cannot upgrade from 11 alpha to 11 beta without first upgrading to 11.alpha4 (if you are not already on 11.alpha4).

As of July 22, 2024, we entered beta status where our focus is now smashing bugs and stabilising the software. All planned features have been implemented for 11.0 (and most others deferred to 11.1 or later), though we may still merge in a few minor features or tweaks. The upgrader has been tested on a typical non-custom v10 site.

We will be releasing several beta versions in the beta phase.

We do not know when we will be able to release the first Release Candidate or stable versions at this time.

These plans are all subject to change without notice.

• Account: join, login, lost_password, setup_push_notifications
• Misc: contact_us
• Content: commandr_fs

• New major/minor versions are released as they are ready.
• Patch releases, primarily containing bug fixes, are only released for the latest supported major/minor version branch.

• Understand that Composr is developed and maintained by volunteers who dedicate their time to the project.
• Refrain from demanding free support or expecting developers to work on specific schedules.
• Avoid placing undue pressure on volunteers or pushing them beyond their capacity.
• Approach the community with respect and a collaborative spirit.
• Remember that offering financial sponsorship for desired features can accelerate development.

• Be specific and detailed. Identify particular issues and provide clear examples.
• Offer solutions. Suggest improvements or provide mockups demonstrating your ideas.
• Avoid vague statements. General comments like "it looks dated" are unhelpful.
• Understand design constraints. Consider factors like modularity, generality, feature density, compatibility, performance, and the subjective nature of design.

• Be comprehensive and self-contained. Provide all necessary information and context for the developers to understand your suggestion.
• Focus on widely beneficial features. Esoteric suggestions are less likely to be implemented.
• Understand developer constraints. Feature development depends on factors like developer availability, funding, and project strategy.
• Consider sponsoring features. Financial contributions can prioritize the development of desired features as it affords developers the time to implement it.