-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Reinhard Poetz wrote: > Grzegorz Kossakowski wrote: >> Hmmm, does such structure and directory naming makes sense? I would >> expect creation of directory >> like this: >> cocoon/branches/cocoon-forms-1.0.x >> >> Putting Cocoon Forms 1.0.0 into cocoon-2.2 does not make sense because >> form block wouldn't be >> necessary tied to 2.2 of core. > > That might be true but e.g. for the documentation we agreed to put all > blocks unter http://cocoon.apache.org/2.2 because we also can't say that > cocoon-forms-1.0.x will work with all future Cocoon releases. > > When cocoon-forms-1.0.x is still compatible with e.g. Cocoon 2.3, then > we create just another branch > cocoon/branches/cocoon-2.3/cocoon-forms-1.0.x/ (though I hardly believe > that this will happen ...) So, where to put it now! Is this in need for a vote ;-) - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.6 (GNU/Linux) iD8DBQFG/OnuLNdJvZjjVZARAoprAKDOiPizDaxIbUcDp8OjMboS+AISfgCgtODM wUT5Ohwx5db8kALhlzB4nLc= =OcuM -----END PGP SIGNATURE-----
