On Fri, Jul 15, 2011 at 2:19 PM, Martin Nordholts wrote:
> * Regarding "Bug 304798 - Painting brush outline is slow", is this
> still a big problem? I know Alexia and mitch has worked on this.
Not enough to be a blocker I think. It COULD be optimized more, but as
is, its faster than 2.6, that l
Hi everyone,
I just went through our GIMP 2.8 schedule at
http://tasktaste.com/projects/Enselic/gimp-2-8 and made some
adjustments and about a month was added to the release date estimate
because of it. I would like to describe the adjustments I did, check
the status of the various tasks, and disc
On 04/15/2011 09:57 AM, Alexia Death wrote:
> On Fri, Apr 15, 2011 at 9:08 AM, Martin Nordholts wrote:
>> Hi
>>
>> Two new items on the 2.8 schedule has been added:
>> * Bug 647835 - Handle deprecated GTK+ API
>> * Bug 647834 - Stop using deprecated API in plug-ins
>>
>> And one item has been fixe
2011/4/15 Kevin Cozens :
> Martin Nordholts wrote:
>> The last fixed item means that we run all our tests each night now,
>> including UI tests.
>
> Um... ok... How does a buildbot run UI tests?
If the backend is X, you use http://en.wikipedia.org/wiki/Xvfb.
Although it is often more convenient to
Martin Nordholts wrote:
> The last fixed item means that we run all our tests each night now,
> including UI tests.
Um... ok... How does a buildbot run UI tests?
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berk
On Fri, Apr 15, 2011 at 9:08 AM, Martin Nordholts wrote:
> Hi
>
> Two new items on the 2.8 schedule has been added:
> * Bug 647835 - Handle deprecated GTK+ API
> * Bug 647834 - Stop using deprecated API in plug-ins
>
> And one item has been fixed:
> * Include UI tests in nightly Jenkins builds
Bu
Hi
Two new items on the 2.8 schedule has been added:
* Bug 647835 - Handle deprecated GTK+ API
* Bug 647834 - Stop using deprecated API in plug-ins
And one item has been fixed:
* Include UI tests in nightly Jenkins builds
The last fixed item means that we run all our tests each night now,
includ
On 01/25/2010 12:00 PM, Alexandre Prokoudine wrote:
> The somewhat scary thing about this schedule is that neither 2.8, nor
> 2.10-3.0 section mentions GEGL at all :)
Hi Alexandre!
There will be no further integration of GEGL for GIMP 2.8, and the
2.10/3.0 section does not contain things planned
On Mon, Jan 11, 2010 at 11:53 PM, Martin Nordholts wrote:
> The schedule is very simple. It contains a list of things we want to do
> for GIMP 2.8 and an estimate of the time each task will take in the unit
> "8-hour workdays". The sum of all tasks is then multiplied with a "days
> worked per week
Martin Nordholts wrote:
> I have made a schedule for GIMP 2.8 with the main purpose of being a
> tool to help us decide what features to include or exclude.
I've commited the schedule now, it can be downloaded from
http://git.gnome.org/browse/gimp/plain/devel-docs/gimp-schedule.ods?id=038ea9474d9
On 1/14/10, Patrick Horgan wrote:
>> In order to speed up development then, you would have to hire a specific
>> person.
>
> In the lilypond list they have this great thing. People that want a
> particular feature offer to sponser it, and say how much they are willing to
> pay. Occasionally othe
Martin Nordholts wrote:
Nelson A. de Oliveira wrote:
Can donations (money) to GIMP somehow speed up its development, please?
Currently, money donated to GIMP as a project will not be used to pay
people for writing code, but is instead used for doing things like
paying
Nelson A. de Oliveira wrote:
> Can donations (money) to GIMP somehow speed up its development, please?
Currently, money donated to GIMP as a project will not be used to pay
people for writing code, but is instead used for doing things like
paying flight tickets to e.g. Libre Graphics Meeting.
I
Hi!
Can donations (money) to GIMP somehow speed up its development, please?
Thank you!
Best regards,
Nelson
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Alexandre Prokoudine wrote:
> On 1/11/10, Martin Nordholts wrote:
>
>> Then the ETA of GIMP 2.8 becomes 2010-12-02 which is more
>> reasonable.
>
> And still somewhat scary :)
>
> The plan however does not seem to mention Python scripting
> improvements branch. (which will make estimations only
On Wed, Jan 13, 2010 at 8:57 AM, Alexandre Prokoudine
wrote:
> On 1/11/10, Martin Nordholts wrote:
>
>> Then the ETA of GIMP 2.8 becomes 2010-12-02 which is more
>> reasonable.
>
> And still somewhat scary :)
>
> The plan however does not seem to mention Python scripting
> improvements branch. (wh
On 1/11/10, Martin Nordholts wrote:
> Then the ETA of GIMP 2.8 becomes 2010-12-02 which is more
> reasonable.
And still somewhat scary :)
The plan however does not seem to mention Python scripting
improvements branch. (which will make estimations only scarier :))
Alexandre
_
Liam R E Quin wrote:
> "clean up on-text editing", is there a better description?
Not yet, but everyone is free to look into exactly what we need to do
and come up with more detailed tasks. On-canvas text editing simply
needs to work a bit better than it currently does. Just by using it it's
po
Alexia Death wrote:
> In general, its wonderful. A few notes tho. The format. It does not really
> facilitate discussion and is a bit inconvenient to follow. Perhaps a wiki
> format, tho I assume calc was selected because of the eta math? Versioning is
> a good idea regardless.
>
> Next, It cur
On Mon, 2010-01-11 at 21:53 +0100, Martin Nordholts wrote:
> [1] http://www.chromecode.com/gimp/gimp-2-8-schedule.ods
"clean up on-text editing", is there a better description?
This could usefully be put somewhere people could sign up
for things.
Some of the bugs appear to have been fixed alrea
Hi Martin,
I am happy to do that. Last time we asked though people said there is no time...
I wonder when you tried integrating it? It should definitely compile...
Gerald
--
Dr. Gerald Friedland
International Computer Science Institute
1947 Center Street, Suite 600
CA-94704 Berkeley, USA
http:/
Gerald Friedland wrote:
> Hi,
>
> I think we owe it to Google that all the Google Summer of Code stuff
> be put into GIMP 2.8 (or earlier).
Hi Gerald
If you want the SIOX improvements in 2.8 you should help us integrate
it. For me the code on the branch didn't even compile last time I tried.
T
On Monday 11 January 2010 22:53:06 Martin Nordholts wrote:
> I have made a schedule for GIMP 2.8 with the main purpose of being a
> tool to help us decide what features to include or exclude.
...snip...
> Right now the schedule can be found at [1]. My proposal is that we
> version control the Open
I have made a schedule for GIMP 2.8 with the main purpose of being a
tool to help us decide what features to include or exclude. The schedule
will also let us track project progress and assist "third parties" in
their planning, such as the documentation team and distro package
maintainers.
The
24 matches
Mail list logo
