SuperAmerica/agilefant — pull request #17 by mike1072 (2012-02-13 07:15:09+00:00)
Title: Sprint 2 - Agilegret Standalone Iteration Branch

The changes to standalone iterations are in a separate branch due to limited testing and additional requirements to merge.

Story: https://soberit.myfant.com/qr.action?q=story:378

"When these changes are migrated the DB schema changes. One can either run the DB migration script in:
doc/upgrade/agilefant_upgrader.sh, or reset the DB by dropping it, creating it and re-creating the schema from a fresh build/create-db.ddl file ("ant create-ddl").

The migration system will use the script in doc/sql/upgrader/205-300.sql and check that if the current database version is 205 ("select * from settings where name='AgilefantDatabaseVersion';"). It will change the schema and update the stories which are under an iteration. The newly created iteration_id will then point to the iteration's db ID and the backlog_id is set to point to the iteration's parent (project backlog). For stories that are not directly under an iteration, the iteration_id is left NULL, which means that the story isn't assigned to any iteration and can remain in a project or product backlog."

-----------------------

"The confidence level is around 80% that this will actually work in a production case. Testing the new code would require lots of more time and going back and forth with the old DB+code and new code+migrated DB.

So I wouldn't recommend yet pushing it to the main superamerica branch and demoing it, unless that's what Jarno wants us to do. I wouldn't want to cause harm to other teams by breaking their system, but on the other hand that might improve the quality by finding more bugs. Jarno?? What to do?

.antti"