Ticket #612 (closed planned_task: obsolete)

Opened 14 years ago

Last modified 13 years ago


Reported by: Astea Owned by: niki
Priority: 3 Milestone: M03_PRE3
Component: BOOK_MANAGING Version: 2.0
Keywords: Cc:
Category: MAIN Effort: 1
Importance: 20 Ticket_group:
Estimated Number of Hours: Add Hours to Ticket:
Billable?: Total Hours:
Analysis_owners: niki Design_owners:
Imp._owners: Test_owners:
Analysis_reviewers: gogov Changelog:
Design_reviewers: Imp._reviewers:
Test_reviewers: Analysis_score: 2
Design_score: 0 Imp._score: 0
Test_score: 0


wiki page: BOOK_FILE_OPERATIONS_R0 - effort: 1d

Change History

comment:1 Changed 14 years ago by Tanya

  • Category set to MAIN
  • Design_score set to 0
  • Imp._score set to 0
  • Test_score set to 0
  • Analysis_score set to 0

comment:2 Changed 14 years ago by Tanya

  • Importance changed from 0 to 20

comment:3 Changed 14 years ago by niki

  • Owner changed from Astea to niki
  • Status changed from new to s1a_analysis_started


comment:4 Changed 14 years ago by niki

  • Status changed from s1a_analysis_started to s1b_analysis_finished
  • Analysis_owners set to niki

comment:5 Changed 14 years ago by gogov

  • Status changed from s1b_analysis_finished to new
  • Analysis_reviewers set to gogov
  • Analysis_score changed from 0 to 2
  • The goal of this task isn't to create, save and open book files but to describe how should these operations be implemented in Sophie 2, as well as providing info on detailed versions of them such as "Save as", for instance. Also maybe other operations should be available and it could be considered in the analysis.
  • The Task requirements section contains just a list of operations with no details provided on what has to happen. At least to aspects could be covered -- functionality from implementation point of view as well as the end-user point of view, e.g. what operations should be implemented internally and what the user gets as UI options. Also, in every other analysis you've done, you use awkward indentation and some weird "EXTRA" notion. The idea is to write stuff in a standard way, (see PLATFORM_STANDARDS_GENERAL and related to see how things should be done), but not in some weird way.
  • Result of this task shouldn't be just code but also some more detailed design in the wiki.
  • Related problems and tasks should be expanded -- besides the one you've listed, you should note tasks related with the book format for instance, etc.

comment:6 Changed 13 years ago by deyan

  • Status changed from new to closed
  • Resolution set to obsolete

Batch update from file query-obsoleted.csv

Note: See TracTickets for help on using tickets.