You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <br...@users.sf.net> on 2013/11/05 19:26:15 UTC
[allura:tickets] #6848 Coalesce scripts/migrations/*trove*.py into
command/create_trove_categories.py
---
** [tickets:#6848] Coalesce scripts/migrations/*trove*.py into command/create_trove_categories.py**
**Status:** open
**Created:** Tue Nov 05, 2013 06:26 PM UTC by Dave Brondsema
**Last Updated:** Tue Nov 05, 2013 06:26 PM UTC
**Owner:** nobody
command/create_trove_categories.py sets up the initial trove categories. Over time we've created several migrations to update the trove categories, but few (if any) of those changes are in the command/create_trove_categories.py So when you start a new instance of Allura, you don't have the latest (unless you run all the migrations).
So we should take all the changes specified in these files, and update command/create_trove_categories.py to set them all up properly there. Be very careful! :)
scripts/migrations/014-add-trove-category-agpl.py
scripts/migrations/016-add-trove-category-lppl.py
scripts/migrations/017-sync-trove-categories.py
scripts/migrations/019-set-parent-only-troves.py
scripts/migrations/021-add-new-trove-license-categories.py
scripts/migrations/023-add-new-trove-license-category.py
scripts/migrations/030-set-trove-show_as_skill.py
The end result should be that the `trove_category` collection is the same after running NEW command/create_trove_categories.py, compared to OLD command/create_trove_categories.py PLUS all migrations.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6848 Coalesce scripts/migrations/*trove*.py into
command/create_trove_categories.py
Posted by Tim Van Steenburgh <va...@users.sf.net>.
- **QA**: Tim Van Steenburgh
- **Milestone**: forge-backlog --> forge-jan-10
---
** [tickets:#6848] Coalesce scripts/migrations/*trove*.py into command/create_trove_categories.py**
**Status:** code-review
**Labels:** 42cc
**Created:** Tue Nov 05, 2013 06:26 PM UTC by Dave Brondsema
**Last Updated:** Fri Dec 27, 2013 02:26 PM UTC
**Owner:** nobody
command/create_trove_categories.py sets up the initial trove categories. Over time we've created several migrations to update the trove categories, but few (if any) of those changes are in the command/create_trove_categories.py So when you start a new instance of Allura, you don't have the latest (unless you run all the migrations).
So we should take all the changes specified in these files, and update command/create_trove_categories.py to set them all up properly there. Be very careful! :)
scripts/migrations/014-add-trove-category-agpl.py
scripts/migrations/016-add-trove-category-lppl.py
scripts/migrations/017-sync-trove-categories.py
scripts/migrations/019-set-parent-only-troves.py
scripts/migrations/021-add-new-trove-license-categories.py
scripts/migrations/023-add-new-trove-license-category.py
scripts/migrations/030-set-trove-show_as_skill.py
The end result should be that the `trove_category` collection is the same after running NEW command/create_trove_categories.py, compared to OLD command/create_trove_categories.py PLUS all migrations.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: #6848 Coalesce scripts/migrations/*trove*.py into
command/create_trove_categories.py
Posted by Dave Brondsema <br...@users.sf.net>.
Yes, definitely.
---
** [tickets:#6848] Coalesce scripts/migrations/*trove*.py into command/create_trove_categories.py**
**Status:** in-progress
**Labels:** 42cc
**Created:** Tue Nov 05, 2013 06:26 PM UTC by Dave Brondsema
**Last Updated:** Fri Nov 08, 2013 08:01 AM UTC
**Owner:** nobody
command/create_trove_categories.py sets up the initial trove categories. Over time we've created several migrations to update the trove categories, but few (if any) of those changes are in the command/create_trove_categories.py So when you start a new instance of Allura, you don't have the latest (unless you run all the migrations).
So we should take all the changes specified in these files, and update command/create_trove_categories.py to set them all up properly there. Be very careful! :)
scripts/migrations/014-add-trove-category-agpl.py
scripts/migrations/016-add-trove-category-lppl.py
scripts/migrations/017-sync-trove-categories.py
scripts/migrations/019-set-parent-only-troves.py
scripts/migrations/021-add-new-trove-license-categories.py
scripts/migrations/023-add-new-trove-license-category.py
scripts/migrations/030-set-trove-show_as_skill.py
The end result should be that the `trove_category` collection is the same after running NEW command/create_trove_categories.py, compared to OLD command/create_trove_categories.py PLUS all migrations.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6848 Coalesce scripts/migrations/*trove*.py into
command/create_trove_categories.py
Posted by Igor Bondarenko <je...@users.sf.net>.
`scripts/migrations/019-set-parent-only-troves.py` talks to sfx database to select trove categories with `parent_only==1`, adn than sets `parent_only = True` on corresponding categories in Allura db. I wonder if we could drop this and use a hardcoded list of ids in new trove command (fetched once from sfx db) to avoid dependency on sfx. What do you think?
---
** [tickets:#6848] Coalesce scripts/migrations/*trove*.py into command/create_trove_categories.py**
**Status:** in-progress
**Labels:** 42cc
**Created:** Tue Nov 05, 2013 06:26 PM UTC by Dave Brondsema
**Last Updated:** Wed Nov 06, 2013 07:52 PM UTC
**Owner:** nobody
command/create_trove_categories.py sets up the initial trove categories. Over time we've created several migrations to update the trove categories, but few (if any) of those changes are in the command/create_trove_categories.py So when you start a new instance of Allura, you don't have the latest (unless you run all the migrations).
So we should take all the changes specified in these files, and update command/create_trove_categories.py to set them all up properly there. Be very careful! :)
scripts/migrations/014-add-trove-category-agpl.py
scripts/migrations/016-add-trove-category-lppl.py
scripts/migrations/017-sync-trove-categories.py
scripts/migrations/019-set-parent-only-troves.py
scripts/migrations/021-add-new-trove-license-categories.py
scripts/migrations/023-add-new-trove-license-category.py
scripts/migrations/030-set-trove-show_as_skill.py
The end result should be that the `trove_category` collection is the same after running NEW command/create_trove_categories.py, compared to OLD command/create_trove_categories.py PLUS all migrations.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6848 Coalesce scripts/migrations/*trove*.py into
command/create_trove_categories.py
Posted by Tim Van Steenburgh <va...@users.sf.net>.
- **status**: code-review --> closed
---
** [tickets:#6848] Coalesce scripts/migrations/*trove*.py into command/create_trove_categories.py**
**Status:** closed
**Labels:** 42cc
**Created:** Tue Nov 05, 2013 06:26 PM UTC by Dave Brondsema
**Last Updated:** Thu Jan 02, 2014 02:36 PM UTC
**Owner:** nobody
command/create_trove_categories.py sets up the initial trove categories. Over time we've created several migrations to update the trove categories, but few (if any) of those changes are in the command/create_trove_categories.py So when you start a new instance of Allura, you don't have the latest (unless you run all the migrations).
So we should take all the changes specified in these files, and update command/create_trove_categories.py to set them all up properly there. Be very careful! :)
scripts/migrations/014-add-trove-category-agpl.py
scripts/migrations/016-add-trove-category-lppl.py
scripts/migrations/017-sync-trove-categories.py
scripts/migrations/019-set-parent-only-troves.py
scripts/migrations/021-add-new-trove-license-categories.py
scripts/migrations/023-add-new-trove-license-category.py
scripts/migrations/030-set-trove-show_as_skill.py
The end result should be that the `trove_category` collection is the same after running NEW command/create_trove_categories.py, compared to OLD command/create_trove_categories.py PLUS all migrations.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6848 Coalesce scripts/migrations/*trove*.py into
command/create_trove_categories.py
Posted by Igor Bondarenko <je...@users.sf.net>.
Closed #483. `je/42cc_6848`
How I tested:
- checkout master and run command + each migration in order
- dump trove_collection to a file `mongo pyforge dump_trove.js > before.json` (`dump_trove.js` in attachments)
- checkout `je/42cc_6848`, run command again
- `mongo pyforge dump_trove.js > before.json`
- `diff before.py mongo.py` mustn't show any differences
Attachment: dump_trove.js (254 Bytes; application/javascript)
---
** [tickets:#6848] Coalesce scripts/migrations/*trove*.py into command/create_trove_categories.py**
**Status:** in-progress
**Labels:** 42cc
**Created:** Tue Nov 05, 2013 06:26 PM UTC by Dave Brondsema
**Last Updated:** Fri Nov 08, 2013 08:01 AM UTC
**Owner:** nobody
command/create_trove_categories.py sets up the initial trove categories. Over time we've created several migrations to update the trove categories, but few (if any) of those changes are in the command/create_trove_categories.py So when you start a new instance of Allura, you don't have the latest (unless you run all the migrations).
So we should take all the changes specified in these files, and update command/create_trove_categories.py to set them all up properly there. Be very careful! :)
scripts/migrations/014-add-trove-category-agpl.py
scripts/migrations/016-add-trove-category-lppl.py
scripts/migrations/017-sync-trove-categories.py
scripts/migrations/019-set-parent-only-troves.py
scripts/migrations/021-add-new-trove-license-categories.py
scripts/migrations/023-add-new-trove-license-category.py
scripts/migrations/030-set-trove-show_as_skill.py
The end result should be that the `trove_category` collection is the same after running NEW command/create_trove_categories.py, compared to OLD command/create_trove_categories.py PLUS all migrations.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #6848 Coalesce scripts/migrations/*trove*.py into
command/create_trove_categories.py
Posted by Igor Bondarenko <je...@users.sf.net>.
- **status**: in-progress --> code-review
---
** [tickets:#6848] Coalesce scripts/migrations/*trove*.py into command/create_trove_categories.py**
**Status:** code-review
**Labels:** 42cc
**Created:** Tue Nov 05, 2013 06:26 PM UTC by Dave Brondsema
**Last Updated:** Fri Dec 27, 2013 02:24 PM UTC
**Owner:** nobody
command/create_trove_categories.py sets up the initial trove categories. Over time we've created several migrations to update the trove categories, but few (if any) of those changes are in the command/create_trove_categories.py So when you start a new instance of Allura, you don't have the latest (unless you run all the migrations).
So we should take all the changes specified in these files, and update command/create_trove_categories.py to set them all up properly there. Be very careful! :)
scripts/migrations/014-add-trove-category-agpl.py
scripts/migrations/016-add-trove-category-lppl.py
scripts/migrations/017-sync-trove-categories.py
scripts/migrations/019-set-parent-only-troves.py
scripts/migrations/021-add-new-trove-license-categories.py
scripts/migrations/023-add-new-trove-license-category.py
scripts/migrations/030-set-trove-show_as_skill.py
The end result should be that the `trove_category` collection is the same after running NEW command/create_trove_categories.py, compared to OLD command/create_trove_categories.py PLUS all migrations.
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.