A Dimarts, 28 de febrer de 2012 19:29:47, Udo Spallek va escriure: > Hi, > Sat, 21 Jan 2012 18:19:20 +0100 > > Paul J Stevens <[email protected]>: > > Sat, 21 Jan 2012 16:24:01 +0100 > > > > Albert Cervera i Areny <[email protected]>: > > > c) How to share code migration tools > > > Sharing the tools one uses to migrate modules would be great I > > > think. From simple "grep" statements to codemod [1] scripts. > > > Although, CHANGELOG could be improved I'm not sure that's the > > > appropriate place to share those scripts and tips. If we want to > > > keep them in the repository, maybe we could add a new directory > > > with a subdirectory or file per release where that information was > > > included. That said, a wiki has the advantage that more people can > > > easily share improvement's over the original tools. > > > > I for one agree that more information and descriptive examples is > > better than just changelog messages. > > Those are very terse and no: > > referring to rietveld or commit-sets is no replacement for recipes > > and howtos. The Transaction conversion was doable because the was a > > lot of people doing similar changes, providing lots of examples of > > the required change pattern. Finding those changes months or maybe > > years later will be that much harder. Having a wiki page with > > upgrade/migration notes will be a great boon. > > Typically I suspect and expect that real-world deployments will not > > upgrade to the latest and greatest whenever it comes available, just > > because it's available. They will want to upgrade when not upgrading > > becomes too painful. As long as the running version works ok, why > > change? > > I make most of my money upgrading old Plone installations. And I can > > tell you; unit-tests are very great, but clear and concise upgrade > > notes are golden. > > Yes, I agree, migration and upgrade notes are life saving. > > To check out if we have a consensus at least on this topic, I > like to request the Tryton community: > > * Are we willing to collaborate to collect migration recipes and > helper scripts for future versions of Tryton?
Yes! > * Is the actual form[1] sufficient enough? Or are there better ideas? Don't have a better idea. That said, I don't know if we'd like to "standarize" (for a very loose meaning of "standarize") in some tools for that task. For example, facebook's codemod could be of help. [1] https://github.com/facebook/codemod -- Albert Cervera i Areny http://www.NaN-tic.com Tel: +34 93 553 18 03 http://twitter.com/albertnan http://www.nan-tic.com/blog -- [email protected] mailing list
