Re: Preparing for rc1

2008-08-04 Thread Anders Ekberg
Unfortunately I've never got the universal part to work and don't have time to dive into it. I hope Konrad has the possibility to create a universal installer. Meanwhile I have put a zipped 1.6rc1 Intel-binary (without installer) on http://homepage.mac.com/anek/Temp/FileSharing24.html for th

Re: Preparing for rc1

2008-08-01 Thread Bennett Helm
On Fri, Aug 1, 2008 at 2:39 PM, José Matos <[EMAIL PROTECTED]> wrote: >I would like to release a first candidate to rc1 next Monday, this > follows > our agreed schedule where RC1 was planned for today. If all goes well I > would > like to release on Tuesday or Wednesday. I won't be able

Preparing for rc1

2008-08-01 Thread José Matos
Hello, I have turned on the release flag for rc1. I have done that in order to guarantee that we are building/running lyx with the same compiler flags used to build rc1. Not only that but I have been using lyx-1.6.0 for my daily work for the last week. So far I like what I see.

Re: Preparing for rc1

2008-07-04 Thread Jürgen Spitzmüller
Abdelrazak Younes wrote: > Do we have a list of such bugs? They should be marked as blocker so that > they appear in this list: Actually, the only really crucial one is this: http://bugzilla.lyx.org/show_bug.cgi?id=4927 Another candidate is this: http://bugzilla.lyx.org/show_bug.cgi?id=4812 (coul

Re: Preparing for rc1

2008-07-04 Thread Pavel Sanda
Abdelrazak Younes wrote: > Jürgen Spitzmüller wrote: >> José Matos wrote: >> >>> That is fair, so the criteria to change from beta to rc is the >>> (in)existence of data loss bugs? >>> >> >> I'd say so. >> > > Do we have a list of such bugs? They should be marked as blocker so that > th

Re: Preparing for rc1

2008-07-04 Thread Pavel Sanda
Jürgen Spitzmüller wrote: > José Matos wrote: > > That is fair, so the criteria to change from beta to rc is the > > (in)existence of data loss bugs? > > I'd say so. i added it here http://www.lyx.org/VersioningSystem pavel

Re: Preparing for rc1

2008-07-04 Thread Abdelrazak Younes
Jürgen Spitzmüller wrote: José Matos wrote: That is fair, so the criteria to change from beta to rc is the (in)existence of data loss bugs? I'd say so. Do we have a list of such bugs? They should be marked as blocker so that they appear in this list: http://tinyurl.com/5au5uz

Re: Preparing for rc1

2008-07-04 Thread Jürgen Spitzmüller
José Matos wrote: > That is fair, so the criteria to change from beta to rc is the > (in)existence of data loss bugs? I'd say so. > Nevertheless we are now in bug fix mode only, I know this is consensual I > am just stating it explicitly. :-) This is a very good decision. Jürgen

Re: Preparing for rc1

2008-07-04 Thread José Matos
On Friday 04 July 2008 11:16:07 Jürgen Spitzmüller wrote: > I agree. Most notably, we have _dataloss_ bugs. I think those should be > fixed before we release something tagged _release candidate_. That is fair, so the criteria to change from beta to rc is the (in)existence of data loss bugs? Neve

Re: Preparing for rc1

2008-07-04 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: What I do not quite understand, is why the second window should have a size different from the first one's? As I said, I don't really care. But what about the third? Should it have the same size as the curre

Re: Preparing for rc1

2008-07-04 Thread Jean-Marc Lasgouttes
Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> What I do not quite understand, is why the second window should have a >> size different from the first one's? >> > As I said, I don't really care. But what about the third? Should it > have the same size as the current window or as the first one

Re: Preparing for rc1

2008-07-04 Thread Abdelrazak Younes
[EMAIL PROTECTED] wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: But there is no way to decide what is the size of these new windows, then? Right, we could add this information to "default.ui" instead of hardcoding it with a line like this: geometry 690 510 50 50 What

Re: Preparing for rc1

