That depends on several factors. Here are some pros and cons of each:

It is not recommended you do this because you may run into issues. For example, some changes were made in crypto_master.php and data/upgrader2.php prior to the first v11 alpha. These changes will result in a broken upgrade unless you already pulled these changes from git. Similar situations could happen in the future as well.

It is recommended you either discard the git install and use a fresh install from the Downloads, or to maintain a git install and a bleeding-edge release install separately. Do not combine the two.

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.

• Filtering constraints: Limits filtering options to those incorporated in the data structure.
• Historical data limitation: To maintain site stability, statistics older than 31 days aren't pre-processed. This may lead to data gaps if the system scheduler malfunctions or statistical data is manually deleted.

• GDPR compliance: Prevents indefinite storage of raw (potentially personal) data while preserving historical statistics.
• Computational efficiency: Avoids real-time execution of complex calculations, ensuring optimal performance.
• Scalability: Handles vast amounts of data without performance degradation.
• Responsiveness: Enables quick and seamless statistics browsing and filtering.
• Data accessibility: Makes generated data readily available for other Composr components.

• Quick reference: Available on the Admin Zone dashboard staff checklist.
• Target setting: Allows setting targets against KPIs, visualized on graphs and in overview summaries.
• Notifications: Staff members receive regular notifications regarding target achievement status.

• Random tracking code: Choose a random tracking code from a set and activate it for the user session.
• Conditional output: Generate different content variations based on the active tracking code.

• URL parameter: The _t URL parameter can contain any custom tracking code, automatically registered by the stats addon.
• Recommend addon: This addon automatically includes tracking codes for the referral source, referring member, and the referred page.
• Member joining: When a referred member joins, the referring member receives points and a friend request.
• Referrals addon: Allows manual tracking code input upon joining and facilitates a referrer reward system.
• Stats addon: Generates graphs of tracking codes, including conversion rate measurements.
• User lookup tool: Allows checking if a user accessed the site via a tracking code.
• Tempcode integration: Inject tracking codes into Tempcode using symbols like {$SET_TRACKING_CODE,some code} or {$SPLIT_TEST,some code,some other code}.

• Inbuilt events: Automatically recorded for actions like form submissions, purchases, newsletter signups, etc.
• Tempcode symbol: Use the {$LOG_STATS_EVENT,event} symbol within your templates to track events when the template is displayed.
• JavaScript function: Employ the $cms.statsEventTrack JavaScript function to track events from within your JavaScript code.
• HTML data attribute: Add data-click-stats-event-track="{ category: 'some event', nativeTracking: true }" to HTML elements. This method acts as a wrapper for the JavaScript function.
• URL wrapping: Wrap URLs in links using the {$STATS_TRACK_URL,URL,event} symbol. This approach records events via a redirection script and doesn't rely on JavaScript.

• Offers sophisticated functionality for professional marketers.
• Integrates with other Google products like AdSense and Search Console.
• Provides insights based on Google's marketing data, such as visitor demographics.

• Limited to web visit data unless custom programming or complex configuration is implemented.
• Relies on JavaScript for tracking, which can be blocked by users.
• Uses tracking cookies, raising privacy concerns and potential GDPR compliance issues.
• Data is potentially sold to third-party data brokers or used for targeted advertising by Google.
• Closed-source platform.

• Server-side tracking, independent of JavaScript and browser configurations.
• Contextual information and graphs for data beyond web visits (e.g., sales).
• Enhanced privacy as it only uses IP addresses, session IDs, and member IDs.
• Complete data control as it is hosted on your website.
• Open-source addon, fully customizable.

• Documentation & Tutorials: Utilize the extensive Composr documentation and tutorials available online to familiarize staff with the platform's functionalities.
• Mentorship: Pair experienced staff with newcomers to provide guidance and support during the initial learning phase.
• Private Forums & Chat: Create dedicated communication channels where staff can exchange knowledge, ask questions, and share best practices.
• Regular Meetings: Conduct regular staff meetings to discuss updates, share information, and address any arising challenges.
• External Resources: Leverage external resources like online courses or workshops focused on relevant skills, such as content management or community moderation.