+1
Pavel Janík wrote:
Hi,
today, I investigated changes in aquavcl01 (in modules != vcl).
Some changes are very clean and can't affect other platforms. But some
changes we have in the tree can affect other platforms. This is very
unfortunate, because it makes the integration a bit harder and RE will
look sharply on our changes.
To prevent this, I suggest to first do cleanup of our cws. In the past,
we haven't cared about entering issue touching code of other platforms
etc. I have sent several e-mails to the members of our team to fix the
issues identified and will start cleaning up modules != vcl to be
integrated even before to get better testing.
I'd like to propose the following now:
- when fixing some issue in module != vcl, please file proper issue for
your fix!
- please do not add new modules now to aquavcl01, wait for new cws and
for the integration of aquavcl01
- after integration of aquavcl01, we should go into standard OOo
development model, ie. no commit without respective issue.
Do you agree?
--
If you give someone a program, you will frustrate them for a day;
if you teach them how to program, you will frustrate them for a lifetime.
-- Author unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
