Luis Rivera wrote:
I think I have the squasher somewhere... let me see... do we have the
NewAPI.h patch somewhere in the cvs tree? Where should I look for to see
the existing patches?
The NewAPI.h patch is already in the code base. However, from what I
understand, it, or our use of it, is
Luis Rivera wrote:
> I think I have the squasher somewhere... let me see... do we have the
> NewAPI.h patch somewhere in the cvs tree? Where should I look for to see
> the existing patches?
The NewAPI.h patch is already in the code base. However, from what I
understand, it, or our use of it, is
On Fri, Nov 11, 2005 at 11:58:45PM +, Luis Rivera wrote:
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
Alex == Alex [EMAIL PROTECTED] writes:
Alex Dear All, I would like to ask when the 1.3.7 version is going
to Alex be released?
There is no deadline yet,
Actually,
Dear Andre,
In my opinion there is no need to delay a release due to troubles
with some outdated platform.
The bugfix is important, some user cannot upgrade OS, due to a reason over
them.
And there is no need for the core developers to spend time on that
issue at all. If some Win95 wants
Alex wrote:
In my opinion there is no need to delay a release due to troubles
with some outdated platform.
The bugfix is important, some user cannot upgrade OS, due to a reason
over them.
And there is no need for the core developers to spend time on that
issue at all. If some Win95 wants
On Fri, Nov 11, 2005 at 11:58:45PM +, Luis Rivera wrote:
> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
> >
> > > "Alex" == Alex <[EMAIL PROTECTED]> writes:
> >
> > Alex> Dear All, I would like to ask when the 1.3.7 version is going
> > to Alex> be released?
> >
> > There is no
Dear Andre,
> In my opinion there is no need to delay a release due to troubles
> with some outdated platform.
The bugfix is important, some user cannot upgrade OS, due to a reason over
them.
> And there is no need for the core developers to spend time on that
> issue at all. If some Win95
Alex wrote:
>> In my opinion there is no need to delay a release due to troubles
>> with some outdated platform.
> The bugfix is important, some user cannot upgrade OS, due to a reason
> over them.
>> And there is no need for the core developers to spend time on that
>> issue at all. If some
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
Alex == Alex [EMAIL PROTECTED] writes:
Alex Dear All, I would like to ask when the 1.3.7 version is going to
Alex be released?
There is no deadline yet,
Actually, I am not very good at planning releases and warning
everybody. So it is
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
> > "Alex" == Alex <[EMAIL PROTECTED]> writes:
>
> Alex> Dear All, I would like to ask when the 1.3.7 version is going to
> Alex> be released?
>
> There is no deadline yet,
>
> Actually, I am not very good at planning releases and
Alex == Alex [EMAIL PROTECTED] writes:
Alex Ok. Here I send you the current version. It is just after
Alex several bugfix. I don't want to send every day, just after
Alex major updates. :) E.g. only after updating 50 or 100 strings or
Alex similar. We will see.
Very good. It is in now.
Alex
Dear Jean-Marc,
Alex Ok. Here I send you the current version. It is just after
Alex several bugfix. I don't want to send every day, just after
Alex major updates. :) E.g. only after updating 50 or 100 strings or
Alex similar. We will see.
Very good. It is in now.
Alex Anyway, after the XForms
> "Alex" == Alex <[EMAIL PROTECTED]> writes:
Alex> Ok. Here I send you the current version. It is just after
Alex> several "bugfix". I don't want to send every day, just after
Alex> major updates. :) E.g. only after updating 50 or 100 strings or
Alex> similar. We will see.
Very good. It is
Dear Jean-Marc,
Alex>> Ok. Here I send you the current version. It is just after
Alex>> several "bugfix". I don't want to send every day, just after
Alex>> major updates. :) E.g. only after updating 50 or 100 strings or
Alex>> similar. We will see.
> Very good. It is in now.
Alex>> Anyway,
:). Remember the mantra ``release
early, release often''.
Actually, I am not very good at planning releases and warning
everybody. So it is safer to avoid waiting. Currently, I guess 1.3.7
will be released when we know for sure that the 1.4.0 format will not
evolve anymore. But if a bad bug turns up
do not object to doing several updates of
translations (not everyday, maybe :). Remember the mantra ``release
early, release often''.
Actually, I am not very good at planning releases and warning
everybody. So it is safer to avoid waiting. Currently, I guess 1.3.7
will be released when we know
Dear All,
I would like to ask when the 1.3.7 version is going to be released?
I am doing the localisation based 1.3.7.pot file.
I have to complete 777 of 2806. Almost all the Qt strings are translated,
but just a few for xforms.
I am doing cleanup and testing for the translation, with some
Dear All,
I would like to ask when the 1.3.7 version is going to be released?
I am doing the localisation based 1.3.7.pot file.
I have to complete 777 of 2806. Almost all the Qt strings are translated,
but just a few for xforms.
I am doing cleanup and testing for the translation, with some
18 matches
Mail list logo