André Schnabel, 30-07-2007 18:30:
Caio Tiago Oliveira schrieb:
If we really need a fixed set of scripts, I'd rather go with CVS-Tags ..
or wait for other suggestions (we will need such suggestions anyway, as
"soon" as we start to collect resultfiles from the community).
We need the scripts from other branches than HEAD.
I have no problem with that. just tell me a set of relevant branches and
I'll genereate the archives.
But from what I see, there are only two relevant branches available at
the moment .. HEAD and OOo220.
We're going to have a branch for 2.3 soon, and branches for other major
versions.
I'm pretty sure you'll know when this happens.
The ideal would be to have a certified version from our automation team.
This would avoid bothering with errors from the scripts while testing.
I absolutely agree to most of your points. But I'm not sure what would
really make sense here.That could only be answered by the automation
team (or better by those people who work day by day with and on the
scripts). To provide archives on a dayly basis that have the the date in
the file name (without knowing, if this set of scripts has a
spezial"stable" meaning for a given milestone) is nothing but a waste of
diskspace.
We would only require one for each branch, one certified to work on the
latest milestone (from HEAD).
The date itself would be only to help if he finds some issues. It's
easier to say that his scripts are from some date than looking at each
relevant header.
There is no need to archive every set of scripts.
So I'd really wait for an answer from automation team before I implement
something like that.
I agreed here.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
