Andreas Hartmann wrote:
Gregor J. Rothfuss wrote:
Andreas Hartmann wrote:
We once agreed to avoid backwards-incompatible changes in stable
branches, i.e., when 1.4 is released there may not be any backwards-
incompatible changes anymore. We would have to setup a new trunk
(1.6-dev), and this would mean to maintain 3 branches. IIRC the
community
agreed that this is too complex.
I'm totally in favor of the "release early, release often" credo,
but I can't see how we could manage it ... How do other projects
with small communities handle this situation?
at the time of 1.4 branching, we would stop maintaining the 1.2 branch.
Yes, that occured to me too as the only reasonable consequence.
But is this really feasible, given that the migration from 1.2
to 1.4 is not really trivial?
Well, in want of an alternative, I'd agree to this practice.
I'd rather give some migration support than delay the 1.4 release
much further.
What do the others think?
+1
Although I stopped running 1.2 a year ago. I think we should work on
migration issues to make easier.
The migration target in the original email didn't work for me. I
changed it to point to my tomcat webapp directory but it made a new
content directory in the pubs dir (instead of the publication). This
works for me:
<target name="migrate-extensions">
<property name="publication" value=""/>
<move todir="${tomcat.webapps.dir}/lenya/pubs/${publication}">
<fileset dir="${tomcat.webapps.dir}/lenya/pubs/${publication}">
<include name="content/**"/>
<exclude name="content/*/site.xml"/>
<exclude name="content/*/sitetree.xml"/>
</fileset>
<compositemapper>
<mapper type="glob" from="*.xml" to="*"/>
<mapper type="glob" from="*.xml.meta" to="*.meta"/>
</compositemapper>
</move>
</target>
--Doug
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
