The Midgard Project is celebrating its 10th Anniversary on May 8th 2009. Midgard 1.0.0 was released in 1999, starting the free software project:

The Midgard Project has finally released the first public version of Midgard Application Server Suite. The new release contains Midgard core libraries, a PHP3-based web application server for the Apache platform and the needed web-based administration tools.

Midgard is freely-available platform for creating powerful web applications. It is fully based on Open Source software, giving you freedom to create your solutions in an open environment. Midgard is the tool for creating, modifying and maintaining dynamic database-enabled web services.

Midgard already has a quite good set of features for creating powerful web sites, and is being used with successful results by some commercial and uncommercial organizations. But this is not where the development will end; rather, the development team also has more ambitious goals about revolutionizing the way people think about web development.

Midgard developer Henri Bergius has posted a blog entry about the occasion.

You can join the celebrations either in Helsinki, Finland, or by telling about your first Midgard experiences on Qaiku.

About this release

Midgard2 9.03 is targeted at web framework and desktop application
developers. It provides a comprehensive set of content repository APIs
that can be used to build replicated information applications that
share their information using a common storage layer and replication
tools.

Vinland series of Midgard2 is not intended to act as a content
management system, and so no CMS tools are shipped with the release.
Midgard2 Vinland however can be used to build a CMS, or to refactor
existing CMS tools to work with a repository-centric model.

In this release we provide Content Repository API bindings for the
following programming languages: C, Python, PHP and Objective-C. D-Bus
signals are used to inform different Midgard2 applications about
things happening in the repository, enabling for example a PHP website
and a Python background process to communicate with each other.

Midgard2

Midgard2 is a content reporitory. It provides an object-oriented and
replicated environment for building data-intensive applications.

Midgard's philosophy includes building on top of a well-known and
supported GNOME libraries like glib and libgda on the system end, and
connecting with popular programming languages like PHP and Python.
Data storage can utilize SQLite with desktop and mobile applications,
or a database server like MySQL or Postgres for web application
storage.

The Midgard2 platform enables developers to define a storage structure
once and use it on both web and desktop applications, with the
possibility of easy data replication between the two.

Read more about Midgard's content repository approach:

• http://bergie.iki.fi/blog/midgard2_at_fscons-your_data-everywhere
• http://bergie.iki.fi/blog/midgard_and_jcr-a_look_at_two_content_repositories
• http://teroheikkinen.iki.fi/blog/midgard_workshop_at_fscons

New Midgard architecture

Language independence

Midgard is also language independent and due to its powerful
architecture has proven as stable, secure and flexible solution
implemented in various environments:

• PHP5 extension for web application and CMS development
• Python module for desktop application and background process development
• Objective-C package for Mac OS X and GNUstep developers

Database independence

The Midgard 1.x was heavily coupled with the MySQL database. The new
Midgard2 architecture is instead built on top of libgda, the GNOME
database abstraction layer. This enables Midgard to be used with
various storage engines, including:

• MySQL
• Postgres
• SQLite
• Microsoft SQL Server
• Oracle
• DB2

Built-in replication and metadata

All Midgard objects are automatically equipped with a consistent set
of metadata properties that can be used for access control and
workflow.

In addition, Midgard provides an API for serializing and unserializing
stored objects in XML format that can be used for replicating data
between different systems. The replication architecture can be used
for staging/live web environments or mobile applications that
synchronize between each other or a web back-end.

Planned for next Midgard2 releases

• Midgard MVC, an elegant PHP MVC framework written for Midgard2

Midgard resources

• Download page and changelog for latest release
• Bug reporting

User and developers support:

• Users' forum
• Developers' forum
• IRC: #midgard on irc.freenode.net
• #midgard on Qaiku

About Midgard

The Midgard Framework development started in 1997 and it was initially
released as free software in May 1999. Midgard Project has since
gathered an active user and developer community, powering thousands of
web sites ranging from simple organizational intranets to large
community portals.

Midgard is being developed by an international team of professionals.
Midgard's development team includes new media designers, system
integrators and content management consultants. Midgard development
has been supported by several commercial and governmental entities
including the European Union and the Swedish Internet Foundation.

Midgard2 is free software available under the GNU LGPL license.

