[almighty] How are we handling migrations at the moment ?

[Thomas Mäder]

Hi Shoubik,

We don't handle this at the moment. We have 
https://github.com/almighty/almighty-core/issues/123 to address this 
issue, but it is not planned for this sprint.

We might cheat and use a database migration for the change, but that, 
too is blocked by https://github.com/almighty/almighty-core/issues/184. 
Konrad, do you think that will arrive in time to help Shoubik?

If only we had a system to track dependencies between tasks...

/Thomas


On 09/23/2016 09:39 AM, Shoubhik Bose wrote:
> Hi,
>
> I've changed the work item type fields to have an additional field 
> called "system.remote_item_id" which has a required=false ( in the 
> createCommon() method in migration/migration.go )
>
> When the code gets merged to master, the existing work items would 
> need to be altered.
> How would that be handled?
>
>
> Thanks,
> Shoubhik
>
>
>
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160923/bb29f6d0/attachment.htm>