The Bugzilla Migration Framework

[Max Kanat-Alexander]

On 10/24/2009 12:42 AM, David Miller wrote:
> You should write up a version of this post targeted at integrators and
> consultants and send it to the announce list, might get some good
> traction on it.

	I did this today, basically, as part of the latest Bugzilla Update:

	http://bugzillaupdate.wordpress.com/2009/11/05/release-3-4-3/

	By the way, I highly encourage anybody who reads this list to also
subscribe to the Bugzilla Update--it's a good concise summary of what's
been going on with the Bugzilla Project, and I hope to update it more
often than we release--that is, on a somewhat regular schedule.

> Should we make any kind of rule about not breaking import from an older
> version of something in order to make an import from a newer version
> work?  I'm pretty sure the gnats2bz script in contrib got updated for a
> newer version of gnats at one point and it got wholesale replaced with
> the code for the new version instead of checking to see which schema it
> needed to work with.
> 
> On the other hand, if it always works with the latest version I suppose
> we could tell people they need to ugprade whatever they're migrating
> from to the latest first.  But then again, sometimes that costs money
> you wouldn't want to spend if you're moving away from that product anyway...

	I think the thing to do for now is to play it by ear. If there's a
situation that's going to break import from an old version, but the
version is like 10 years old, then I think it's less important than if
we're breaking import from the latest stable version in order to get
compatibility with a development version. (Those would be the two extremes.)

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.