ams-5>
> --
>
>
>
>
> -- Forwarded message -----
> From: Isabelle Hurbain-Palatin
> Date: Mon, Dec 23, 2019 at 6:32 AM
> Subject: Re: Fwd: [darktable-dev] Feature freeze for 3.0
> To: Aurélien Pierre
> Cc: Bruce Williams , darktable &
---
From: Isabelle Hurbain-Palatin
Date: Mon, Dec 23, 2019 at 6:32 AM
Subject: Re: Fwd: [darktable-dev] Feature freeze for 3.0
To: Aurélien Pierre
Cc: Bruce Williams , darktable <
darktable-dev@lists.darktable.org>
Hi all,
I just opened a PR for the filmic rgb documentation:
https://git
ut the information in shape for a documentation ? Not
>>>> that I want to give you the bad job, but I might be more useful on the
>>>> debugging team, as the release approaches. I'm still happy to do
>>>> proof-reading.
>>>>
>>>> Cheers,
>
proaches. I'm still happy to do
>>> proof-reading.
>>>
>>> Cheers,
>>>
>>> Aurélien.
>>> Le 18/08/2019 à 06:34, Bruce Williams a écrit :
>>>
>>> Thanks, I'll check it out!
>>>
>>> Cheers,
>>> Bruce
2019 à 06:34, Bruce Williams a écrit :
>>
>> Thanks, I'll check it out!
>>
>> Cheers,
>> Bruce Williams.
>>
>> -- Forwarded message -
>> From: Ariel Kanterewicz
>> Date: Sun., 18 Aug. 2019, 09:06
>> Subject: Re: [darktable-
:37
Subject: Re: Fwd: [darktable-dev] Feature freeze for 3.0
To: Isabelle Hurbain-Palatin
Cc: Bruce Williams , darktable <
darktable-dev@lists.darktable.org>
Hello Isabelle and William and everyone,
is this arrangement still on ? I have started emptying my brain here (in
English) :
s.
>>
>> -- Forwarded message -----
>> From: *Ariel Kanterewicz* > <mailto:ar...@aknt.com.ar>>
>> Date: Sun., 18 Aug. 2019, 09:06
>> Subject: Re: [darktable-dev] Feature freeze for 3.0
>> To: darktable > <mai
Dear All,
the translation into German is done now and can merged into master.
See pull request https://github.com/darktable-org/darktable/pull/3506[1]
Pierre Metzner
Am Montag, 12. August 2019, 11:21:27 CET schrieb Pascal Obry:
> Dear all,
>
> The next version of darktable will have a quite
> From: Andreas Schneider
> Sent: Tuesday, August 20, 2019 2:20 AM
> To: darktable-dev@lists.darktable.org
> Cc: Bruce Williams
> Subject: Re: Fwd: [darktable-dev] Feature freeze for 3.0
>
> On Sunday, August 18, 2019 3:29:30 AM CEST Bruce Williams wrote:
> > I will c
Spanish translators ready for duty
On Tue, Aug 20, 2019, 9:22 AM Maurizio Paglia wrote:
> We are working in order to give dt an Italian interface again with a
> couple of new volunteers.
> Maurizio
>
> Il mar 20 ago 2019, 09:24 Pascal Obry ha scritto:
>
>> Hello Pierre,
>>
>> > from my side I
We are working in order to give dt an Italian interface again with a couple
of new volunteers.
Maurizio
Il mar 20 ago 2019, 09:24 Pascal Obry ha scritto:
> Hello Pierre,
>
> > from my side I will help as last year at the German translation for
> > darktable and the German user manual.
> >
> >
Hello Pierre,
> from my side I will help as last year at the German translation for
> darktable and the German user manual.
>
> It would be nice if there would be a trigger signal when the translations
> can be started.
Sure. I'll send a notification here.
> Does darktable 3.0 have its own
If Andreas is not available, I can cover github via a video chat training.
Tim
-Original Message-
From: Andreas Schneider
Sent: Tuesday, August 20, 2019 2:20 AM
To: darktable-dev@lists.darktable.org
Cc: Bruce Williams
Subject: Re: Fwd: [darktable-dev] Feature freeze for 3.0
On Sunday
On Sunday, August 18, 2019 3:29:30 AM CEST Bruce Williams wrote:
> I will certainly do what I can.
> As yet, I have not delved into the world of github, pull requests, merges,
> and so forth.
> Nor compiling!
> But when I get home from holiday (another 8 days), that is on my list of
> things to
Hello developers and writer,
from my side I will help as last year at the German translation for
darktable and the German user manual.
It would be nice if there would be a trigger signal when the translations
can be started.
Does darktable 3.0 have its own branch or is this in master?
Is the
proof-reading.
Cheers,
Aurélien.
Le 18/08/2019 à 06:34, Bruce Williams a écrit :
Thanks, I'll check it out!
Cheers,
Bruce Williams.
-- Forwarded message -
From: Ariel Kanterewicz
Date: Sun., 18 Aug. 2019, 09:06
Subject: Re: [darktable-dev] Feature freeze for 3.0
To: darktable
liams a écrit :
>
> Thanks, I'll check it out!
>
> Cheers,
> Bruce Williams.
>
> -- Forwarded message -
> From: Ariel Kanterewicz
> Date: Sun., 18 Aug. 2019, 09:06
> Subject: Re: [darktable-dev] Feature freeze for 3.0
> To: darktable
>
>
> @Bruc
:
> Thanks, I'll check it out!
>
> Cheers,
> Bruce Williams.
>
> -- Forwarded message -
> From: *Ariel Kanterewicz* mailto:ar...@aknt.com.ar>>
> Date: Sun., 18 Aug. 2019, 09:06
> Subject: Re: [darktable-dev] Feature freeze for 3.0
> To: darktable <m
to get up to speed on.
>
> Cheers,
> Bruce Williams.
>
> -- Forwarded message -
> From: Ulrich Pegelow
> Date: Sun., 18 Aug. 2019, 01:31
> Subject: Re: [darktable-dev] Feature freeze for 3.0
> To:
>
>
> Hi,
>
> frankly speaking I am still usi
-
From: Ulrich Pegelow
Date: Sun., 18 Aug. 2019, 01:31
Subject: Re: [darktable-dev] Feature freeze for 3.0
To:
Hi,
frankly speaking I am still using the 2.6 branch and have no experience
of any of the 2.7 features at all. I would be happy if someone closer to
the recent development (Bruce
Hi,
frankly speaking I am still using the 2.6 branch and have no experience
of any of the 2.7 features at all. I would be happy if someone closer to
the recent development (Bruce?) could take over the manual.
Best wishes
Ulrich
Am 13.08.19 um 17:42 schrieb Pascal Obry:
Hi Matthieu,
I
Hi Matthieu,
I fully agree here. I'm not the maintainer of the documentation so I
cannot speak for Ulrich.
That being said, I can certainly ping developers to start a draft of
the code they have introduced in dt 3.0.
I have noted that Bruce will be happy to help doing the preparation of
the
Apologies for the misspelling, Mattieu.
-- Forwarded message -
From: Bruce Williams
Date: Tue., 13 Aug. 2019, 15:23
Subject: Fwd: [darktable-dev] Feature freeze for 3.0
To: darktable
I wholeheartedly agree with Matthew on the documentation front.
Now, I'll confess, I couldn't
: [darktable-dev] Feature freeze for 3.0
To: Pascal Obry
Cc: darktable
- Original Message -
> From: "Pascal Obry"
> Also, to avoid the hard work at the end of year (like in 2018) I'd like
> to have a feature freeze earlier.
I support this. We had a lot of last-minutes fixes la
- Original Message -
> From: "Pascal Obry"
> Also, to avoid the hard work at the end of year (like in 2018) I'd like
> to have a feature freeze earlier.
I support this. We had a lot of last-minutes fixes last years, and given the
amount of changes, we really need a long testing period
Wow, this sounds outrageously cool! I've been using darktable since the
1.x versions and it has progressed so far. Thanks to all the developers
who have worked on it...it's my favourite open source project of all time!
Jason
On 2019-08-12 5:21 a.m., Pascal Obry wrote:
>
> Dear all,
>
> The
Dear all,
The next version of darktable will have a quite long list of
enhancements (full rework of the UI, culling mode, large lighttable
speedup, new modules...) and many changes with some part completely
reworked.
So next version will be named 3.0, that is raising the major version
number
* I will try to provide a tool to fix this issue (as far as possible).
This, however, will take some time and I can not guarantee that this
conversion will be possible. But I will try my best.
see also
https://github.com/darktable-org/darktable/pull/1827#issuecomment-439224708
Dear Andreas,
Am 15.11.18 um 21:40 schrieb Andreas Schneider:
On Thursday, 15 November 2018 21:33:00 CET Pascal Obry wrote:
Le jeudi 15 novembre 2018 à 21:25 +0100, Andreas Schneider a écrit :
The issue is probably a migration which didn't work:
Le jeudi 15 novembre 2018 à 22:00 +0100, Andreas Schneider a écrit :
> I don't have a backup to restore but I will have in future for the last 14
> days ...
That's good :) I have a rsnapshot of most of my work for 6 months with
snapshot every 4 weeks and 9 days.
I understand how bad news it can
On Thursday, 15 November 2018 21:33:00 CET Pascal Obry wrote:
> Le jeudi 15 novembre 2018 à 21:25 +0100, Andreas Schneider a écrit :
> > The issue is probably a migration which didn't work:
> >
> > https://github.com/darktable-org/darktable/pull/1827
> >
> >
> > I'm using darktable master which
On Thursday, 15 November 2018 21:33:00 CET Pascal Obry wrote:
> Le jeudi 15 novembre 2018 à 21:25 +0100, Andreas Schneider a écrit :
> > The issue is probably a migration which didn't work:
> >
> > https://github.com/darktable-org/darktable/pull/1827
> >
> >
> > I'm using darktable master which
Le jeudi 15 novembre 2018 à 21:25 +0100, Andreas Schneider a écrit :
> The issue is probably a migration which didn't work:
>
> https://github.com/darktable-org/darktable/pull/1827
>
>
> I'm using darktable master which was normally quite stable. The question is
> how can I fix this, change
On Thursday, 15 November 2018 20:55:31 CET Bruce Williams wrote:
> Can you force a reload via the "selected images" module? I'm not at my
> machine right now, but from memory, there's a button that says "load side
> car file" or something similar.
The issue is probably a migration which didn't
2018, 06:49
Subject: Re: [darktable-dev] feature freeze
To:
Am 15.11.18 um 20:42 schrieb Andreas Schneider:
> On Thursday, 15 November 2018 18:36:02 CET Pascal Obry wrote:
>> Dear all,
>>
>> The feature freeze is effective since yesterday Nov 14th. So no more
>&g
Am 15.11.18 um 20:42 schrieb Andreas Schneider:
On Thursday, 15 November 2018 18:36:02 CET Pascal Obry wrote:
Dear all,
The feature freeze is effective since yesterday Nov 14th. So no more
new feature can be integrated into darktable at this stage.
It is a good time to do some testing and
On Thursday, 15 November 2018 18:36:02 CET Pascal Obry wrote:
> Dear all,
>
> The feature freeze is effective since yesterday Nov 14th. So no more
> new feature can be integrated into darktable at this stage.
>
> It is a good time to do some testing and report the issues you
> encounter. That
Dear all,
The feature freeze is effective since yesterday Nov 14th. So no more
new feature can be integrated into darktable at this stage.
It is a good time to do some testing and report the issues you
encounter. That is, we are entering a bug squash period :)
As previously said, the string
Dear all,
The end of year is coming fast and we want to do the feature freeze (we
are a bit late this year) on Nov 14th.
If you are working on a wonderful new feature please open a GitHub
pull-request very soon now. After the feature freeze only the bug fixes
will be integrated.
The string
Dear list,
autumn is coming. So it's time to get ready for the next feature release of
darktable, 2.4.0.
Therefore we are happy to announce the feature freeze for October 14th. If you
are working on anything please make sure to have it pushed or PRed until then.
Dates for string freeze, an RC
Hello Tobias,
> So by all means, if you two can get this to work I am all for it.
I think I've fixed this. The undo.h file does not contain reference to
history or map anymore. Please let me know if this is what you had in
mind or if I missed something.
Cheers,
--
Pascal Obry / Magny Les
let's wait for another couple of days for this then? and soft-freeze
the other features ;) ?
cheers,
jo
On Tue, Oct 4, 2016 at 11:34 PM, Tobias Ellinghaus wrote:
> Am Dienstag, 4. Oktober 2016, 13:01:43 CEST schrieb Roman Lebedev:
>
> [...]
>
>> I'm not sure about merging it
Am Dienstag, 4. Oktober 2016, 13:01:43 CEST schrieb Roman Lebedev:
[...]
> I'm not sure about merging it *right now*, IIRC Tobias had some ideas
> about undo in general.
My only concern was with the way our undo infrastructure works. And even that
was more details of the design, like having
Hi Jo,
I really would have like to have the darkroom undo feature merged.
https://github.com/darktable-org/darktable/pull/1103
I'm not sure where we stand, I can try to rebase on master and finalize this.
Cheers,
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by
hi all,
in an effort to get a feature release out before end of the year this
time around, i'd like to announce the feature freeze for 2.2 on the
master branch.
this should give us devs some time to make the features we have more
stable, and everybody else a chance to find bugs.
note that we're
Dear devs.
A while ago it was written on this list that branch 1.6.x and master
(soon 2.0) create different xmp sidecar files. So, switching between
both versions was not recommended.
Is this still the case?
Will dt from master read/understand my old xmp files?
I would like to try the current
46 matches
Mail list logo