Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=GROUP_SCS_SUMMARY_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

As project blog and mail list are regular tasks, the requirements are not different from previous revisions.

Task requirements

Send two e-mails:

• Mail1 to the sophie2-devs list - contains last sprint summary
• Mail2 to the sophie2-users list - contains information mentioned below
  • Features
  • Latest release
    • Changelog
  • Upcoming releases
  • Features expected in the next release
• Collect this information about current iteration and send an e-mail containing it.

Write two blog posts for this iteration
Post 1: (at the iteration start)

• Last sprint overview (added features and functionality)
• Explain interesting technologies introduced in this sprint
• What went well
• What could be better
• Decided improvements that will be applied

Post 2: (at the middle of the iteration)

• Progress overview
• Interesting technologies used
• Challanging tasks
• Applied improvements (from the sprint closing)

Task result

Two e-mails. One to the developer group and one to the user group. Two blog posts.

Implementation idea

For the e-mail one, keep the structure of previous revisions of this task. Contact the release team to get the changelog. You may include feature from the feature schedule the release team is working on. Use the closing log from the repository.

Related

SCS_PROJECT_BLOG_R5?
SCS_MAIL_LIST_R5?

How to demo

Explain what is done. Show the blog posts.

Design

• Sample content for the devs mail and blog post

  ITERATION_05 Summary
  ITERATION_05 is over and now it is time to look back at what has been done.
  As scheduled on March 13 we delivered the pre-alpha4 version of Sophie 2, which is available for download here [http://www.sophie2.org/users/downloads.html]. We also are proud to present the new Sophie 2 community site [http://www.sophie2.org] which will be enhanced even more in the upcoming week. We had a lot of design discussions which improved the global vision of the team members, you can find the videos here [http://sophie2.org/trac/wiki/Videos]. We managed to create stable wireframe for the specifications of the project and improved the overall quality of the code.
  But now let’s pay attention to the Sophie 2 third release and its features. Sophie 2 pre-alpha4 can run on Windows, Linux and MacOS and includes many of the functionalities (some in prototype form) of the final product. Some of them are: inserting different types of resources like pdf files, images, audio and video files, creating annotations, basic frame manipulation and others that you can check by yourself. Although there are still some known issues most of which are listed in the product’s download page [http://www.sophie2.org/users/downloads.html] in the section “Known Problems”.
  As usual we’re going to inform you about the results of the iteration closing in the next section.
  What went well:
   * release was on time
   * new functionalities were added to the product
   * team’s availability has improved a lot
   * discussions helped to spread the global vision
   * lots of blockers were fixed
  What could be better:
   * because of the release date we didn’t follow the process
   * we may need to simplify the process
   * self management could be better
  How to improve:
   * better self management
   * improve the process
   * prioritizing of tasks
   * do some pair programming
  Best regards from the Sophie team!
  

• Send the sample content to Nick and Ludmil for possible corrections.
• Fix it according to the recommendations and send it in the implementation phase of the task.

Implementation

• Fixed content

  ITERATION_05 Summary
  ITERATION_05 is over and now it is time to look back at what has been done.
  As scheduled on March 13 we delivered the pre-alpha4 version of Sophie 2, which is available for download here [http://www.sophie2.org/users/downloads.html]. We also are proud to present the new Sophie 2 community site [http://www.sophie2.org] which will be enhanced even more in the upcoming week. We had a lot of design discussions which improved the global vision of the team members, you can find the videos here [http://sophie2.org/trac/wiki/Videos]. We managed to create stable wireframe for the specifications of the project and improved the overall quality of the code.
  But now let’s pay attention to the Sophie 2 third release and its features. Sophie 2 pre-alpha4 can run on Windows, Linux and MacOS and includes many of the functionalities (some in prototype form) of the final product. Some of them are: inserting different types of resources like pdf files, images, audio and video files, creating annotations, basic frame manipulation and others that you can check by yourself. Although there are still some known issues most of which are listed in the product’s download page [http://www.sophie2.org/users/downloads.html] in the section “Known Problems”.
  As usual we’re going to inform you about the results of the iteration closing in the next section.
  What went well:
   * release was on time
   * new functionalities were added to the product
   * team’s availability has improved a lot
   * discussions helped to spread the global vision
   * lots of blockers were fixed
  What could be better:
   * because of the release date we didn’t follow the process
   * we may need to simplify the process
   * self management could be better
  How to improve:
   * better self management
   * improve the process
   * prioritizing of tasks
   * do some pair programming
  Best regards from the Sophie team!
  

• The mail was sent to the devs and post was created in the blog.

Testing

^{(Place the testing results here.)}

Comments

^{(Write comments for this or later revisions here.)}