Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> > have you killed those components already? (i see outliner add but no
> > component deleted...)
>
> Hell froze over, I have killed some components.
thanks
pavel
Pavel Sanda writes:
> have you killed those components already? (i see outliner add but no
> component deleted...)
Hell froze over, I have killed some components.
JMarc
Jean-Marc Lasgouttes wrote:
>
>>> have you killed those components already? (i see outliner add but no
>>> component deleted...)
>>
>> ping
>
> I'll come to it. But killing InsetCollapsable code is more funny.
ping :)
pavel
"Vincent van Ravesteijn - TNW" writes:
> Without these, the diagram becomes quite... trivial.
Yes.
> What about 'fixedinbranch', 'fixedintrunk' ? That is useful for the
> users to know.
Yes, but a bug can be in both states at the same time...
> It would be exciting when these will become real
> So, assuming that I used the correct trac.ini, the
> diagram I created and embedded on the following page,
>
> http://wiki.lyx.org/Devel/Administration#Trac_lifecycle
>
> should be our current workflow. Could you (Jean-Marc)
> verify that it's correct?
>
>It looks correct, although I do not think
Christian Ridderström writes:
> So, assuming that I used the correct trac.ini, the diagram I created
> and embedded on the following page,
>
> http://wiki.lyx.org/Devel/Administration#Trac_lifecycle
>
> should be our current workflow. Could you (Jean-Marc) verify that it's
> correct?
It looks cor
On Sun, 12 Jul 2009, Jean-Marc Lasgouttes wrote:
> Note that bugs are first NEW, and become assigned when someone
> accepts them. We could add a new unconfirmed state.
Do we have some diagram or similar that illustrates the life cycle of
issues? Perhaps useful to show to people reporting bug
have you killed those components already? (i see outliner add but
no component deleted...)
ping
I'll come to it. But killing InsetCollapsable code is more funny.
JMarc
Pavel Sanda wrote:
> Pavel Sanda wrote:
> > > >> frontend-* except qt4
> > > >> guii (move to frontend-qt4?)
> > >
> > > or keep separate frontend and frontend-qt4.
> >
> > if it was on me i would merge them.
> >
> > > >> lyxlex
> > >
> > > Why? (I just renamed it to lexer btw)
> >
> > i haven
Pavel Sanda wrote:
> > >> frontend-* except qt4
> > >> guii (move to frontend-qt4?)
> >
> > or keep separate frontend and frontend-qt4.
>
> if it was on me i would merge them.
>
> > >> lyxlex
> >
> > Why? (I just renamed it to lexer btw)
>
> i havent seen a single opened bug and cant remember
Le 12 juil. 09 à 20:26, Christian Ridderström a écrit :
Note that bugs are first NEW, and become assigned when someone
accepts them.
We could add a new unconfirmed state.
Do we have some diagram or similar that illustrates the life cycle
of issues? Perhaps useful to show to people report
Note that bugs are first NEW, and become assigned when someone accepts them.
We could add a new unconfirmed state.
Do we have some diagram or similar that illustrates the life cycle of
issues? Perhaps useful to show to people reporting bugs.
Similarly, are we writing a description of for w
On Fri, 10 Jul 2009, Jean-Marc Lasgouttes wrote:
Christian Ridderström writes:
I've never used 'website' myself, but I think it'd be good to have if
I ever do get around to using the issue tracking system for issues
related to the wiki/web site. Which I really should. In fact, given
that, I mi
Jean-Marc Lasgouttes wrote:
>> i dont need particularly "zombie". infoneeded is just fine.
>
> I'll add that.
infowanted is a typo?
pavel
Jean-Marc Lasgouttes wrote:
> No, but we need years old bugs without any activity, any CC, with
> reproducibility
> steps still opened.
ok
pavel
Le 12 juil. 09 à 15:34, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
I am not sure these bugs should be closed if they are real.
Having them
open is
useful for people reporting bugs.
do we need years old bugs without any activity, any CC (i'm not
talking about
enhacements) without re
Jean-Marc Lasgouttes wrote:
>>> We could add a new unconfirmed state.
>>
>> in the sense that
>> 1. its the first state of bug when entered
>> 2. checkbox unconfirmed checkbox is visible (and unchecked)
>> when doing custom query in trac?
>
> Well, maybe. But since it will require me to grok yet
Jean-Marc Lasgouttes wrote:
>>> I am not sure these bugs should be closed if they are real. Having them
>>> open is
>>> useful for people reporting bugs.
do we need years old bugs without any activity, any CC (i'm not talking about
enhacements) without reproducibility steps still opened?
>> i wan
Le 12 juil. 09 à 15:11, Pavel Sanda a écrit :
Note that bugs are first NEW, and become assigned when someone
accepts
them.
We could add a new unconfirmed state.
in the sense that
1. its the first state of bug when entered
2. checkbox unconfirmed checkbox is visible (and unchecked)
when doin
Jean-Marc Lasgouttes wrote:
> OK, I added both. Juergen is in charge of master/child and nobody is in
> charge of
> outliner.
thanks
>> 1. i would like to have new keyword, say "zombie". this would somehow
>> allow to
>> mimic "unconfirmed state" from bugzilla and i could also tag the bugs
>>
Le 12 juil. 09 à 14:03, Pavel Sanda a écrit :
Should master/child be a component or a keyword? I would think that
bugs
concern
component.
some special component everytime. We do not have an area of code
which is
master/child.
indeed, but they constitute itw own logical complex.
For ou
Jean-Marc Lasgouttes wrote:
> Le 10 juil. 09 ? 14:20, Pavel Sanda a écrit :
>>> What about creating an "obsolete" component and rename things like
>>> frontend-xforms or relyx to this?
>>
>> whats the merit?
>>
>> adding master/child and outliner is ok?
>
> Should master/child be a component or a k
Le 10 juil. 09 à 14:20, Pavel Sanda a écrit :
What about creating an "obsolete" component and rename things like
frontend-xforms or relyx to this?
whats the merit?
adding master/child and outliner is ok?
Should master/child be a component or a keyword? I would think that
bugs concern
some
Pavel Sanda wrote:
> of unfixed bugs to proper components, reseting old keywords should be ok now.)
old "components" of course
> it even seems that mails are not sent with this operation. so keep your hats i
> plan to do the massive priorities movement soon ;)
>
> pavel
Jean-Marc Lasgouttes wrote:
> it actually works reliably enough. This is the problems with all these
> plugins: they are not always actively maintained.
i just tried small experiment to move residual guii bugs into frontend-qt4
and everything seem to work well. (this also should finish the movemen
Pavel Sanda writes:
> Jean-Marc Lasgouttes wrote:
>> I think I have something for you. Try a custom query and tell me what
>> you think.
>
> bugza masta wow!
For the entertainment of others, what he sees now (and juergen sees it
too I think) is the batch ticket updater plugin.
http://trac-ha
Jean-Marc Lasgouttes wrote:
> I think I have something for you. Try a custom query and tell me what
> you think.
bugza masta wow!
pavel
Jean-Marc Lasgouttes wrote:
> >> i would simply reset it to general. imho these are clearly for removal:
> >>
> >> frontend-* except qt4
> >> guii (move to frontend-qt4?)
>
> or keep separate frontend and frontend-qt4.
if it was on me i would merge them.
> >> lyxlex
>
> Why? (I just renamed it
Pavel Sanda writes:
>> i would simply reset it to general. imho these are clearly for removal:
>>
>> frontend-* except qt4
>> guii (move to frontend-qt4?)
or keep separate frontend and frontend-qt4.
>> linuxdoc export
ok
>> lyxlex
Why? (I just renamed it to lexer btw)
>> relyx
ok
>> suppo
Christian Ridderström writes:
> I've never used 'website' myself, but I think it'd be good to have if
> I ever do get around to using the issue tracking system for issues
> related to the wiki/web site. Which I really should. In fact, given
> that, I might even want two separate components (or cat
Pavel Sanda writes:
> hah we are in a deadlock ;) i moved some but have waited for your nod
> which components to knock down.
>
> as for my coloring obsession i have though if there is possibility
> to communicate by trac via sql would it be possible to run some
> query which in the first run put
Pavel Sanda wrote:
> Pavel Sanda wrote:
> > > Yes, I can do that. You should maybe first reset the bugs that use that
> > > to "general" component (or a new "obsolete" component?)
> >
> > i would simply reset it to general. imho these are clearly for removal:
> >
> > frontend-* except qt4
> > gui
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> > JMarc, do you plan to update the components list?
>
> I was waiting to see whether you would first reaffect all those bugs to
> other components :) More seriously, I want to search a bit more whether
> there is a trac-approved way of getting r
Pavel Sanda writes:
> JMarc, do you plan to update the components list?
I was waiting to see whether you would first reaffect all those bugs to
other components :) More seriously, I want to search a bit more whether
there is a trac-approved way of getting rid of components.
JMarc
Christian Ridderström wrote:
> On Tue, 7 Jul 2009, Pavel Sanda wrote:
>
>> and these are for discussion - i dont remember them to be much used:
>>
>> minibuffer
>> website
>> lyxtext
>> lyxserver
>
> I've never used 'website' myself, but I think it'd be good to have if I
> ever do get around to us
On Tue, 7 Jul 2009, Pavel Sanda wrote:
and these are for discussion - i dont remember them to be much used:
minibuffer
website
lyxtext
lyxserver
I've never used 'website' myself, but I think it'd be good to have if I
ever do get around to using the issue tracking system for issues related
t
Pavel Sanda wrote:
> > Yes, I can do that. You should maybe first reset the bugs that use that
> > to "general" component (or a new "obsolete" component?)
>
> i would simply reset it to general. imho these are clearly for removal:
>
> frontend-* except qt4
> guii (move to frontend-qt4?)
> linuxdo
Pavel Sanda writes:
> Jean-Marc Lasgouttes wrote:
>> It is the place where you can add new reports (try to click on one and
>> click edit). The in a wiki page, the markup {1} will add report number
>> 1.
>
> do you have some special rights? there is no edit button here.
Err, you mean like TRAC_A
Jean-Marc Lasgouttes wrote:
> It is the place where you can add new reports (try to click on one and
> click edit). The in a wiki page, the markup {1} will add report number
> 1.
do you have some special rights? there is no edit button here.
pavel
Pavel Sanda writes:
> Jean-Marc Lasgouttes wrote:
>> Pavel Sanda writes:
>> > can you show me a simple wiki page which uses this?
>>
>> http://www.lyx.org/trac/report
>
> wiki page means you have means to edit it.
It is the place where you can add new reports (try to click on one and
click edi
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> > can you show me a simple wiki page which uses this?
>
> http://www.lyx.org/trac/report
wiki page means you have means to edit it.
pavel
Jean-Marc Lasgouttes wrote:
> Add "component!=general"?
already found this ;)
> > now for more important things - is it possible to kill some components
> > or at least to hide them from comboxes? i would see some canditates
> > for removal - they only clutter ui.
>
> Yes, I can do that. You sho
Pavel Sanda writes:
> can you show me a simple wiki page which uses this?
http://www.lyx.org/trac/report
JMarc
Pavel Sanda writes:
>> Why not just use group=component in the query?
>
> nice. still some issues ;) - no toc generated and some thing we dont want to
> see as the lngest general component.
Add "component!=general"?
> now for more important things - is it possible to kill some components
> o
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> > i found it would be very convenient when working with trac to have some fast
> > separation of bugs/enhacenment requests. as we havent find way how to tweak
> > colorings in the output i would like to turn enhacenment bugs priority field
> > in
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> > i setup this new wiki page, feel free to add components you are intersted
> > in:
> > http://www.lyx.org/trac/wiki/Components
>
> Why not just use group=component in the query?
nice. still some issues ;) - no toc generated and some thing we
Pavel Sanda writes:
> i setup this new wiki page, feel free to add components you are intersted in:
> http://www.lyx.org/trac/wiki/Components
Why not just use group=component in the query?
JMarc
Pavel Sanda writes:
> i found it would be very convenient when working with trac to have some fast
> separation of bugs/enhacenment requests. as we havent find way how to tweak
> colorings in the output i would like to turn enhacenment bugs priority field
> into 'lower' ones. its rather useless du
48 matches
Mail list logo
