Michael Gerz a écrit :
Jean-Marc Lasgouttes wrote:
Unicode has to go forward anyway. I'd think that 1.5 now would not
make sense (since qt4 and gtk are not ready). When they are ready,
we'll see how far the unicode work has gone.It may be that the LyX
meeting is what we need to get unicode goin
Jean-Marc Lasgouttes wrote:
Unicode has to go forward anyway. I'd think that 1.5 now would not
make sense (since qt4 and gtk are not ready). When they are ready,
we'll see how far the unicode work has gone.It may be that the LyX
meeting is what we need to get unicode going.
Abdel, do you have
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> I am not going for another round of being release manager for a
| Lars> release, se we need to appoint one. I think we should take turns
| Lars> on being release for differ
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> I am not going for another round of being release manager for a
Lars> release, se we need to appoint one. I think we should take turns
Lars> on being release for different releases.
This is a good idea indeed, if you find a vol
[EMAIL PROTECTED] writes:
| On 28 Apr 2006, Lars Gullik Bjønnes wrote:
|
| > I guess we should formalize our release procedure a tiny bit at the same
| > time. (Like a release checklist, pre-release period, getting people to
| > test, primary/secondary platforms/os etc)
|
| What exactly is invol
On 28 Apr 2006, Lars Gullik Bjønnes wrote:
> I guess we should formalize our release procedure a tiny bit at the same
> time. (Like a release checklist, pre-release period, getting people to
> test, primary/secondary platforms/os etc)
What exactly is involved in the release procedure today? A whi
Martin Vermeer <[EMAIL PROTECTED]> writes:
| On Fri, Apr 28, 2006 at 03:08:55PM +0200, Lars Gullik Bjønnes wrote:
| > Georg Baum <[EMAIL PROTECTED]> writes:
| >
| > | Lars Gullik Bjønnes wrote:
| > |
| > | > Then trunk will be unusable.
| > | > So currently that is not an options.
| > |
| > |
On Fri, Apr 28, 2006 at 03:08:55PM +0200, Lars Gullik Bjønnes wrote:
> Georg Baum <[EMAIL PROTECTED]> writes:
>
> | Lars Gullik Bjønnes wrote:
> |
> | > Then trunk will be unusable.
> | > So currently that is not an options.
> |
> | Why not?
>
> Becuase the unicode changes currently makes lyx
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Fri, Apr 28, 2006 at 02:48:49PM +0200, Lars Gullik Bjønnes wrote:
| > Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| >
| > | > (Wrt unicode, unless I get some help it will go
| > | > slowly forward.)
| > |
| > | I suspect you won't find any help if
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| Georg Baum a écrit :
| > Lars Gullik Bjønnes wrote:
| >
| >> Then trunk will be unusable.
| >> So currently that is not an options.
| > Why not? Both qt4 and gtk will progress slowly as stated by Abdel
| > and John,
| > so IMHO it does not make sen
On Fri, Apr 28, 2006 at 02:48:49PM +0200, Lars Gullik Bjønnes wrote:
> Abdelrazak Younes <[EMAIL PROTECTED]> writes:
>
> | > (Wrt unicode, unless I get some help it will go
> | > slowly forward.)
> |
> | I suspect you won't find any help if you don't push your changes into trunk.
>
> Then trunk
Jean-Marc Lasgouttes a écrit :
"Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> As a side note, IMHO, if unicode is going to
Abdelrazak> impact the frontends code a lot, we should really switch
Abdelrazak> to qt4 and let the qt3 stay unchanged. This way qt3 will
Abdelra
Lars Gullik Bjønnes wrote:
> When I have a hint of something that actually works I will move all to
> trunk.
Good.
> I am not taking feature complete, I am talking compiling,runnning and
> showing something recognizable on screen.
Even that would be no problem IMO if it came with an announcemen
> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes:
Abdelrazak> As a side note, IMHO, if unicode is going to
Abdelrazak> impact the frontends code a lot, we should really switch
Abdelrazak> to qt4 and let the qt3 stay unchanged. This way qt3 will
Abdelrazak> stay usable and qt4 wil
Georg Baum a écrit :
Lars Gullik Bjønnes wrote:
Then trunk will be unusable.
So currently that is not an options.
Why not? Both qt4 and gtk will progress slowly as stated by Abdel and John,
so IMHO it does not make sense to wait for these.
I am not sure Lars is waiting for qt4 or gtk to com
Georg Baum <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
|
| > Then trunk will be unusable.
| > So currently that is not an options.
|
| Why not?
Becuase the unicode changes currently makes lyx unusable.
| I personally have not yet checked out the unicode branch, but would probably
Lars Gullik Bjønnes wrote:
> Then trunk will be unusable.
> So currently that is not an options.
Why not? Both qt4 and gtk will progress slowly as stated by Abdel and John,
so IMHO it does not make sense to wait for these. Lots of other small stuff
that happens now falls IMHO in two categories:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
| > (Wrt unicode, unless I get some help it will go
| > slowly forward.)
|
| I suspect you won't find any help if you don't push your changes into trunk.
Then trunk will be unusable.
So currently that is not an options.
--
Lgb
Lars Gullik Bjønnes a écrit :
We also need to address the question wrt releasing 1.5 soon or wait
for "major" features.
Jean-Marc suggested that a complete port to Qt4 could justify a 1.5.0
release. I don't see that happening soon as Potential Qt developers (me
included) don't seem to have ti
I am not going for another round of being release manager for a
release, se we need to appoint one. I think we should take turns on
being release for different releases.
In that vein I also propose that the release manager, continues to
manage 1.X.x releases.
On trunk the release manager will no
20 matches
Mail list logo
