On Tue, Feb 15, 2005 at 11:08:45AM +0100, Lars Gullik Bjønnes wrote:
Asger Alstrup [EMAIL PROTECTED] writes:
| Andre Poenitz wrote:
On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
If there is interest and if things evolve positively, I may be able to
propose Paris
Andre Poenitz [EMAIL PROTECTED] writes:
| [BTW, do we have still have Intra-EU regulations on the amount of beer
| one is allowed to transport from one country to another?]
Yes, but is now somtehing like 150 litres
--
Lgb
On Tue, Feb 15, 2005 at 11:08:45AM +0100, Lars Gullik Bjønnes wrote:
> Asger Alstrup <[EMAIL PROTECTED]> writes:
>
> | Andre Poenitz wrote:
> >> On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
> >>>If there is interest and if things evolve positively, I may be able to
> >>>
Andre Poenitz <[EMAIL PROTECTED]> writes:
| [BTW, do we have still have Intra-EU regulations on the amount of beer
| one is allowed to transport from one country to another?]
Yes, but is now somtehing like 150 litres
--
Lgb
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
| Paris sounds great!
Lars Except for the beer... but I can settle for some wine as well.
Sure, beer is not a big selling point.
Lars I think you just got selected by acclamation, Jean-Marc.
Hmm, well, let's see what I can do.
JMarc
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| Paris sounds great!
Lars> Except for the beer... but I can settle for some wine as well.
Sure, beer is not a big selling point.
Lars> I think you just got selected by acclamation, Jean-Marc.
Hmm, well, let's see what I can do.
Andre Poenitz wrote:
On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
If there is interest and if things evolve positively, I may be able to
propose Paris
Both sound nice. [And in case it matters: I am a bit biased towards
France outside Paris...]
Paris sounds great!
Regards,
On Monday 14 February 2005 16:17, Jean-Marc Lasgouttes wrote:
Interested?
Certainly. :-)
JMarc
--
José Abílio
Asger Alstrup [EMAIL PROTECTED] writes:
| Andre Poenitz wrote:
On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
If there is interest and if things evolve positively, I may be able to
propose Paris
Both sound nice. [And in case it matters: I am a bit biased towards
France
Andre Poenitz wrote:
On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
If there is interest and if things evolve positively, I may be able to
propose Paris
Both sound nice. [And in case it matters: I am a bit biased towards
France outside Paris...]
Paris sounds great!
Regards,
On Monday 14 February 2005 16:17, Jean-Marc Lasgouttes wrote:
> Interested?
Certainly. :-)
> JMarc
--
José Abílio
Asger Alstrup <[EMAIL PROTECTED]> writes:
| Andre Poenitz wrote:
>> On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
>>>If there is interest and if things evolve positively, I may be able to
>>> propose Paris
>> Both sound nice. [And in case it matters: I am a bit biased
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
Andre On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes
Andre wrote:
We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I
hope this still holds...
Andre Apropos Chemnitz. Where do we go this year?
If there is
On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
Andre == Andre Poenitz [EMAIL PROTECTED] writes:
Andre On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes
Andre wrote:
We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I
hope this still
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes
Andre> wrote:
>> We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I
>> hope this still holds...
Andre> Apropos Chemnitz. Where do we go this year?
If
On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
> > "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> Andre> On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes
> Andre> wrote:
> >> We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I
>
On Thu, Feb 10, 2005 at 01:06:45PM +0100, Lars Gullik Bjønnes wrote:
It might be that I am a bit out.
But I see no bug problems in CVS currently.
What must be fixed for 1.4.0?
(and bugzilla is not up to snuff...)
I'd like all code-cleanup, feature-fixing etc to stop now and go into
On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes wrote:
We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I
hope this still holds...
Apropos Chemnitz. Where do we go this year?
Andre'
On Thu, Feb 10, 2005 at 08:01:55PM +0100, Michael Schmitt wrote:
What I am most concerned about is: Will there be any fundamental code
changes right after the release of LyX 1.4?
I would guess people will have a shot at XML file format which will
probably change (and hopefully simplify) most of
On Fri, Feb 11, 2005 at 10:18:25PM +0100, Andre Poenitz wrote:
What I am most concerned about is: Will there be any fundamental code
changes right after the release of LyX 1.4?
I would guess people will have a shot at XML file format which will
probably change (and hopefully simplify)
On Thu, Feb 10, 2005 at 01:06:45PM +0100, Lars Gullik Bjønnes wrote:
>
> It might be that I am a bit "out".
>
> But I see no bug problems in CVS currently.
> What must be fixed for 1.4.0?
>
> (and bugzilla is not up to snuff...)
>
> I'd like all code-cleanup, feature-fixing etc to stop now and
On Thu, Feb 10, 2005 at 09:50:40PM +0100, Jean-Marc Lasgouttes wrote:
> We agreed in Chemnitz to delay the 1.5 branch until 1.4.1 is out. I
> hope this still holds...
Apropos Chemnitz. Where do we go this year?
Andre'
On Thu, Feb 10, 2005 at 08:01:55PM +0100, Michael Schmitt wrote:
> What I am most concerned about is: Will there be any fundamental code
> changes right after the release of LyX 1.4?
I would guess people will have a shot at XML file format which will
probably change (and hopefully simplify) most
On Fri, Feb 11, 2005 at 10:18:25PM +0100, Andre Poenitz wrote:
> > What I am most concerned about is: Will there be any fundamental code
> > changes right after the release of LyX 1.4?
>
> I would guess people will have a shot at XML file format which will
> probably change (and hopefully
Jürgen wrote:
Jean-Marc Lasgouttes wrote:
We have to decide what to do about change tracking.
I think we can ship 1.4 with change tracking. The status is not worse (even a
bit better) than the unofficial 1.3 version that has been distributed
separately, and AFAIK people have used that for
Johnathan Burchill wrote:
Change-tracking itself probably does not need a major rewrite. It's the
cut-and-paste code that needs to be thought-out.
Yes, that's what I meant.
I will look into HEAD this weekend, and report back to the list.
That'd be great.
Thanks,
Jürgen
Jürgen wrote:
>Jean-Marc Lasgouttes wrote:
>> We have to decide what to do about change tracking.
>
>I think we can ship 1.4 with change tracking. The status is not worse (even a
>bit better) than the unofficial 1.3 version that has been distributed
>separately, and AFAIK people have used that
Johnathan Burchill wrote:
> Change-tracking itself probably does not need a major rewrite. It's the
> cut-and-paste code that needs to be thought-out.
Yes, that's what I meant.
> I will look into HEAD this weekend, and report back to the list.
That'd be great.
Thanks,
Jürgen
It might be that I am a bit out.
But I see no bug problems in CVS currently.
What must be fixed for 1.4.0?
(and bugzilla is not up to snuff...)
I'd like all code-cleanup, feature-fixing etc to stop now and go into
hard freeze and only fix regressions and crashes.
--
Lgb
Lars Gullik Bjønnes wrote:
It might be that I am a bit out.
But I see no bug problems in CVS currently.
What must be fixed for 1.4.0?
(and bugzilla is not up to snuff...)
I'd say the important ones are targeted for MILESTONE 1.4.0
(IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the
Lars Gullik Bjnnes [EMAIL PROTECTED] writes:
It might be that I am a bit out.
But I see no bug problems in CVS currently.
What must be fixed for 1.4.0?
Currently I have problems with crashes related to fast events
and previews/forked processes.
For example, when I start LyX, open the
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars But I see no bug problems in CVS currently. What must be fixed
Lars for 1.4.0?
Lars I'd like all code-cleanup, feature-fixing etc to stop now and go
Lars into hard freeze and only fix regressions and crashes.
One thing I see that may
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
| Lars But I see no bug problems in CVS currently. What must be fixed
| Lars for 1.4.0?
| Lars I'd like all code-cleanup, feature-fixing etc to stop now and go
| Lars into hard freeze and only
Juergen Spitzmueller [EMAIL PROTECTED] writes:
I'd say the important ones are targeted for MILESTONE 1.4.0
(IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with
inInset [e.g., when the document has a caption outside a float], which is not
yet in bugzilla).
When I
Andreas Vox [EMAIL PROTECTED] writes:
| Juergen Spitzmueller [EMAIL PROTECTED] writes:
I'd say the important ones are targeted for MILESTONE 1.4.0
(IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with
inInset [e.g., when the document has a caption outside a float], which
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
One thing I see that may need big changes is that selecting with the
mouse is terribly slow.
Can't confirm that for LyX/Aqua.
/Andreas
Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars Then we should work on fixing these regressions, but improving
Lars any other feature that we have.
Yes.
Lars I'll have a look at the double click issue.
OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not
sure it is
Lars Gullik Bjnnes [EMAIL PROTECTED] writes:
If they are not marked with taget 1.4.0 then I don't see them.
(and if they are not marked, they need to be verified to be present on
1.4.0)
??
So open bugs which should be fixed for target 1.3.6 wont get fixed for
target 1.4.0? I'm not sure if I
Jean-Marc Lasgouttes wrote:
We have to decide what to do about change tracking.
I think we can ship 1.4 with change tracking. The status is not worse (even a
bit better) than the unofficial 1.3 version that has been distributed
separately, and AFAIK people have used that for their daily work.
Andreas Vox [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
If they are not marked with taget 1.4.0 then I don't see them.
(and if they are not marked, they need to be verified to be present on
1.4.0)
| ??
| So open bugs which should be fixed for target 1.3.6 wont
Andreas == Andreas Vox [EMAIL PROTECTED] writes:
Andreas Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
If they are not marked with taget 1.4.0 then I don't see them. (and
if they are not marked, they need to be verified to be present on
1.4.0)
Andreas ?? So open bugs which should be fixed
Lars Gullik Bjnnes [EMAIL PROTECTED] writes:
Me neither perhaps.
We have some 250 open bugs, but no idea if they exist in 1.3.x or in
HEAD. We need to be able to mark the bugs so that we know what to work
on.
So maybe we should use a wiki TODO list once more. My proposal:
- bugs 1119,
Andreas == Andreas Vox [EMAIL PROTECTED] writes:
Andreas - set PATH_prefix in lib/configure for Mac (Bennet complained
Andreas about this. As it is now, LyX won't work out of the box on
Andreas Mac)
The other solution is to preset this in the preferences file, as is
done currently for
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
Andreas == Andreas Vox [EMAIL PROTECTED] writes:
Andreas - set PATH_prefix in lib/configure for Mac (Bennet complained
Andreas about this. As it is now, LyX won't work out of the box on
Andreas Mac)
The other solution is to preset this in
On Feb 10, 2005, at 10:31 AM, Jean-Marc Lasgouttes wrote:
Andreas == Andreas Vox [EMAIL PROTECTED] writes:
Andreas - set PATH_prefix in lib/configure for Mac (Bennet complained
Andreas about this. As it is now, LyX won't work out of the box on
Andreas Mac)
The other solution is to preset this in
Andreas Vox [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Me neither perhaps.
We have some 250 open bugs, but no idea if they exist in 1.3.x or in
HEAD. We need to be able to mark the bugs so that we know what to work
on.
| So maybe we should use a wiki TODO
On Thursday 10 February 2005 15:42, Andreas Vox wrote:
Note that nothing that needs a format change will be accepted after
1.4.0. So be sure that you plan ahead.
No file format change is needed.
Just want to polish, not to re-forge :-) It's mainly the bitmap
generation for equations,
Bennett Helm [EMAIL PROTECTED] writes:
Is it possible to include all of these in the preference file? --
Simply entering
/usr/local/teTeX/bin/powerpc-apple-darwin-current:/opt/local/teTeX/bin:
/sw/bin doesn't seem to do it.
Why? I just tested adding a non-existing directory to my
On Feb 10, 2005, at 10:59 AM, Andreas Vox wrote:
Bennett Helm [EMAIL PROTECTED] writes:
Is it possible to include all of these in the preference file? --
Simply entering
/usr/local/teTeX/bin/powerpc-apple-darwin-current:/opt/local/teTeX/
bin:
/sw/bin doesn't seem to do it.
Why? I just tested
On Thu, Feb 10, 2005 at 03:51:56PM +0100, Lars Gullik Bj?nnes wrote:
We have some 250 open bugs, but no idea if they exist in 1.3.x or in
HEAD. We need to be able to mark the bugs so that we know what to work
on.
If there's not marked with 'fixedintrunk', then they're probably still
there...
On Thu, Feb 10, 2005 at 04:24:07PM +0100, Jean-Marc Lasgouttes wrote:
A possibility is to search for bugs reported against 1.4.0cvs.
I used to try mark regressions with 'regression'.
Whilst I don't have time to re-learn all the internals of LyX, I can
certainly try to do some triage...
Am Donnerstag, 10. Februar 2005 16:32 schrieb Juergen Spitzmueller:
quite a bunch of them are fixedintrunk.
I think we should resolve these bugs to avoid mistakes like this. Either
as WONTFIX (because they won't be fixed in 1.3, I'd prefer that) or as
FIXED.
Georg
On Thu, Feb 10, 2005 at 06:12:06PM +0100, Georg Baum wrote:
I think we should resolve these bugs to avoid mistakes like this. Either
as WONTFIX (because they won't be fixed in 1.3, I'd prefer that) or as
FIXED.
I don't think we should mark fixed bugs as WONTFIX, that's just too
unclear.
OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not
sure it is going to get used.
For 1.3.0 we had Michael's bug list which was very useful.
And this Michael is still alive and waits for a sign to start testing now
that LyX can be used on the Windows platform... :-)
Michael
I think we can ship 1.4 with change tracking. The status is not worse
(even a
bit better) than the unofficial 1.3 version that has been distributed
separately, and AFAIK people have used that for their daily work.
I would also like to see change tracking in LyX 1.4. Actually, this feature
alone
Am Donnerstag, 10. Februar 2005 13:06 schrieb Lars Gullik Bjønnes:
It might be that I am a bit out.
But I see no bug problems in CVS currently.
What must be fixed for 1.4.0?
I have some changes to tex2lyx that are basically finished but need some
testing that I would like to see in 1.4.
Michael == Michael Schmitt [EMAIL PROTECTED] writes:
Michael What I am most concerned about is: Will there be any
Michael fundamental code changes right after the release of LyX 1.4?
Michael Or in other words: Can we guarantee that the remaining open
Michael bugs can be fixed (easily) in the
Michael == Michael Schmitt [EMAIL PROTECTED] writes:
OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not
sure it is going to get used.
For 1.3.0 we had Michael's bug list which was very useful.
Michael And this Michael is still alive and waits for a sign to start
Michael
It might be that I am a bit "out".
But I see no bug problems in CVS currently.
What must be fixed for 1.4.0?
(and bugzilla is not up to snuff...)
I'd like all code-cleanup, feature-fixing etc to stop now and go into
hard freeze and only fix regressions and crashes.
--
Lgb
Lars Gullik Bjønnes wrote:
> It might be that I am a bit "out".
>
> But I see no bug problems in CVS currently.
> What must be fixed for 1.4.0?
>
> (and bugzilla is not up to snuff...)
I'd say the important ones are targeted for MILESTONE 1.4.0
(IMO, especially 1598, 1411, 1667, 1764, 1765, 1787
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes:
>
> It might be that I am a bit "out".
>
> But I see no bug problems in CVS currently.
> What must be fixed for 1.4.0?
Currently I have problems with crashes related to fast events
and previews/forked processes.
For example, when I start LyX,
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> But I see no bug problems in CVS currently. What must be fixed
Lars> for 1.4.0?
Lars> I'd like all code-cleanup, feature-fixing etc to stop now and go
Lars> into hard freeze and only fix regressions and crashes.
One thing I
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
| Lars> But I see no bug problems in CVS currently. What must be fixed
| Lars> for 1.4.0?
>
| Lars> I'd like all code-cleanup, feature-fixing etc to stop now and go
| Lars> into
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
> I'd say the important ones are targeted for MILESTONE 1.4.0
> (IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with
> inInset [e.g., when the document has a caption outside a float], which is not
> yet in bugzilla).
When I
Andreas Vox <[EMAIL PROTECTED]> writes:
| Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
>
>
>> I'd say the important ones are targeted for MILESTONE 1.4.0
>> (IMO, especially 1598, 1411, 1667, 1764, 1765, 1787 and the crashes with
>> inInset [e.g., when the document has a caption outside a
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> One thing I see that may need big changes is that selecting with the
> mouse is terribly slow.
Can't confirm that for LyX/Aqua.
/Andreas
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Then we should work on fixing these regressions, but improving
Lars> any other feature that we have.
Yes.
Lars> I'll have a look at the double click issue.
OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes:
> If they are not marked with taget 1.4.0 then I don't see them.
> (and if they are not marked, they need to be verified to be present on
> 1.4.0)
??
So open bugs which should be fixed for target 1.3.6 wont get fixed for
target 1.4.0? I'm not sure
Jean-Marc Lasgouttes wrote:
> We have to decide what to do about change tracking.
I think we can ship 1.4 with change tracking. The status is not worse (even a
bit better) than the unofficial 1.3 version that has been distributed
separately, and AFAIK people have used that for their daily work.
Andreas Vox <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
>> If they are not marked with taget 1.4.0 then I don't see them.
>> (and if they are not marked, they need to be verified to be present on
>> 1.4.0)
>
| ??
| So open bugs which should be fixed for target
> "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes:
Andreas> Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>> If they are not marked with taget 1.4.0 then I don't see them. (and
>> if they are not marked, they need to be verified to be present on
>> 1.4.0)
Andreas> ?? So open bugs which
Lars Gullik BjÃnnes <[EMAIL PROTECTED]> writes:
> Me neither perhaps.
>
> We have some 250 open bugs, but no idea if they exist in 1.3.x or in
> HEAD. We need to be able to mark the bugs so that we know what to work
> on.
>
So maybe we should use a wiki TODO list once more. My proposal:
-
> "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes:
Andreas> - set PATH_prefix in lib/configure for Mac (Bennet complained
Andreas> about this. As it is now, LyX won't work out of the box on
Andreas> Mac)
The other solution is to preset this in the preferences file, as is
done currently
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
> > "Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes:
>
> Andreas> - set PATH_prefix in lib/configure for Mac (Bennet complained
> Andreas> about this. As it is now, LyX won't work out of the box on
> Andreas> Mac)
>
> The other
On Feb 10, 2005, at 10:31 AM, Jean-Marc Lasgouttes wrote:
"Andreas" == Andreas Vox <[EMAIL PROTECTED]> writes:
Andreas> - set PATH_prefix in lib/configure for Mac (Bennet complained
Andreas> about this. As it is now, LyX won't work out of the box on
Andreas> Mac)
The other solution is to preset
Andreas Vox <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
>> Me neither perhaps.
>>
>> We have some 250 open bugs, but no idea if they exist in 1.3.x or in
>> HEAD. We need to be able to mark the bugs so that we know what to work
>> on.
>>
>
| So maybe we
On Thursday 10 February 2005 15:42, Andreas Vox wrote:
> > Note that nothing that needs a format change will be accepted after
> > 1.4.0. So be sure that you plan ahead.
No file format change is needed.
> Just want to polish, not to re-forge :-) It's mainly the bitmap
> generation for
Bennett Helm <[EMAIL PROTECTED]> writes:
>
> Is it possible to include all of these in the preference file? --
> Simply entering
> /usr/local/teTeX/bin/powerpc-apple-darwin-current:/opt/local/teTeX/bin:
> /sw/bin doesn't seem to do it.
Why? I just tested adding a non-existing directory to
On Feb 10, 2005, at 10:59 AM, Andreas Vox wrote:
Bennett Helm <[EMAIL PROTECTED]> writes:
Is it possible to include all of these in the preference file? --
Simply entering
/usr/local/teTeX/bin/powerpc-apple-darwin-current:/opt/local/teTeX/
bin:
/sw/bin doesn't seem to do it.
Why? I just tested
On Thu, Feb 10, 2005 at 03:51:56PM +0100, Lars Gullik Bj?nnes wrote:
> We have some 250 open bugs, but no idea if they exist in 1.3.x or in
> HEAD. We need to be able to mark the bugs so that we know what to work
> on.
If there's not marked with 'fixedintrunk', then they're probably still
On Thu, Feb 10, 2005 at 04:24:07PM +0100, Jean-Marc Lasgouttes wrote:
> A possibility is to search for bugs reported against 1.4.0cvs.
I used to try mark regressions with 'regression'.
Whilst I don't have time to re-learn all the internals of LyX, I can
certainly try to do some triage...
Am Donnerstag, 10. Februar 2005 16:32 schrieb Juergen Spitzmueller:
> quite a bunch of them are fixedintrunk.
I think we should resolve these bugs to avoid mistakes like this. Either
as WONTFIX (because they won't be fixed in 1.3, I'd prefer that) or as
FIXED.
Georg
On Thu, Feb 10, 2005 at 06:12:06PM +0100, Georg Baum wrote:
> I think we should resolve these bugs to avoid mistakes like this. Either
> as WONTFIX (because they won't be fixed in 1.3, I'd prefer that) or as
> FIXED.
I don't think we should mark fixed bugs as WONTFIX, that's just too
unclear.
OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not
sure it is going to get used.
For 1.3.0 we had Michael's bug list which was very useful.
And this Michael is still alive and waits for a sign to start testing now
that LyX can be used on the Windows platform... :-)
Michael
I think we can ship 1.4 with change tracking. The status is not worse
(even a
bit better) than the unofficial 1.3 version that has been distributed
separately, and AFAIK people have used that for their daily work.
I would also like to see change tracking in LyX 1.4. Actually, this feature
alone
Am Donnerstag, 10. Februar 2005 13:06 schrieb Lars Gullik Bjønnes:
>
> It might be that I am a bit "out".
>
> But I see no bug problems in CVS currently.
> What must be fixed for 1.4.0?
I have some changes to tex2lyx that are basically finished but need some
testing that I would like to see in
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
Michael> What I am most concerned about is: Will there be any
Michael> fundamental code changes right after the release of LyX 1.4?
Michael> Or in other words: Can we guarantee that the remaining open
Michael> bugs can be fixed
> "Michael" == Michael Schmitt <[EMAIL PROTECTED]> writes:
>> OK. We could maybe open a 1.4.0 TODO list on the wiki, but I am not
>> sure it is going to get used.
>>
>> For 1.3.0 we had Michael's bug list which was very useful.
Michael> And this Michael is still alive and waits for a sign
88 matches
Mail list logo
