On Tue, Nov 27, 2012 at 2:12 PM, Armando Perico wrote:
> This could be a good solution, however, the idea of having the files in
> different directories (moving for each status) is not really appreciated
> here :S
>
If you don't at least copy the final/release revs to tags, you are
pretty far awa
Considering that I won't be able to suggest a DMS (which would be the
correct solution as suggested by Andy),
what would do is:
1) In order to attach the status of the document and allowing the users to
easily see the current status and the previous values, I would probably
require a flag i.e.: [
Yes, use trac could be an option too. I will definitely check the pros and
cons for that!
On Tue, Nov 27, 2012 at 8:02 PM, Les Mikesell wrote:
> On Tue, Nov 27, 2012 at 9:51 AM, armando.perico.n...@usi.ch
> wrote:
> >
> > you are probably right if we think only about code and software
> projec
In some projects we have to use Dimensions, which is a proprietary solution
(http://www.serena.com/products/dimensions-cm/index.html) ; However, the
standard solution for the projects is SVN and I don't think I will be able
to make everybody to learn and use use another program.
Well, in any case,
This could be a good solution, however, the idea of having the files in
different directories (moving for each status) is not really appreciated
here :S
I really appreciated your answer, it is great to have different
point-of-views about this!
On Tue, Nov 27, 2012 at 5:10 PM, Ulrich Eckhardt <
On Tue, Nov 27, 2012 at 9:51 AM, armando.perico.n...@usi.ch
wrote:
>
> you are probably right if we think only about code and software projects;
> however, the needs for these features here are to control "documentation
> projects" i.e.: to handle documents for ISOs and IECs standard implementat
Guten Tag Ulrich Eckhardt,
am Dienstag, 27. November 2012 um 17:10 schrieben Sie:
> BTW: If you take a look at TortoiseSVN, it allows diffing of MS Word
> files, which could be very beneficial to you as it allows making small
> changes like spelling fixes without forcing people to make a full
> r
On Tue, Nov 27, 2012 at 10:51 AM, armando.perico.n...@usi.ch <
armando.perico.n...@usi.ch> wrote:
> Hi Andy,
>
> you are probably right if we think only about code and software projects;
> however, the needs for these features here are to control "documentation
> projects" i.e.: to handle document
Am 27.11.2012 16:51, schrieb armando.perico.n...@usi.ch:
Note: An important requirement here is that the path of the document
shall never change once it has been defined and published
internally.
Some uses cases:
> - Only create a "release" versions of the
documentation when all the documents
Hi Andy,
you are probably right if we think only about code and software projects;
however, the needs for these features here are to control "documentation
projects" i.e.: to handle documents for ISOs and IECs standard implementation
(we pretty much handle .doc files - no need to handle line di
On Tue, Nov 27, 2012 at 8:44 AM, armando.perico.n...@usi.ch <
armando.perico.n...@usi.ch> wrote:
> Guten Tag Thorsten!
>
> that's what I've imagined.
>
> We actually have to use SVN as a sort of configure management system. I am
> currently writing a pre-commit hook so we can control it without us
Guten Tag armando.perico.n...@usi.ch,
am Dienstag, 27. November 2012 um 14:44 schrieben Sie:
> Guten Tag Thorsten!
Please don't forget to answer to the list instead of me directly as
your input surely is interesting to others as well.
> It seems weird though that subversion has not a native way
Guten Tag Thorsten!
that's what I've imagined.
We actually have to use SVN as a sort of configure management system. I am
currently writing a pre-commit hook so we can control it without using the
"svn:properties" (we've decided to add a flag on the commit messages with the
current file statu
Guten Tag armando.perico.n...@usi.ch,
am Dienstag, 27. November 2012 um 13:47 schrieben Sie:
> I would like to know what is used so far to accomplish this task.
Subversion provides versioned properties which could be used but from
my experience most projects seem to not think in cases of status f
Hi,
I am part of the quality management at my company and we use SVN as our source
code repository.
I would like to know if is there a way in which I can control the "STATUS" of a
file (and its status-changes) ?
Example:
lets say that we have the following statuses:
UnderDevelopment, Tested, Ap
Guten Tag Bakke, Bjørn Ole,
am Dienstag, 27. November 2012 um 11:07 schrieben Sie:
> [ERROR]
> C:\Users\BLB\AppData\Local\Temp\svn-crash-log20121127095941.log
> [ERROR]
> C:\Users\BLB\AppData\Local\Temp\svn-crash-log20121127095941.dmp
http://mail-archives.apache.org/mod_mbox/subversion-users/2012
16 matches
Mail list logo