Hide Forgot
We have some customers who are frustrated by the lack of proper tooling for migrations. To avoid one-off patches, we often suggest that customers upgrade versions of our products, but when we have inadequate tooling to assist with migrations this is not well received. Migration tools could also be of use in community-to-supported situations. We sometimes get tickets from Drools shops that would like to become BRMS customers, but the transition is unnecessarily difficult. Could we please build better migration facilities, probably based on the ant repository migration tool? This seems to be the preferred mechanism. We would save ourselves considerable headaches if we would please consider this a proper part of the distribution and devote proper development and QE time for it. Thanks.
Can you please explain the requirement a little more? Upgrading serialized RuleBases? Serialised Packages etc or does this relate to Guvnor repositories etc?
@manstis There's a big discussion about this, I 've forwarded you the discussion mail called "Drools migration script". Bottom line is GUVNOR-1214.