Calendar:Release Notes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Prepare the release notes draft for 0.3 alpha2)
Line 4: Line 4:


===Goals of the 0.3 alpha2 Release===
===Goals of the 0.3 alpha2 Release===
Sunbird 0.3 alpha2 is not intended to be a production-quality release. (See "Limitations and Known Bugs". Instead, it is being released largely in order to showcase/test the new backend code and the advanced new view code. This includes:
Sunbird 0.3 alpha2 is not intended to be a production-quality release. (See "Limitations and Known Bugs". Instead, it is being released largely in order to showcase/test the advanced new view code. This includes:
*...
*Inline editing of event titles
*...
*Restoration of drag and drop editing in the day/week views


It is hoped that the release of Sunbird 0.3 alpha2 will draw a wider audience of testers that can more fully identify any bugs or problems in this backend codeThose wishing to perform more rigorous testing can use the [[Calendar:Tests]] page as a guide. Other goals of the release include:
In addition to showcasing and testing the new views, Sunbird 0.3a2 aims to provide users of Sunbird 0.3a1 with a new release that contains a large number of bug fixes for many of the issues identified in that releaseThis includes:
 
*Ability to modify individual elements of a recurring event
*...
*Fewer import/export errors
*...
*Better error reporting
*Improved alarm functionality
*A new, more intuitive New Event dialog.


===Limitations and Known Bugs===
===Limitations and Known Bugs===
Before using Sunbird 0.3 alpha2, it is '''strongly''' encouraged that you read the following limitations that the release possesses.
Before using Sunbird 0.3 alpha2, it is '''strongly''' encouraged that you read the following limitations that the release possesses.


*...
*'''Dataloss may occur if you attempt to use Sunbird with calendar files created by other calendaring programs.'''
*...
*Undo/Redo abilities may not be available for all types of modifications
 
*Printing support remains minimal. However, extension authors now have the ability to easily add additional print options
Minor:
*CalDAV support remains extremely basic
*...
*Shutting down Sunbird immediately after a change has been made (within 5 seconds) may result in the change not being recorded.
*Sunbird 0.3a2 does not work for dates before 1970 or after 2031
*Snooze functionality is not currently present.


===The Next Step===
===The Next Step===
The next step in the development process of Sunbird/Calendar is to implement...
The current roadmap for Sunbird development lists this release as the last alpha release on the way to Sunbird 0.3.  The next planned release of Sunbird is planned to be Sunbird 0.3 beta-1, which only has the goal of fixing bugs identified in this release, in an effort towards creating a final, production quality release.  While new features are not directly planned for Sunbird 0.3b, ongoing parallel development of Lightning 0.2 may result in additional features being implemented in this next release as well.


Users wishing to follow the implementations of these features should feel free to download nightly builds. As always, testing and good bug reports are always greatly appreciated.
Users wishing to follow the progress towards this beta release should feel free to download nightly builds. As always, testing and good bug reports are always greatly appreciated.

Revision as of 16:44, 18 March 2006

Sunbird 0.3 alpha2 Release Notes (Draft)

On [DAY] [MONTH] 2006, the Sunbird/Calendar project released Sunbird 0.3 alpha2. This marks the second official release Sunbird since the lengthy task of rewriting the backend code was undertaken. Sunbird 0.3 alpha2 marks the second milestone on the roadmap towards a final Sunbird 0.3. These release notes are intended to provide a clear picture of what users should and should not expect in this version.

Goals of the 0.3 alpha2 Release

Sunbird 0.3 alpha2 is not intended to be a production-quality release. (See "Limitations and Known Bugs". Instead, it is being released largely in order to showcase/test the advanced new view code. This includes:

  • Inline editing of event titles
  • Restoration of drag and drop editing in the day/week views

In addition to showcasing and testing the new views, Sunbird 0.3a2 aims to provide users of Sunbird 0.3a1 with a new release that contains a large number of bug fixes for many of the issues identified in that release. This includes:

  • Ability to modify individual elements of a recurring event
  • Fewer import/export errors
  • Better error reporting
  • Improved alarm functionality
  • A new, more intuitive New Event dialog.

Limitations and Known Bugs

Before using Sunbird 0.3 alpha2, it is strongly encouraged that you read the following limitations that the release possesses.

  • Dataloss may occur if you attempt to use Sunbird with calendar files created by other calendaring programs.
  • Undo/Redo abilities may not be available for all types of modifications
  • Printing support remains minimal. However, extension authors now have the ability to easily add additional print options
  • CalDAV support remains extremely basic
  • Shutting down Sunbird immediately after a change has been made (within 5 seconds) may result in the change not being recorded.
  • Sunbird 0.3a2 does not work for dates before 1970 or after 2031
  • Snooze functionality is not currently present.

The Next Step

The current roadmap for Sunbird development lists this release as the last alpha release on the way to Sunbird 0.3. The next planned release of Sunbird is planned to be Sunbird 0.3 beta-1, which only has the goal of fixing bugs identified in this release, in an effort towards creating a final, production quality release. While new features are not directly planned for Sunbird 0.3b, ongoing parallel development of Lightning 0.2 may result in additional features being implemented in this next release as well.

Users wishing to follow the progress towards this beta release should feel free to download nightly builds. As always, testing and good bug reports are always greatly appreciated.