Jean-Marc Lasgouttes wrote:
> I added it.
Thanks (I also asked Lars in the meantime)
> Do you want to be trac_admin? There is no way to grant
> specifically
> the right to add versions.
Yes, why not.
Jürgen
Le 5 juin 09 à 17:21, Jürgen Spitzmüller a écrit :
Jean-Marc Lasgouttes wrote:
I used that in the past to mark bugs that must be fixed before a
release
(since "blocker" on bugzilla had a different meaning).
So, do you want it? It is up to you.
Yes, please add it.
done.
BTW. do you know
Jean-Marc Lasgouttes wrote:
> > I used that in the past to mark bugs that must be fixed before a release
> > (since "blocker" on bugzilla had a different meaning).
>
> So, do you want it? It is up to you.
Yes, please add it.
BTW. do you know how to add a new version (i.e., 1.6.3) to the version c
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>> On aussie, right?
>
> ftp.devel.lyx.org. Is this aussie (I always forget that)?
Yes.
>> The only other one we missed is 'release_blocker', which does not seem
>> useful either.
>
> I used that in the past to mark bugs that must be fixed
Jean-Marc Lasgouttes wrote:
> On aussie, right?
ftp.devel.lyx.org. Is this aussie (I always forget that)?
> A more recent version seems to be:
>
> ./data/versioncache:@::legal_keywords =
> ('assertion','compat','cosmetic','crash','dataloss','easyfix','fileformat',
>'fixedinbranch','fixedintrunk',
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>> > The old description (which I found now on the server in bugzilla/)
>> > says:
>>
>> Where exactly?
>
> /home/bugzilla/Bugzilla.sql
On aussie, right?
A more recent version seems to be:
./data/versioncache:@::legal_keywords =
('asser
Jean-Marc Lasgouttes wrote:
> > The old description (which I found now on the server in bugzilla/)
> > says:
>
> Where exactly?
/home/bugzilla/Bugzilla.sql
> > 'compat','Correct import of previous versions of LyX documents'
>
> OK, I will not add it then.
>
> > * 'leak','(Suspected) memory leak.'
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>> What is this good for? It looks to be related to import problems, but do
>> we want to keep it? (we can keep it in old bugs as long as we do not
>> edit them IMO)
>
> The old description (which I found now on the server in bugzilla/)
> s
Jean-Marc Lasgouttes wrote:
> What is this good for? It looks to be related to import problems, but do
> we want to keep it? (we can keep it in old bugs as long as we do not
> edit them IMO)
The old description (which I found now on the server in bugzilla/) says:
'compat','Correct import of previ
Jürgen Spitzmüller writes:
> I found further:
> compat,
What is this good for? It looks to be related to import problems, but do
we want to keep it? (we can keep it in old bugs as long as we do not
edit them IMO)
I can added if you want me too.
> VERIFIED,
I think it has been added by Lars'
Jean-Marc Lasgouttes wrote:
>Here is my new list. I killed copier and RFE.
>keywords = crash, regression, dataloss, patch, easyfix, fixedinbranch,
> fixedintrunk, ui, qtbug, fileformat, assertion, testcase, cosmetic,
> release_notes, perf, os=linux, os=windows, os=macosx
Nice work!
I found furthe
Jürgen Spitzmüller writes:
> I'm sure I missed some.
Yes, you missed at least dataloss.
Here is my new list. I killed copier and RFE.
keywords = crash, regression, dataloss, patch, easyfix, fixedinbranch,
fixedintrunk, ui, qtbug, fileformat, assertion, testcase, cosmetic,
release_notes, perf,
Jean-Marc Lasgouttes wrote:
> Next question: do we have a list of keywords somewhere?
We used to have one on bugzilla, but I guess it is lost.
> Currently I have
> keywords = crash,regression,patch,easyfix,fixedinbranch,fixedintrunk
ui, qtbug, fileformat, assertion, testcase, cosmetic, RFE (?),
Jürgen Spitzmüller writes:
> Vincent van Ravesteijn wrote:
>> There are only a few with a comma.
>
> Exactly 3, if my query was correct. Zero now.
Next question: do we have a list of keywords somewhere? Currently I have
keywords = crash,regression,patch,easyfix,fixedinbranch,fixedintrunk
What e
Vincent van Ravesteijn wrote:
> There are only a few with a comma.
Exactly 3, if my query was correct. Zero now.
Jürgen
Jean-Marc Lasgouttes schreef:
Jürgen Spitzmüller writes:
Jean-Marc Lasgouttes wrote:
http://trac-hacks.org/wiki/BatchModifyPlugin
It does not (yet) help in the given case, but I agree it would be useful in
general.
Also, do we want this one?
http://trac-hacks.org/wiki
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>> http://trac-hacks.org/wiki/BatchModifyPlugin
>
> It does not (yet) help in the given case, but I agree it would be useful in
> general.
>
>> Also, do we want this one?
>>
>> http://trac-hacks.org/wiki/KeywordSuggestPlugin
>
> Yes, this
Jean-Marc Lasgouttes wrote:
> http://trac-hacks.org/wiki/BatchModifyPlugin
It does not (yet) help in the given case, but I agree it would be useful in
general.
> Also, do we want this one?
>
> http://trac-hacks.org/wiki/KeywordSuggestPlugin
Yes, this would solve the keywords mess.
Also this on
Pavel Sanda wrote:
> maybe this is a good indication to stop use "fixedinbranch" and close the
> bugs directly?
We introduced these keywords for good reasons. Remember the user complaints
about "fixed" bugs that are not fixed yet in their newest release.
Jürgen
Le 3 juin 09 à 22:43, Jean-Marc Lasgouttes a écrit :
This plugin looks like what we want, but it seems that it does not
allow to close in batch.
Hmph
http://trac-hacks.org/wiki/BatchModifyPlugin
Also, do we want this one?
http://trac-hacks.org/wiki/KeywordSuggestPlugin
JMarc
Le 3 juin 09 à 19:10, Jürgen Spitzmüller a écrit :
AFAICS, there is no way in trac to change several tickets at once,
and the
server is so damn slow :-(
If you are in the mood, could you please help me resolving these
bugs? If I
have to do this alone, I might need hours.
http://www.lyx.org
Jürgen Spitzmüller wrote:
> AFAICS, there is no way in trac to change several tickets at once, and the
> server is so damn slow :-(
>
> If you are in the mood, could you please help me resolving these bugs? If I
> have to do this alone, I might need hours.
maybe this is a good indication to sto
AFAICS, there is no way in trac to change several tickets at once, and the
server is so damn slow :-(
If you are in the mood, could you please help me resolving these bugs? If I
have to do this alone, I might need hours.
http://www.lyx.org/trac/query?status=accepted&status=assigned&status=new&s
23 matches
Mail list logo
