Ticket #1439 (closed planned_task: obsolete)

Opened 14 years ago

Last modified 13 years ago


Reported by: Astea Owned by: todor
Priority: 3 Milestone: M05_PRE5
Component: PROJECT_COMMUNITY Version: 2.0
Keywords: Cc:
Category: SCS Effort: 1
Importance: 60 Ticket_group:
Estimated Number of Hours: Add Hours to Ticket:
Billable?: Total Hours:
Analysis_owners: deyan Design_owners: todor
Imp._owners: todor Test_owners:
Analysis_reviewers: todor Changelog:
Design_reviewers: kyli Imp._reviewers: danvisel
Test_reviewers: Analysis_score: 3.5
Design_score: 3 Imp._score: 3
Test_score: 0


wiki page: SCS_PROJECT_BLOG_R4 - effort: 1d

Change History

comment:1 Changed 14 years ago by deyan

  • Status changed from new to s1a_analysis_started
  • Analysis_score set to 0
  • Test_score set to 0
  • Design_score set to 0
  • Owner changed from Astea to deyan
  • Imp._score set to 0
  • Analysis_owners set to deyan

taken for analysis

comment:2 Changed 14 years ago by deyan

  • Status changed from s1a_analysis_started to s1b_analysis_finished


comment:3 Changed 14 years ago by todor

  • Status changed from s1b_analysis_finished to s1c_analysis_ok
  • Analysis_reviewers set to todor
  • Analysis_score changed from 0 to 3.5

maybe creating of log file for the closing should be mentioned here.

comment:4 Changed 14 years ago by todor

  • Design_owners set to todor
  • Owner changed from deyan to todor
  • Status changed from s1c_analysis_ok to s2a_design_started


comment:5 Changed 14 years ago by todor

  • Status changed from s2a_design_started to s2b_design_finished

sample post is ready.

comment:6 Changed 14 years ago by kyli

  • Status changed from s2b_design_finished to s2c_design_ok
  • Design_score changed from 0 to 3
  • Design_reviewers set to kyli


  • When deciding to change a task, the standard process is to super review it, then re-analyze it. If you have decided to remove the second post, you should do so. Please, follow the process.
  • For the last two revisions of this task, Dan suggests to help with proofreading and formatting of the post. I think it is reasonable to let people help us if they want to.
  • The requirement about this blog post is to be provided at the beginning of the sprint. As I see, it is posted on 26th feb, which is not good. You should think about making sure the task will not be implemented too late the next time (maybe setting its importance, etc.)

comment:7 Changed 14 years ago by todor

  • Status changed from s2c_design_ok to s3a_implementation_started
  • Imp._owners set to todor

the delay of the post is due to the fact that it needs to be approved by ludmil and nick, because of this delay super reviewing and following the process would result in even bigger delay.

comment:8 Changed 14 years ago by todor

  • Status changed from s3a_implementation_started to s3b_implementation_finished

it took too much time to follow all states for the regular tasks (they're waiting too much for reviews), especially for the one that need to be done in specific time, this need to be mentioned when discussing the process. maybe we should discuss other approach for blog and mail list.

comment:9 Changed 14 years ago by danvisel

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

The end result is good; it's too bad that it couldn't have been finished on 13 March when the release came out, which is a problem.

I'd suggest that for next time it might make sense to split this into two different posts: first, a quick post when the release comes out announcing that there is a release with a quick overview of what's new in the release, and second, a longer post with the summary of the iteration. The release was on time; when the blog post is late, that suggests to the public that the release was late, which we don't want to do. I think it would be okay if the summary came out later - that serves a different function.

comment:10 Changed 13 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.