wiki:UNPLANNED_FEATURE_SCHEDULE_REVIEW_R0

Version 15 (modified by pap, 16 years ago) (diff)

--

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=UNPLANNED_FEATURE_SCHEDULE_REVIEW_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

The RELEASE_SCHEDULE needs to be reviewed by the team.

Task requirements

  1. Each team member should read the release schedule. It can be found RELEASE_SCHEDULE.
  2. Each team member should submit their input as a comment on this wiki page (see link at top of this page)

Task result

The result of this task is a Release Schedule that has taken into account the comments made during this review.

Implementation idea

I think the best way to collect comments would be in the comments of the ticket. Those comments can then be copied to this wiki page.

How to demo

Show the comments on this page

Design

  • This is the schedule that the customer will use to evaluate our productivity.
  • Each reviewer should feel comfortable with these dates.
  • Do not feel as though you need to make comments just for making comments sake.
  • Please only give constructive feedback if you feel there is an fatal error in the schedule.
  • Remember that the dates are approximately 5 weeks after the sprint date, to allow for testing.
    • The exception is the last few releases, which have closer release times
  • Leave your comments in the comments section below in the form:
    • <USERID> - <COMMENT>

Implementation

(Implementation results should be described and linked here (from the wiki or the repository))

Testing

N/A

Comments

boyan - Weekends may not be suitable for releasing. 2008-02-15 and 2008-03-15 are Sundays and maybe it is a good idea to shift the release date by one day. 2008-08-15 is Saturday and should probably also be shifted.

alex -

  • Maybe Release 4 has too many features included. And would be better if some of them can be postponed for release 5. For example PDF export sounds pretty complicated.
  • Betas and Alphas should have better explanations of what is expected of them. And exactly which features are expected to work as they should.

pav -

  • There are only basic features mentioned for Sophie server in release 2 and 3. I suppose this means that there is no defined date for the other server features and it just should be ready in the final release?
  • There is no features listed for the Reader Sophie Edition also.
  • More constructive: In my point of view we will have more functionallity in the releases and should be good if there are more of them listed. Of course the schedule should be balanced and there is no need to list everything but at least the new to Sophie and some server and reader features should be in the plan.

pap -

  • we could add plugin support for Release 1
  • the availability of different editions could be mentioned, Perhaps Autror/Server for Release 1, Reader for Release 2
  • I think it is better to schedule halos and huds for Relase 2. The same is also possible for menus.
  • dialogs could go in Release 1