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.

Related

• UNPLANNED_FEATURE_SCHEDULE_R0
• UNPLANNED_FEATURE_SCHEDULE_DELIVERY_R0

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

We discussed all of the comments and integrated some changes during a team meeting.

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

gogov:

General:

• lots of tasks are listed with a prototype phase but don't contain medium or finishing phases so further planning is needed to include finishing or even medium development phases for certain feature sets.
• there could be some sort of listing the level of completeness of different categories of features in the Alpha phases.

There is some outline provided now but it'd be better if more details are included to underline the priorities of completing different categories in time.

• in general the list is too short in details which might lead to lots of extra questions and planning at a later phase.

The following are a few more specific things I noticed and listed in order to get a discussion going on if such details are to be included in this list or not. I've got lots of other specific comments like these but if not needed there's no sense in listing them here.

Release 2:

• more menu support -- this section should be more specific

Release 3:

• Community Web Site -- it'd be better if this is included in Release 2, so more people can get involved earlier in the Sophie project in general

Release 4:

• page zooming & frame rotating -- these tasks should be included as subtasks in a more general scene management task, and this task should be broken in different phases.
• application help -- should be updated more frequently so users of earlier versions have some documentation available

Release 5:

• adding to the comments listed in the Release 6 notes, timelines should definitely have more detailed breakdown, since the task of completing them is quite complex and reuires much effort.
• page element grouping -- this seems related to Release 2 "Prototype for selecting multiple page objects", so it could be brought earlier in time so the two tasks are closer.

milo -

• General:
  • We should add the corresponding milestones (at least on the wiki page), because developers will get confused, since Release 1 corresponds to M02_PRE2 (and so on).
  • I think that it is ok not to define lots of things, but it is important for our clients to see all the major features they expect.
• Release 1:
  • "Can be run on the Macintosh with script changes" - should be changed to "Can be run on the Macintosh with configuaration tweaking" or something
  • On the community site we may add "mail lists, discussion forum, developers wiki". Documentation page is ambigious and should be written in another way.
• Release 2:
  • While on the heading it says prototypical, some of the features are also marked as prototypical, while others are not. We should either remove the protypical word from these, or add it to the all.
  • Plugin support may be added. (we already have it)
• Release 3:
  • The resource changes are not only part of the server. To the application, there will be added functionalities to list and manipulate resources.
  • The prototype of the book's desktop is a significant feature and we may add it.
• Release 4:
  • "Developers skin" is not an apropriate name. If we dont want to use "hackers" we should use "Alternative skin".

deyan -

• What is meant by documentation page?
• Using "Prototype" word is not correct.

peko -

• Release 1 -2008-12-15
  • Sophie Properties - Should think whether internal things are going to be included.
  • Suggestion: - divide the list into sections for internal things and non-internal things, so that people do not get confused.

• Release 2 - 2009-02-13
  • More menu support - should be more specific. Explain which menus (for example File Menu, Insert Menu etc.) are going to be implemented on releases.

• Release 3 - 2009-03-15
  • In comparison to Release 2, this release has very little things to add. In my opinion some things from the Release 2 should go in Release 3 so that things are more balanced.

• Release 4 - 2009-04-15
  • Status Bar - What should this one exactly show since we had not decided whether we will have this one yet.

• Release 5 - 2009-05-15
  • Timelines - what exaclty.

• In my opinion things should be explained further. "Timelines" does not provide enough information while "Prototypes for page object alignment" does.