You will find the OCS development roadmap for 2012 below. Please note that these dates are not fixed. OCS development is currently following two development branches: a 'stable' 2.3.x line which includes mainly bugfixes and will be an easy upgrade; and a 'master' 2.4 line, which includes large-scale changes in the underlying codebase as well as many new features, but is not yet ready for production use.

−

'''<big>PKP Framework</big>'''

+

While we do attempt to list all bugs tracked against a given release, quite often a bug report against one release will be ported to another (this is especially the case with 2.3.x bugfixes into the master branch; less so with 2.4 enhancements into the stable branch). This is also the case with some bugs tracked against other applications such as Open Journal Systems. You are encouraged to browse [http://pkp.sfu.ca/bugzilla our Bugzilla database] fully.

−

* Development of a common framework for all PKP software.

+

−

* See [http://pkp.sfu.ca/node/1600 Modularization of PKP Systems] for details.

As with [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_2.3.x_.28Ad-hoc_scheduling.29 OJS 2.3.x], OCS 2.3.x releases will be made as necessary to correct security issues or as sufficient minor fixes accumulate to make a release worthwhile.

PKP currently intends to consider release plans for OCS 2.4 from the master branch after the same has been completed for OJS 2.4. See [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_2.4_.28Q3_2012.29 OJS Milestone 2.4] for details. It is possible that PKP will opt to jump directly to considering OCS 3.0, described below.

+

+

==Milestone 3.0 ('''Not yet scheduled''')==

+

+

OJS 3.0, described [http://pkp.sfu.ca/wiki/index.php/OJS_Roadmap#Milestone_3.0_.28Not_yet_scheduled.29 here], will reconcile the departure in coding style pioneered by OMP by bringing OJS back into line, incorporating new UI tools and back-end structures. Broadly speaking this will be a priority for OCS as well, though timelines and plans for OCS are currently less defined. Much of this work will attempt to blur the distinctions between the different applications, further decreasing the amount of distinct code per application and introducing greater flexibility in workflow within each application.

+

+

* See [http://pkp.sfu.ca/node/1600 Modularization of PKP Systems] for details on the proposed modularization of PKP applications.

Revision as of 16:58, 19 April 2012

Contents

Development Roadmap

You will find the OCS development roadmap for 2012 below. Please note that these dates are not fixed. OCS development is currently following two development branches: a 'stable' 2.3.x line which includes mainly bugfixes and will be an easy upgrade; and a 'master' 2.4 line, which includes large-scale changes in the underlying codebase as well as many new features, but is not yet ready for production use.

While we do attempt to list all bugs tracked against a given release, quite often a bug report against one release will be ported to another (this is especially the case with 2.3.x bugfixes into the master branch; less so with 2.4 enhancements into the stable branch). This is also the case with some bugs tracked against other applications such as Open Journal Systems. You are encouraged to browse our Bugzilla database fully.

Milestone 2.3.x (Ad-hoc scheduling)

As with OJS 2.3.x, OCS 2.3.x releases will be made as necessary to correct security issues or as sufficient minor fixes accumulate to make a release worthwhile.

Milestone 2.4 (Not yet scheduled)

PKP currently intends to consider release plans for OCS 2.4 from the master branch after the same has been completed for OJS 2.4. See OJS Milestone 2.4 for details. It is possible that PKP will opt to jump directly to considering OCS 3.0, described below.

Milestone 3.0 (Not yet scheduled)

OJS 3.0, described here, will reconcile the departure in coding style pioneered by OMP by bringing OJS back into line, incorporating new UI tools and back-end structures. Broadly speaking this will be a priority for OCS as well, though timelines and plans for OCS are currently less defined. Much of this work will attempt to blur the distinctions between the different applications, further decreasing the amount of distinct code per application and introducing greater flexibility in workflow within each application.