On Friday, 20 December 2019 16:38:41 CET Nicolas Auffray wrote:
> Hi Maurizio,
>
> Sorry, I forgot to inform. My Github needed a cleanup to make the PR to
> prepare coming publishing.
>
> The new path for the article is this one :
> https://github.com/Nilvus/dtorg/tree/3.0-article/content/blog/2019-12-24-dar
> ktable-3.0
So changes should be a PR to your repo? The first paragraph is a bit strange.
Also I don't know what you are trying to express.
> Following the tradition, darktable 3.0 was released for Christmas.
Following the tradition of the last years, darktable 3.0 has been released for
Christmas.
> After a lot of renewal in 2018, 2019 has seen many very unexpected changes
in darktable, both in its user interface and in its internal mechanisms. This
makes darktable 3.0 a more than major version, justifying the direct
transition from version 2.6.x to version 3.0.
What do you mean with renewal? It is normally used for subscriptions. My guess
would be that you meant innovation:
After a lot of innovation in 2018, this year we have seen a lot of unexpected
research, redesign and development in darktable. Both the user interface an
the internal wiring of darktable had significant changes. This makes darktable
3.0 a major version, which justifies the major version bump from 2.6 to 3.0.
Just my 2 cents.
Andreas
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