2008-07-04 Thread lasgouttes
Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> But there is no way to decide what is the size of these new windows, >> then? >> > Right, we could add this information to "default.ui" instead of > hardcoding it with a line like this: > > geometry 690 510 50 50 What I do not quite understand, i

Re: Preparing for rc1

2008-07-04 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: Another thing I never get to ask: when I open LyX, the window has the size kept in session file. Fine. But now, when I create a new window, I get another default size. Is there a reason for that? That seemed a s

Re: Preparing for rc1

2008-07-04 Thread Jean-Marc Lasgouttes
Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> Another thing I never get to ask: when I open LyX, the window has the >> size kept in session file. Fine. But now, when I create a new window, >> I get another default size. Is there a reason for that? > > That seemed a sane default behaviour to me.

Re: Preparing for rc1

2008-07-04 Thread Abdelrazak Younes
Pavel Sanda wrote: Abdelrazak Younes wrote: speaking about 'only bugfixes' do you still plan to change the underlying key handling ? That would just be a refactoring of the key handling support functions so this is still bugfixing in my definition. in terms of stability the

Re: Preparing for rc1

2008-07-04 Thread Abdelrazak Younes
Jean-Marc Lasgouttes wrote: Abdelrazak Younes <[EMAIL PROTECTED]> writes: btw Abdel, what are your plans wrt http://bugzilla.lyx.org/show_bug.cgi?id=4888 ? Fix it when I find the time :-) Another thing I never get to ask: when I open LyX, the window has the size kept in se

Re: Preparing for rc1

2008-07-04 Thread Jean-Marc Lasgouttes
Abdelrazak Younes <[EMAIL PROTECTED]> writes: >> btw Abdel, what are your plans wrt >> http://bugzilla.lyx.org/show_bug.cgi?id=4888 ? >> > > Fix it when I find the time :-) Another thing I never get to ask: when I open LyX, the window has the size kept in session file. Fine. But now, when I c

Re: Preparing for rc1

2008-07-04 Thread Jürgen Spitzmüller
Abdelrazak Younes wrote: > Agreed for 'only bugfixes'. But as for tagging it rc1 I am not sure as > we have a number of major and critical bugs still, 14 to be exact: > > *http://tinyurl.com/5au5uz I agree. Most notably, we have _dataloss_ bugs. I think those should be fixed before we release som

Re: Preparing for rc1

2008-07-04 Thread Pavel Sanda
Abdelrazak Younes wrote: >> speaking about 'only bugfixes' do you still plan to change the underlying >> key handling ? >> > That would just be a refactoring of the key handling support functions so > this is still bugfixing in my definition. in terms of stability the refactoring or 'shuffle

Re: Preparing for rc1

2008-07-04 Thread Abdelrazak Younes
Pavel Sanda wrote: Abdelrazak Younes wrote: José Matos wrote: Hi, I think that we are ready to go with the first rc1. So that means that from now on no more features are allowed, only bugfixes. Agreed for 'only bugfixes'. But as for tagging it rc1 I am not sure as we have a

Re: Preparing for rc1

2008-07-04 Thread Pavel Sanda
Abdelrazak Younes wrote: > José Matos wrote: >> Hi, >> I think that we are ready to go with the first rc1. So that means that >> from now on no more features are allowed, only bugfixes. >> > > Agreed for 'only bugfixes'. But as for tagging it rc1 I am not sure as we > have a number of maj

Re: Preparing for rc1

2008-07-04 Thread Abdelrazak Younes
José Matos wrote: Hi, I think that we are ready to go with the first rc1. So that means that from now on no more features are allowed, only bugfixes. Agreed for 'only bugfixes'. But as for tagging it rc1 I am not sure as we have a number of major and critical bugs still, 14 to be exact:

Preparing for rc1

2008-07-04 Thread José Matos
Hi, I think that we are ready to go with the first rc1. So that means that from now on no more features are allowed, only bugfixes. I propose to release rc1 next Tuesday. Enjoy the weekend, and the holiday if you are American, and let us announce the best lyx to date. ;-) --