[Zope-CMF] Best use of source numbers in GS upgrade steps?

2009-04-16 Thread Maurits van Rees
Hi, I wonder what the best way is of specifying the source number of a GenericSetup upgrade step. Use case Case in point: Products.Poi, an issue tracker for CMFPlone. Between version 1.1 and 1.2 there were changes that needed an upgrade step, which I registered like this:

Re: [Zope-CMF] Best use of source numbers in GS upgrade steps?

2009-04-16 Thread yuppie
Hi Maurits! Maurits van Rees wrote: [...] Probably not relevant here, but for completeness sake: - Poi branch 1.1 has 1.1.x in its version.txt and does not have a metadata.xml. - Poi trunk has 1.2.x in both its version.txt and metadata.xml. I know that it is best to use both files

Re: [Zope-CMF] Best use of source numbers in GS upgrade steps?

2009-04-16 Thread Rob Miller
Maurits van Rees wrote: Hi, I wonder what the best way is of specifying the source number of a GenericSetup upgrade step. ---SNIP a bunch of stuff about how using versions to mark GS upgrade steps is annoying--- yes, as you discovered, using source and destination versions to mark when

Re: [Zope-CMF] Best use of source numbers in GS upgrade steps?

2009-04-16 Thread Maurits van Rees
Hello yuppie! yuppie, on 2009-04-16: Maurits van Rees wrote: So my question is: is this a sane way of doing this? Is it alright to specify a version (or really a profile revision) as source when that version does not yet exist? It works fine as far as I can tell. AFAICS this will not work