Philipp Lohmann wrote:
Rüdiger Timm wrote:
I'm all in favour of this change. My only question would be about the
time line. We are going to split off a separate OOo 3.1 code line
soon. Only 3.1 tasks will be accepted there. Having psprint code
inside vcl on TRUNK and in a separate module on 3.1 branch for several
months sounds like a maintenance nightmare.
Aside from the need for development to handle possible changes in two
separate CWS, will there be additional maintanence problems ? I don't
really expect psprint changes for 3.1 anymore (knock on wood), so I am
willing to risk that. However if there are problems for releng as well,
we could wait a little more until the 3.1 tree has stabilized a bit.
Kind regards, pl
No other problems. Just that childworkspaces for 3.1 / 3.1.1 containing
psprint (and certain parts of vcl?) can't get cloned for 3.2 any more.
Rüdiger
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
