Hi Guiliano, Please send all communication to the mailing list.
On Fri, 2010-01-22 at 14:08 +0000, Giuliano Arroyo Rodrigues wrote: > Good Morning Kristis. > > You wrote: > > "This may be tricky to implement, but doable. For example, how does > one > > first associate the list of files that are allowed to be committed > in > > the bug ? Should it be done on the bug-tracker ? In the glue > > configuration ? Configuring it in the bug-tracker sounds more > > appropriate." > > How do i can do that by the bug-tracker? Do you have any idea? It depends on your bug-tracker, and on how you want to do it. For example, in Bugzilla you could add a custom field in which you could provide a comma separated list of files that should not be modified. Or just add it as a comment with a special prefix, like: ALLOWED FILES: file1.doc dir/file2.csv Regardless of what you do, Scmbug would still need to read that information and validate it. > You wrote: > > "I also need to ask: why do you want to restrict the list of files > that > > can be modified in that bug ? I can imagine how this can be useful > to > > others too. I am curious about why you want to do it." > > One of the demands of the configuration management is the changes > control. We have to control which files are doing modified and why the > modifies are necessary. Nowadays, we have this control, but it is made > by a checklist. In this way, the configuration manager takes long time > do verify this rule. This is the main reason that's why we want to > implement that in SCMBUG > > > > > > > > Subject: Re: [scmbug-users] Validation of committed archives on SCM > with thebug/issue on bugtracker > > From: [email protected] > > To: [email protected] > > CC: [email protected] > > Date: Thu, 21 Jan 2010 10:50:12 -0700 > > > > Hi Guiliano, > > > > I see what you are trying to do. Scmbug currently does not support > the > > option of associating a list of files that are allowed to be changed > in > > a bug. > > > > I have just added this on the todo list: > > > > http://bugzilla.mkgnu.net/show_bug.cgi?id=1450 > > > > This may be tricky to implement, but doable. For example, how does > one > > first associate the list of files that are allowed to be committed > in > > the bug ? Should it be done on the bug-tracker ? In the glue > > configuration ? Configuring it in the bug-tracker sounds more > > appropriate. > > > > > > > > > "For sample, I open the bug #15 and I related the files > build.xml > > > and > > > > >> AppMain.java to it. If the developer try commit to Subversion > the file > > > > For example, how did you "relate" these files to bug #15 ? > > > > I also need to ask: why do you want to restrict the list of files > that > > can be modified in that bug ? I can imagine how this can be useful > to > > others too. I am curious about why you want to do it. > > > > > ______________________________________________________________________ > Quer 25 GB de armazenamento gratuito na web? Conheça o Skydrive > clicando aqui.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
