On 08/28/08 16:01, Jörg Jahnke wrote:
Hi,
Jens-Heiner Rechtien schrieb:
Martin Hollmichel wrote:
Jens-Heiner Rechtien wrote:
Hi Martin,
since almost all OOO300 CWSs (for the RC) will be integrated into
DEV300 as well it makes sense to have most of them already
integrated into DEV300 before starting the migration. Also there are
some quite huge CWSs currently in the queue which will go into
DEV300 today or in the next few days.
The current plan is to have all the cws for 3.0 rc ready this week
(today or tomorrow).
Currently it looks like that DEV300 m31 (the next DEV300 milestone)
could be a good basis for migration.
yes, but I think we should coordinate and announce this on
[EMAIL PROTECTED]
Ok.
So are there objections against starting the migration directly after
DEV300 m31 gets finished? Otherwise we (Hamburg RE) would start at that
time. I should add that ideally any CWSs with greater changes that are
finished already should make it into m31 to avoid unncessary work.
There is
<http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fsb93>
which touches quite a number of files and should go into QA tomorrow.
Not sure whether it is worth waiting for it, though---those who have to
do the actual migration work may have an opinion here.
(However, what would disappoint me somewhat is if the CWS's carefully
written CVS commit comments were effectively lost, for example in case
the CWS is not integrated into the final CVS HEAD revision but only into
some SVN revision other than the initial one---that the corresponding
SVN revision contains changes for which commit comments can be found by
looking at a specific CWS branch tag in the corresponding CVS file log
is so much more obscure than if the commit comments can be found by
looking at the last HEAD entry in the corresponding CVS file log.)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