http://www.midgard2.org

Contacts

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard spokesman
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org

• Authentication routines fixes (#485, #765).
• Fixed major memory corruption in php5-midgard (#1054, #1058).
• Midgard installer improvements.

More than 70 tickets have been closed for this release. See the Midgard
issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.5+Ragnaroek

Planned for next maintenance release:

• More performance tuning
• Unit tests for midgard-php and MidCOM DBA layers
• New Midgard visual guidelines deployed more widely
• Filesync git integration for collaborative site development
• MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.6+Ragnaroek&order=priority

Source downloads
http://www.midgard-project.org/download/

Binary packages
http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started
http://www.midgard-project.org/documentation/getting-started/

Issue tracker
http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/

Due to move of the physical server all PEAR channels will be offline today (2009.04.24) from 5pm (GTM+3) untill later in the evening.

We're sorry for any inconvinience.

UPDATE 2009.04.25 00:10 GMT+3

The servers are now running with proxy set up so you don't have to wait for DNS to update. Getting the servers on-line took a bit longer than expected, sorry about that.

About this release

Midgard2 9.03 is targeted at web framework and desktop developers. It provides a comprehensive set of content repository APIs that can be used to build replicated information applications that share their information using a common storage layer and replication tools.

Vinland series of Midgard2 is not intended to act as a content management system, and so no CMS tools are shipped with the release. Midgard2 Vinland however can be used to build a CMS, or to refactor existing CMS tools to work with a repository-centric model.

In this release we provide Content Repository API bindings for the following programming languages: C, Python, PHP and Objective-C. D-Bus signals are used to inform different Midgard2 applications about things happening in the repository, enabling for example a PHP website and a Python background process to communicate with each other.

Midgard2

Midgard2 is a content reporitory. It provides an object-oriented and replicated environment for building data-intensive applications.

Midgard's philosophy includes building on top of a well-known and supported GNOME libraries like glib and libgda on the system end, and connecting with popular programming languages like PHP and Python. Data storage can utilize SQLite with desktop and mobile applications, or a database server like MySQL or Postgres for web application storage.

The Midgard2 platform enables developers to define a storage structure once and use it on both web and desktop applications, with the possibility of easy data replication between the two.

Read more about Midgard's content repository approach:

• http://bergie.iki.fi/blog/midgard2_at_fscons-your_data-everywhere
• http://bergie.iki.fi/blog/midgard_and_jcr-a_look_at_two_content_repositories
• http://teroheikkinen.iki.fi/blog/midgard_workshop_at_fscons

New Midgard architecture

Language independence

Midgard is also language independent and due to its powerful architecture has proven as stable, secure and flexible solution implemented in various environments:

• PHP5 extension for web application and CMS development
• Python module for desktop application and background process development
• Mono module for desktop application and background process development in C#

Database independence

The Midgard 1.x was heavily coupled with the MySQL database. The new Midgard2 architecture is instead built on top of libgda, the GNOME database abstraction layer. This enables Midgard to be used with various storage engines, including:

• MySQL
• Postgres
• SQLite
• Microsoft SQL Server
• Oracle
• DB2

Built-in replication and metadata

All Midgard objects are automatically equipped with a consistent set of metadata properties that can be used for access control and workflow.

In addition, Midgard provides an API for serializing and unserializing stored objects in XML format that can be used for replicating data between different systems. The replication architecture can be used for staging/live web environments or mobile applications that synchronize between each other or a web back-end.

Planned for next Midgard2 releases

• MidCOM, an elegant PHP MVC framework written for Midgard2
• Mono (C#) bindings

Midgard resources

• Download page and changelog for latest release
• Bug reporting

User and developers support:

• Users' forum
• Developers' forum
• IRC: #midgard on irc.freenode.net

About Midgard

The Midgard Framework development started in 1997 and it was initially released as free software in May 1999. Midgard Project has since gathered an active user and developer community, powering thousands of web sites ranging from simple organizational intranets to large community portals.

Midgard is being developed by an international team of professionals. Midgard's development team includes new media designers, system integrators and content management consultants. Midgard development has been supported by several commercial and governmental entities including the European Union and the Swedish Internet Foundation.

Midgard is free software available under the GNU LGPL license.

Contacts

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard spokesman
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org

About this release

Midgard2 9.03 is targeted at web framework and desktop developers. It provides a comprehensive set of content repository APIs that can be used to build replicated information applications that share their information using a common storage layer and replication tools.

Vinland series of Midgard2 is not intended to act as a content management system, and so no CMS tools are shipped with the release. Midgard2 Vinland however can be used to build a CMS, or to refactor existing CMS tools to work with a repository-centric model.

In this release we provide Content Repository API bindings for the following programming languages: C, Python, PHP and Objective-C. D-Bus signals are used to inform different Midgard2 applications about things happening in the repository, enabling for example a PHP website and a Python background process to communicate with each other.

Midgard2

Midgard2 is a content reporitory. It provides an object-oriented and replicated environment for building data-intensive applications.

Midgard's philosophy includes building on top of a well-known and supported GNOME libraries like glib and libgda on the system end, and connecting with popular programming languages like PHP and Python. Data storage can utilize SQLite with desktop and mobile applications, or a database server like MySQL or Postgres for web application storage.

The Midgard2 platform enables developers to define a storage structure once and use it on both web and desktop applications, with the possibility of easy data replication between the two.

Read more about Midgard's content repository approach:

• http://bergie.iki.fi/blog/midgard2_at_fscons-your_data-everywhere
• http://bergie.iki.fi/blog/midgard_and_jcr-a_look_at_two_content_repositories
• http://teroheikkinen.iki.fi/blog/midgard_workshop_at_fscons

New Midgard architecture

Language independence

Midgard is also language independent and due to its powerful architecture has proven as stable, secure and flexible solution implemented in various environments:

• PHP5 extension for web application and CMS development
• Python module for desktop application and background process development
• Mono module for desktop application and background process development in C#

Database independence

The Midgard 1.x was heavily coupled with the MySQL database. The new Midgard2 architecture is instead built on top of libgda, the GNOME database abstraction layer. This enables Midgard to be used with various storage engines, including:

• MySQL
• Postgres
• SQLite
• Microsoft SQL Server
• Oracle
• DB2

Built-in replication and metadata

All Midgard objects are automatically equipped with a consistent set of metadata properties that can be used for access control and workflow.

In addition, Midgard provides an API for serializing and unserializing stored objects in XML format that can be used for replicating data between different systems. The replication architecture can be used for staging/live web environments or mobile applications that synchronize between each other or a web back-end.

Planned for next Midgard2 releases

• MidCOM, an elegant PHP MVC framework written for Midgard2
• Mono (C#) bindings

Midgard resources

• Download page and changelog for latest release
• Bug reporting

User and developers support:

• Users' forum
• Developers' forum
• IRC: #midgard on irc.freenode.net

About Midgard

The Midgard Framework development started in 1997 and it was initially released as free software in May 1999. Midgard Project has since gathered an active user and developer community, powering thousands of web sites ranging from simple organizational intranets to large community portals.

Midgard is being developed by an international team of professionals. Midgard's development team includes new media designers, system integrators and content management consultants. Midgard development has been supported by several commercial and governmental entities including the European Union and the Swedish Internet Foundation.

Midgard is free software available under the GNU LGPL license.

Contacts

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard spokesman
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org

About this release

The second beta of Midgard2 9.03 is targeted at web framework and desktop developers. It provides a comprehensive set of content repository APIs that can be used to build replicated information applications that share their information using a common storage layer and replication tools.

Vinland series of Midgard2 is not intended to act as a content management system, and so no CMS tools are shipped with the release. Midgard2 Vinland however can be used to build a CMS, or to refactor existing CMS tools to work with a repository-centric model.

In this release we provide Content Repository API bindings for the following programming languages: C, Python, PHP. D-Bus signals are used to inform different Midgard2 applications about things happening in the repository, enabling for example a PHP website and a Python background process to communicate with each other.

Midgard2

Midgard2 is a content reporitory. It provides an object-oriented and replicated environment for building data-intensive applications.

Midgard's philosophy includes building on top of a well-known and supported GNOME libraries like glib and libgda on the system end, and connecting with popular programming languages like PHP and Python. Data storage can utilize SQLite with desktop and mobile applications, or a database server like MySQL or Postgres for web application storage.

The Midgard2 platform enables developers to define a storage structure once and use it on both web and desktop applications, with the possibility of easy data replication between the two.

Read more about Midgard's content repository approach:

• http://bergie.iki.fi/blog/midgard2_at_fscons-your_data-everywhere
• http://bergie.iki.fi/blog/midgard_and_jcr-a_look_at_two_content_repositories
• http://teroheikkinen.iki.fi/blog/midgard_workshop_at_fscons

New Midgard architecture

Language independence

Midgard is also language independent and due to its powerful architecture has proven as stable, secure and flexible solution implemented in various environments:

• PHP5 extension for web application and CMS development
• Python module for desktop application and background process development
• Mono module for desktop application and background process development in C#

Database independence

The Midgard 1.x was heavily coupled with the MySQL database. The new Midgard2 architecture is instead built on top of libgda, the GNOME database abstraction layer. This enables Midgard to be used with various storage engines, including:

• MySQL
• Postgres
• SQLite
• Microsoft SQL Server
• Oracle
• DB2

Built-in replication and metadata

All Midgard objects are automatically equipped with a consistent set of metadata properties that can be used for access control and workflow.

In addition, Midgard provides an API for serializing and unserializing stored objects in XML format that can be used for replicating data between different systems. The replication architecture can be used for staging/live web environments or mobile applications that synchronize between each other or a web back-end.

Planned for next Midgard2 releases

• MidCOM, an elegant PHP MVC framework written for Midgard2
• Objective-C bindings and native Mac packages
• Mono (C#) bindings

Midgard resources

• Download page and changelog for latest release
• Bug reporting

User and developers support:

• Users' forum
• Developers' forum
• IRC: #midgard on irc.freenode.net

About Midgard

The Midgard Framework development started in 1997 and it was initially released as free software in May 1999. Midgard Project has since gathered an active user and developer community, powering thousands of web sites ranging from simple organizational intranets to large community portals.

Midgard is being developed by an international team of professionals. Midgard's development team includes new media designers, system integrators and content management consultants. Midgard development has been supported by several commercial and governmental entities including the European Union and the Swedish Internet Foundation.

Midgard is free software available under the GNU LGPL license.

Contacts

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard spokesman
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org

The Midgard Project has finally released the first public version of Midgard Application Server Suite. The new release contains Midgard core libraries, a PHP3-based web application server for the Apache platform and the needed web-based administration tools.

May 8th 2009:

It's time for celebration - Midgard CMS turns ten in May! The decade of Midgard will be celebrated with a guest gala that is to be held at restaurant Ostrobotnia in Helsinki, Finland.

Looking forward to seeing as many of you in the party as possible! Please register ASAP as we need to tell the restaurant how many tables are needed.

• Midgard installer doesn't depend on pearified.com channel (#747)
• Memory corruption in midgard-php extension has been fixed (#804)
• Query Builder and Collector constructors has been improved (#556)
• Several crashes has been fixed (#712, #734, #801, #870)
• Internal PHP classes can be introspected by PHP Reflection (#479)
• midgard_cron has been improved (#813, #816)
• URL name handling and generation has been rewritten (#809)
• TinyMCE WYSIWYG editor has been upgraded to version 3.2.2
• Issues with handling multilingual content have been fixed (#870, #825, #935, #865, #910)
• Code editor in Asgard has been changed from CodePress to EditArea
• Configuration editor in Asgard now always creates valid configuration snippets (#771)
• MidCOM now uses only the modern Midgard2 API (#611)
• PAM authentication has been fixed (#750)
• Midgard now ships with SELinux policy files (#538)

About this release

The first beta of Midgard2 9.03 is targeted at web framework and desktop developers. It provides a comprehensive set of content repository APIs that can be used to build replicated information applications that share their information using a common storage layer and replication tools.

Vinland series of Midgard2 is not intended to act as a content management system, and so no CMS tools are shipped with the release. Midgard2 Vinland however can be used to build a CMS, or to refactor existing CMS tools to work with a repository-centric model.

In this release we provide Content Repository API bindings for the following programming languages: C, Python, PHP. D-Bus signals are used to inform different Midgard2 applications about things happening in the repository, enabling for example a PHP website and a Python background process to communicate with each other.

Midgard2

Midgard2 is a content reporitory. It provides an object-oriented and replicated environment for building data-intensive applications.

Midgard's philosophy includes building on top of a well-known and supported GNOME libraries like glib and libgda on the system end, and connecting with popular programming languages like PHP and Python. Data storage can utilize SQLite with desktop and mobile applications, or a database server like MySQL or Postgres for web application storage.

The Midgard2 platform enables developers to define a storage structure once and use it on both web and desktop applications, with the possibility of easy data replication between the two.

Read more about Midgard's content repository approach:

• http://bergie.iki.fi/blog/midgard2_at_fscons-your_data-everywhere
• http://bergie.iki.fi/blog/midgard_and_jcr-a_look_at_two_content_repositories
• http://teroheikkinen.iki.fi/blog/midgard_workshop_at_fscons

New Midgard architecture

Language independence

Midgard is also language independent and due to its powerful architecture has proven as stable, secure and flexible solution implemented in various environments:

• PHP5 extension for web application and CMS development
• Python module for desktop application and background process development
• Mono module for desktop application and background process development in C#

Database independence

The Midgard 1.x was heavily coupled with the MySQL database. The new Midgard2 architecture is instead built on top of libgda, the GNOME database abstraction layer. This enables Midgard to be used with various storage engines, including:

• MySQL
• Postgres
• SQLite
• Microsoft SQL Server
• Oracle
• DB2

Built-in replication and metadata

All Midgard objects are automatically equipped with a consistent set of metadata properties that can be used for access control and workflow.

In addition, Midgard provides an API for serializing and unserializing stored objects in XML format that can be used for replicating data between different systems. The replication architecture can be used for staging/live web environments or mobile applications that synchronize between each other or a web back-end.

Planned for next Midgard2 releases

• MidCOM, an elegant PHP MVC framework written for Midgard2
• Objective-C bindings and native Mac packages
• Mono (C#) bindings

Midgard resources

• Download page and changelog for latest release
• Bug reporting

User and developers support:

• Users' forum
• Developers' forum
• IRC: #midgard on irc.freenode.net

About Midgard

The Midgard Framework development started in 1997 and it was initially released as free software in May 1999. Midgard Project has since gathered an active user and developer community, powering thousands of web sites ranging from simple organizational intranets to large community portals.

Midgard is being developed by an international team of professionals. Midgard's development team includes new media designers, system integrators and content management consultants. Midgard development has been supported by several commercial and governmental entities including the European Union and the Swedish Internet Foundation.

Midgard is free software available under the GNU LGPL license.

Contacts

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard spokesman
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org

New package is available from download page.

Binary packages should be ready in next few hours.

• Role_Web: installing public files to server DocumentRoot, deprecated by PEAR's new www role
• Javascript_Prototype: the prototype javascript library used by some components
• Javascript_Scriptaculous: the Scriptaculous javascript library used by some components

Because of this, new installs of Midgard are temporarily unavailable. See bug #747 for more information.

The Midgard team is preparing a 8.09.3.1 maintenance release to resolve this issue as soon as possible. We apologize for the inconvenience.

Lodz, January 12th 2009 -- The Midgard Project has released the third
maintenance release of Midgard 8.09 Ragnaroek LTS.
Ragnaroek LTS is a Long Term Support version of the free software
content management framework.

The 8.09.3 "New Year's diet" release focuses on API and architecture cleanups
in order to ease transition from Midgard 1.x series API to Midgard 2.x APIs.

Stable 8.09.3 release is recommended for all users of Midgard.

Main changes from 8.09.2:

• MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599)
• There is a new online help and documentation viewer
• Safari user experience has been greatly improved (#583, #585)
• Basic authentication on Midgard level has been fixed (#485)
• MidCOM cron is now automatically set up for new virtual hosts (#378)
• All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477)
• Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564
• File attachments now have MultiLang emulation (#420)
• In-page Ajax editing can now be disabled and enabled globally (#526)
• Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625)
• HTTP errors can be mapped to notifications or special logging (#305)
• The Midgard PHP extension is now approximately 50% faster

In total 151 tickets have been closed for this release. See the Midgard issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.3+Ragnaroek

Planned for next maintenance release:

• More performance tuning
• Unit tests for midgard-php and MidCOM DBA layers
• New Midgard visual guidelines deployed more widely
• Filesync git integration for collaborative site development
• MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4+Ragnaroek&order=priority

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/

Changes from 8.09.3RC2:

• Fixed database tables' layout for initial setups
• Replication is faster objects which hold guid references
• Minor bugfixes

Main changes from 8.09.2:

• MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599)
• There is a new online help and documentation viewer
• Safari user experience has been greatly improved (#583, #585)
• Basic authentication on Midgard level has been fixed (#485)
• MidCOM cron is now automatically set up for new virtual hosts (#378)
• All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477)
• Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564
• File attachments now have MultiLang emulation (#420)
• In-page Ajax editing can now be disabled and enabled globally (#526)
• Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625)
• HTTP errors can be mapped to notifications or special logging (#305)
• The Midgard PHP extension is now approximately 50% faster

In total 145 tickets have been closed for this release. See the Midgard issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.3+Ragnaroek

Planned for next maintenance release:

• More performance tuning
• Unit tests for midgard-php and MidCOM DBA layers
• New Midgard visual guidelines deployed more widely
• Filesync git integration for collaborative site development
• MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4+Ragnaroek&order=priority

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/

This release includes several major - backward compatible - improvements and fixes.

Main changes from 8.09.2:

• MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599)
• There is a new online help and documentation viewer
• Safari user experience has been greatly improved (#583, #585)
• Basic authentication on Midgard level has been fixed (#485)
• MidCOM cron is now automatically set up for new virtual hosts (#378)
• All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477)
• Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564
• File attachments now have MultiLang emulation (#420)
• In-page Ajax editing can now be disabled and enabled globally (#526)
• Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625)
• HTTP errors can be mapped to notifications or special logging (#305)
• The Midgard PHP extension is now approximately 50% faster

In total 130 tickets have been closed for this release. See the Midgard issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.3+Ragnaroek

Planned for next maintenance release:

• More performance tuning
• Unit tests for midgard-php and MidCOM DBA layers
• New Midgard visual guidelines deployed more widely
• Filesync git integration for collaborative site development
• MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4+Ragnaroek&order=priority

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/

• MidCOM DBA has been rewritten to follow decorator pattern instead of inheritance (#456 and #599)
• There is a new online help and documentation viewer
• Safari user experience has been greatly improved (#583, #585)
• Basic authentication on Midgard level has been fixed (#485)
• MidCOM cron is now automatically set up for new virtual hosts (#378)
• All legacy metadata fields have been removed in favor of midgard_metadata object (#387, #464, #476 and #477)
• Replication has been changed to work using the new API and decorators (#627, #607, #534, #501, 513, #564
• File attachments now have MultiLang emulation (#420)
• In-page Ajax editing can now be disabled and enabled globally (#526)
• Midgard's tree management has been improved in many ways (#447, #482, #483, #600, #602, #625)
• HTTP errors can be mapped to notifications or special logging (#305)
• The Midgard PHP extension is now approximately 50% faster

In total 130 tickets have been closed for this release. See the Midgard issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.3+Ragnaroek

Planned for next maintenance release:

• More performance tuning
• Unit tests for midgard-php and MidCOM DBA layers
• New Midgard visual guidelines deployed more widely
• Filesync git integration for collaborative site development
• MidCOM packages distributed by a Midgard-powered PEAR channel

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&status=closed&milestone=8.09.4+Ragnaroek&order=priority

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/

The repository is now organized in the following way:

• trunk: The next generation of Midgard that is currently under development, at the moment 9.03 Vinland
• branches/ragnaroek: Midgard 8.09 Ragnaroek LTS
• branches/thor: Midgard 1.8 and MidCOM 2.8
• branches/loki: Midgard 1.7 and MidCOM 2.6
• branches/classic: Midgard 1.6 and MidCOM 2.4

Under each of these there are two subdirectories:

• midgard: Midgard core and language bindings
• midcom: The Midgard components framework

The policy on working with Midgard sources is that each generation branch, and Midgard trunk should be kept stable. To make larger changes possible, it is recommended that developers utilize git-svn and feature branches for their work.

To make a local git checkout of Midgard's SVN repository, use the following command:

git svn clone https://svn.midgard-project.org/midgard/ -T trunk -b branches -t tags

For working with Git, there are some useful tutorials:

• Git SVN crash course
• How to track multiple SVN branches in git
• Feature branches in Midgard development with git

Commit access to the repository can be requested from the VCS Tyrant Eero af Heurlin, who also monitors all commits. The same username and password as used on this site is applicable with Midgard SVN.

• MySQL errors when upgrading old databases have been fixed (#355)
• SQL queries generated by MidCOM's DBA layer have been optimized (#412)
• Midgard now sets up a standalone Asgard administrative interface for
• all new site setups (#36 and #329)
• MidCOM has a new handler for catching PHP Exceptions (#352)
• MidCOM DBA is bypassed for configuration and element loading (#414 and #415)
• Midgard Collector is now able to query metadata properties (#417)
• MultiLang support has been improved with index articles and
• attachments (#288 and #420)
• Debian and Ubuntu packages now automatically install memcached and
• SOLR (#380 and #381)
• Datagard upgrade from 1.8 now installs same MidCOM packages to
• Ragnaroek (#363)
• Swedish translations are now included

In total 98 tickets have been closed for this release. See the Midgard
issue tracker for a full list:
http://trac.midgard-project.org/query?status=closed&milestone=8.09.2+Ragnaroek

Planned for next maintenance release:

• More performance tuning
• Changing MidCOM DBA from subclasses to decorators
• Unit tests for midgard-php and MidCOM DBA layers
• New Midgard visual guidelines deployed more widely
• Filesync git integration for collaborative site development

See the full list in:
http://trac.midgard-project.org/query?status=new&status=assigned&status=reopened&milestone=8.09.3+Ragnaroek

Source downloads

http://www.midgard-project.org/download/

Binary packages

http://download.opensuse.org/repositories/home:/midgardproject:/ragnaroek/

Getting started

http://www.midgard-project.org/documentation/getting-started/

Issue tracker

http://trac.midgard-project.org/roadmap

More information

Piotr Pokora, Midgard release manager
piotrek.pokora(at)gmail.com

Henri Bergius, Midgard bug master
henri.bergius(at)iki.fi

The Midgard Project
http://www.midgard-project.org/

WHAT IF you knew that the next long-term supported releases of Ubuntu, Debian, Red Hat and Novell Linux would all have the same major versions of kernel, GCC, X, GNOME, KDE, OO.o and Mozilla. Would that make a major difference for you? I’m willing to bet not - that from a customer view, folks who prefer X will still prefer X. A person who prefers Red Hat will stick with Red Hat. But from a developer view, would that make it easier to collaborate? Dramatically so.

Another member of the audience came up to talk about the fashion industry. That’s also converged on a highly coordinated model - fabrics and technologies “release” first, then designers introduce their work simultaneously at fashion shows around the world. “Spring 2009″ sees new collections from all the major houses, many re-using similar ideas or components. That hasn’t hurt their industry, rather it helps to build awareness amongst the potential audience.

The same model has been employed very successfully by major projects like GNOME, Eclipse and the Ubuntu distribution. As Midgard relies on many GNOME technologies, being in the same release cycle with them helps our development immensely, and makes Midgard more easy to install because we have a more stable set of dependencies.

This coming weekend Midgard developers will convene in Otaniemi, Espoo, Finland to discuss the plans for the next release, 9.03 "Vinland", the first release to be fully legacy free.

The Coccinella IM project which also utilizes the synchronized release model has posted a list of release synchronicity myths and facts.

New hotfix packages for Midgard 1.8.9 (generation "Thor") has been released today.

midgard-core package includes fix for memory corruption which was randomly, triggered by midgard_replicator.

midgard-php includes small (but very important) fix for integer values being set as unsigned integers. Metadata score property seem to be most affected by this bug.

Both packages are available at download page.

Binary packages are also available.
(Please try later, if packages files are not yet updated)