Skip to main content
AIMEOS logoAIMEOS logo

Aimeos Roadmap

New versions of the Aimeos e-commerce library and its application/framework integrations are released on a quarterly base.

In the beginning of each year, new major versions will be available with a three month beta and a six month stabilization phase. They will contain code cleanups and reorganizations and aren't backward compatible with previous releases. During the stabilization phase, only features will be added that aren't likely to break backward compatibility to working code.

Latest stable (LTS) version:

  • will get bugfixes and security patches
  • will be supported for one year free of charge
  • is supported another four years with extended support (ELTS)

We recommend to use the stable releases for production and upgrade to the corresponding LTS version after it has been released.

Lines

Support periods

20192020202120222023
Version0104071001040710010407100104071001040710
2015.x
2016.x
2017.x
2018.x
2019.x
Support type
Beta release
Stable releases
Long term support (LTS)
Commercial extended LTS support
Lines

Planned for 2019+

  • Allow reordering images/prices/texts in admin interface
  • Use AI-based services for translation and image optimization
  • Use pre-configured attribute sets in product detail admin interface
  • Design JS API for easier handing of headless HTTP APIs
  • Merge mshop_order and mshop_order_base tables
  • Use PHP7 return type hints and maps/collections
  • Add supplier subpanel to product detail panel
  • Move product special price option to price item
  • Move view model code to view helpers
  • Provide Blade/Fluid/Twig templates for the HTML clients
  • Add iterateItems() method to all managers for large result sets
  • Implement settings panel in admin interface
  • Simplify product CSV import format
  • Use filesystem layer for all import files
  • Create simple to adapt Progressive Web Application based on Vue.js and Nuxt.js
  • Add scalar type to order product/service attributes to allow internationalization
  • Replace admin interface REST API by GraphQL API
  • Implement GraphQL API as alternative to JSON REST API for PWA frontend
  • Better reusable address partial for HTML and e-mail templates
  • Use document oriented way to store unit test data
  • Clean up and simplify unit test data
  • Drupal integration
  • Wordpress integration
  • Frontend editing