Ticket #1695 (closed unplanned_task: obsolete)

Opened 10 years ago

Last modified 10 years ago

GROUP_TEMPLATES_R1

Reported by: jani Owned by: jani
Priority: major Milestone: M08_ALPHA3
Component: BASE_BOOK_MODEL Version: 2.0
Keywords: Cc: jani, pav
Category: BASE Effort:
Importance: Ticket_group:
Estimated Number of Hours: Add Hours to Ticket:
Billable?: Total Hours:
Analysis_owners: jani, jani Design_owners: jani, jani
Imp._owners: jani Test_owners:
Analysis_reviewers: pav, meddle Changelog:
Design_reviewers: meddle, meddle Imp._reviewers: meddle
Test_reviewers: Analysis_score: 3.5
Design_score: 3.5 Imp._score: 3
Test_score: 0

Change History

comment:1 Changed 10 years ago by jani

  • Status changed from new to s1a_analysis_started
  • Analysis_owners set to jani

comment:2 Changed 10 years ago by jani

  • Description modified (diff)

comment:3 Changed 10 years ago by jani

  • Status changed from s1a_analysis_started to s1b_analysis_finished

Same analysis as R0.

comment:4 Changed 10 years ago by pav

  • Status changed from s1b_analysis_finished to s1c_analysis_ok
  • Analysis_reviewers set to pav
  • Analysis_score changed from 0 to 4

You could mention why the analysis is the same, because I was wondering at first.

comment:5 Changed 10 years ago by jani

  • Status changed from s1c_analysis_ok to s2a_design_started

comment:6 Changed 10 years ago by jani

  • Design_owners set to jani

comment:7 Changed 10 years ago by jani

  • Status changed from s2a_design_started to s2b_design_finished

comment:8 Changed 10 years ago by meddle

  • Cc jani, pav added
  • Design_score changed from 0 to 2
  • Design_reviewers set to meddle
  • Status changed from s2b_design_finished to new
  • Analysis_score changed from 4 to 2

I will fail this task to the start, because the analysis didn't go through the integrators' team. I have the following notes:

  • Analysis notes:
    • The analysis requirements for every revision are different and the design is done according to them.
    • The implementation idea is for the current revision requirements.
    • Use the analysis guy from you team to help you with the user point of view stuff, like what is the number of halos, huds needed, what will be the use of a palette, etc...
      • If the analysis guy from your team is not available use other one, may be from the integrators' team.
    • Think of the real related task for that revision, for example we seek simplicity for the templates because, we want to persist and copy them easy...
  • Design notes:
    • For the new logic/functionality you need new test that you have to provide with the design.
    • Think of a new demo/visual tests, even system tests.
    • Explain the new logic with the mutables and the templating with more examples, because that is the most important thing for that task.
    • Add the halo icons you will use for the visual part of the task.

2p (90m)

comment:9 Changed 10 years ago by jani

  • Status changed from new to s1a_analysis_started
  • Analysis_owners changed from jani to jani, jani

comment:10 Changed 10 years ago by jani

  • Status changed from s1a_analysis_started to s1b_analysis_finished

comment:11 Changed 10 years ago by meddle

  • Status changed from s1b_analysis_finished to s1c_analysis_ok
  • Analysis_reviewers changed from pav to pav, meddle
  • Analysis_score changed from 2 to 3.5

I think that now the analysis is more accurate, because it gives us the idea what are the problems from the revision one. I think that the visual part of the templates must be discussed with the analysators and in the next revision to have some visual ideas in the analysis.

3.5p (10m)

comment:12 Changed 10 years ago by jani

  • Design_owners changed from jani to jani, jani
  • Status changed from s1c_analysis_ok to s2a_design_started

comment:13 Changed 10 years ago by jani

  • Status changed from s2a_design_started to s2b_design_finished

comment:14 Changed 10 years ago by meddle

  • Status changed from s2b_design_finished to s2c_design_ok
  • Design_score changed from 2 to 3.5

I'm passing the design. Its clear and simple to me, I like the examples, in future please add the model and the tests as a revision to the design.

comment:15 Changed 10 years ago by jani

  • Status changed from s2c_design_ok to s3a_implementation_started
  • Design_reviewers changed from meddle to meddle, meddle
  • Imp._owners set to jani

comment:16 Changed 10 years ago by jani

  • Status changed from s3a_implementation_started to s3b_implementation_finished

comment:17 Changed 10 years ago by meddle

  • Status changed from s3b_implementation_finished to s3c_implementation_ok
  • Imp._score changed from 0 to 3
  • Imp._reviewers set to meddle

I'm passing it.

  • There is one problem with the useTemplate behavior that have to be discussed with the analizators for the next revision. That is when you are changing for example the width of a templated frame, the field is locked, until you manually remove the useTemplate.
  • This behavior with the resources must be fixed in the next revision!
  • There was no JavaDoc on the TemplateSupport class, I added something but you will have to write the right one...

3p (90m)

comment:18 Changed 10 years ago by deyan

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

Batch update from file query-obsoleted.csv

Note: See TracTickets for help on using tickets.