We are working to migrate the existing Forge to another forge platform and during this migration process the current system may experience intermittent interruptions of the service provided through the platform. We expect to complete this migration phase in the course of November.
We have created an email list / group (email@example.com / Forge Migration Google Group) to send your questions about migration that we will monitor and answer. You can also subscribe to this group to receive notifications about migration process.
We would also like to emphasize that you as Forge user can rest assured that your data will be migrated to the new system.
We apologize for any inconvenience you may experience during coming weeks.
We plan to start migration on Wednesday 14th at 17.00 CET. Starting from this time existing Forge won´t be available and it will last till 24.00 CET Thursday 15th. At this time we expect to go live with a new infrastructure that substitutes Forge.
Please be aware that during the next days after migration system may experience intermittent interruptions.
After the go live, we will continue working on improving the new infrastructure and will gradually add further functionality.
Forge Replacement Architecture
At this moment going forward we don´t plan to have Forge as integrated service like it was before.
New infrastructure will consist of two parts:
- Modules publication and search service. That is the most important part of the infrastructure that is required to support Openbravo modularity.
- Development Tools. Set of separate systems hosted by Openbravo (code, issues, wiki, downloads and forums) to which data from existing Forge will be migrated. Modules publication part will have links to them. Restrictions of Development Tools:
- Development Tools are available only for existing Forge projects / modules. New projects and modules won´t have any development tools provided by Openbravo by default (exceptionally we can provide it for new projects also for power Forge users) . We can recommend other third party development tools that Community can use (for example, Bitbucket). Later on if there is a demand we might develop integration between Modules Publication and one of those third party Development Tools .
- Development Tools for existing projects will have some limitations: Some of them (code, downloads) won´t be integrated with SSO and separate login credentials would be provided, some of them (wiki, forums) won´t have private parts.
We believe this is the best approach. It separates concerns and allows us to focus on core Openbravo asset which is Modules publication and promotion service. While it gives our Community freedom to chose whatever tools they find useful to develop these modules from the companies that specialize on those tools.