Difference between revisions of "OJS Roadmap"

From PKP Wiki
Jump to: navigation, search
(Development Roadmap)
(41 intermediate revisions by 5 users not shown)
Line 1: Line 1:
;[[OJS Roadmap]]
+
=History=
:Future directions for OJS
+
[[image:OJS_Release_History.png|thumb|OJS Release History]]
  
;Less linear workflow
+
=Development Roadmap=
:Status: TBA
+
:Less downloading and uploading req'd for workflow
+
:Possibility of using a single file for all workflow and tracking changes rather than submitting new files for each stage (perhaps with drag and drop, with copies left behind for documentation)
+
  
;Better support for pre-prints
+
You will find the OJS development roadmap for 2012 below. Please note that these dates are not fixed. OJS development is currently following three development branches: a 'stable' 2.3.x line which includes mainly bugfixes and will be an easy, painless upgrade for existing users of the current release (and who do not need much in the way of new features); a 'development' 2.4 line, which will become the next stable branch; and the 'master' git repository, which includes large-scale changes in the underlying codebase as well as many new features, and is not yet released for production use.  
:Status: TBA
+
:"In press" section for articles that are currently in holding for actual publication.
+
  
;Thesis Workflow Tool
+
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 Conference Systems. You are encouraged to browse [http://pkp.sfu.ca/bugzilla our Bugzilla database] fully. Bug entries are typically filed against the version in which the new code is expected to be released.
:Status: TBA
+
:OJS as a thesis submission and tracking system.
+
:SFU Library has a project on the books to develop a more robust thesis workflow tool.
+
  
;Submission as single file
+
==Milestone 2.3.x ('''Ad-hoc scheduling''')==
:Status: TBA
+
:Submission model might be made better by including the option to make a .pdf containing the article, all supplementary files and appropriate metadata. Advantages include no need to de-identify properties, and review document is a single document - no need to download all figures, supplementary documents, etc in order to review.  Of course, letter to editor and other documents not for reviewers would need to be submitted not to be included.
+
  
;Miscellaneous
+
Releases of OJS in the 2.3.x line will be made when necessary (e.g. based on security issues) or when desired (e.g. when enough minor fixes accumulate that the community will find them broadly useful). These releases are very limited in change scope to keep the testing and release processes to a minimum; for example, no translation updates are allowed for 2.3.x releases. The most important changes in each 2.3.x release are posted on the [http://pkp.sfu.ca/wiki/index.php/OJS_Recommended_Patches Recommended Patches] page.
:Status: TBA
+
 
:import transaction/rollback
+
==Milestone 2.4 ('''Q3 2012''')==
:more flexible statistics
+
 
:arbitrary metadata gateway
+
This release will include large-scale revamping of the PKP codebase, including the further  abstraction of common code from all applications into the PKP WAL that began with the 2.3.0 line of releases; modularization of the remaining OJS codebase (so that components can be better mixed and matched in each application); and further overall code refinements. This release will set the stage for large-scale porting of OMP functionality (user interface improvements; flexible roles; etc.) in the subsequent 3.0 release.
:Dspace export
+
 
:user/article thesaurus/controlled vocabulary
+
 
:user tagging
+
==Milestone 3.0 ('''Not yet scheduled''')==
:ACL:based permission classes
+
 
:WYSIWYG special character handling (e.g., tinyMCE extension for latek)
+
This proposed release will be the first release to include user interface and software design backporting from the initial release of OMP. Much of the new functionality used by OMP is already in the shared PKP WAL, but there are numerous parts of that framework not yet used by OJS, such as the JavaScript framework.
:"login as" behavior should be limited in certain contexts
+
 
:centralized role management for plugins
+
* See [http://pkp.sfu.ca/node/1600 Modularization of PKP Systems] for details on the proposed modularization of PKP applications.
:featured article plugin/block
+
:user friendly error handling/logging
+
:local private messaging system a la phpBB
+

Revision as of 09:40, 4 October 2012

History

OJS Release History

Development Roadmap

You will find the OJS development roadmap for 2012 below. Please note that these dates are not fixed. OJS development is currently following three development branches: a 'stable' 2.3.x line which includes mainly bugfixes and will be an easy, painless upgrade for existing users of the current release (and who do not need much in the way of new features); a 'development' 2.4 line, which will become the next stable branch; and the 'master' git repository, which includes large-scale changes in the underlying codebase as well as many new features, and is not yet released 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 Conference Systems. You are encouraged to browse our Bugzilla database fully. Bug entries are typically filed against the version in which the new code is expected to be released.

Milestone 2.3.x (Ad-hoc scheduling)

Releases of OJS in the 2.3.x line will be made when necessary (e.g. based on security issues) or when desired (e.g. when enough minor fixes accumulate that the community will find them broadly useful). These releases are very limited in change scope to keep the testing and release processes to a minimum; for example, no translation updates are allowed for 2.3.x releases. The most important changes in each 2.3.x release are posted on the Recommended Patches page.

Milestone 2.4 (Q3 2012)

This release will include large-scale revamping of the PKP codebase, including the further abstraction of common code from all applications into the PKP WAL that began with the 2.3.0 line of releases; modularization of the remaining OJS codebase (so that components can be better mixed and matched in each application); and further overall code refinements. This release will set the stage for large-scale porting of OMP functionality (user interface improvements; flexible roles; etc.) in the subsequent 3.0 release.


Milestone 3.0 (Not yet scheduled)

This proposed release will be the first release to include user interface and software design backporting from the initial release of OMP. Much of the new functionality used by OMP is already in the shared PKP WAL, but there are numerous parts of that framework not yet used by OJS, such as the JavaScript framework.