You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 42
Next »
Sakai 2.5.3
Event |
Date |
Comment |
Freeze |
|
Create 2.5.3 release branch, based on 2.5.2 release and 2.5.x maintenance branch. |
QA |
|
QA will be focused on regression testing of components affected by bug fixes included in the release. |
2.5.3-rc01 |
19-Aug-2008 |
First release candidate. |
2.5.3-rc02 |
28-Aug-2008 |
First release candidate. |
2.5.3-rc03 |
03-Sep-2008 |
First release candidate. |
Release |
|
Official release of Sakai 2.5.3. |
Release Content
Note that not all bug fixes in the 2.5.x Maintenance Branch are necessarily going to be included in the 2.5.3 Maintenance Release. 2.5.3 includes all the bug fixes from previous 2.5 Maintenance Releases plus fixes for a selected subset of components (see below). This will help us reduce the scope of component regression testing in order to speed up the frequency of Maintenance Releases. Fixes for components available in 2.5.x, but not included in 2.5.3, will be included in a subsequent Maintenance Release.
The preliminary list of components for which fixes will be included in Sakai 2.5.3:
Assignments
SAK-13789
-
Getting issue details...
STATUS
(Link only works for those with permission to view security-related issues.)
SAK-13551
-
Getting issue details...
STATUS
(Link only works for those with permission to view security-related issues.) - needs to be tested and merged
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Content-Review (request of AZ)
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Entity Broker
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Discussion (legacy)
Note this needs to be tested & merged
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Messages
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Portal/Database
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
rWiki
SAK-14076
-
Getting issue details...
STATUS
(Link only works for those with permission to view security-related issues.)
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Misc Security - Link only works for those with permission to view security-related issues.
Worksite Setup / Site Setup
SAK-13958
-
Getting issue details...
STATUS
Blogger
SAK-13955
-
Getting issue details...
STATUS
Tests & Surveys - Needs testing and merging
SAK-13930
-
Getting issue details...
STATUS
Jira Filters
- Sakai 2.5.3 Fixes (
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
)
- Sakai 2.5.3 Known Issues (
type |
key |
summary |
assignee |
reporter |
priority |
status |
resolution |
created |
updated |
due |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
)
2.5.3 QA
Draft