Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4.0.11 #1802

Closed
Beep6581 opened this issue Aug 11, 2015 · 29 comments
Closed

4.0.11 #1802

Beep6581 opened this issue Aug 11, 2015 · 29 comments
Assignees

Comments

@Beep6581
Copy link
Owner

Originally reported on Google Code with ID 1818

I would like to release 4.0.11 ASAP. A bug-fix release.

Reported by entertheyoni on 2013-03-30 21:26:18

@Beep6581
Copy link
Owner Author

About issue 1778: would you like that i temporarilly remove the shortcut lines that
generates the crash?

Reported by natureh.510 on 2013-03-31 14:24:59

@Beep6581 Beep6581 self-assigned this Aug 11, 2015
@Beep6581
Copy link
Owner Author

Sounds good, but since you already posted a patch for linux, if it works, could you
comment out the windows section only? 

Reported by entertheyoni on 2013-03-31 14:40:35

@Beep6581
Copy link
Owner Author

Sure.

Reported by natureh.510 on 2013-03-31 14:43:37

@Beep6581
Copy link
Owner Author

Added the auto-distortion that stopped working somehow around > 4.0.9.184

Reported by oduis@hotmail.com on 2013-03-31 20:24:43

@Beep6581
Copy link
Owner Author

Sorry but that is not a serious issue, no patch has been submitted and nobody accepted
it. I won't delay 4.0.11 for it.

Reported by entertheyoni on 2013-03-31 20:45:58

@Beep6581
Copy link
Owner Author

It's a pretty complex (and RT unique) feature that stopped working, and the user even
narrowed down the changeset.
If no dev can support that feature, it should at least be removed if it's broken.

If a feature-stopped-working is not serious, then what is the definition of a serious
build breaker?

Reported by oduis@hotmail.com on 2013-03-31 21:16:26

@Beep6581
Copy link
Owner Author

added 1821, problem with color management on input jpgs

Reported by michaelezra000 on 2013-03-31 21:20:32

@Beep6581
Copy link
Owner Author

Issue 1768 has been solved (and will be committed soon). Added issue 1806 to the list,
it will be solved within 1-2 days.

Reported by natureh.510 on 2013-04-01 01:05:43

@Beep6581
Copy link
Owner Author

Reported by michaelezra000 on 2013-04-01 02:13:24

@Beep6581
Copy link
Owner Author

FYI: Status of issue 1641 is FixedPendingConfirmation

Reported by natureh.510 on 2013-04-01 09:51:31

@Beep6581
Copy link
Owner Author

Auto-distortion only works with a fraction of images, and only a fraction of the people
who work on those images willl try to use it. Compare this to not being able to save
an image (issue 1778)... As the issue was minor and untouched for two weeks, chances
that it would be fixed anytime soon were slim, but since Hombre took it I have nothing
against including it.

Reported by entertheyoni on 2013-04-01 12:23:45

@Beep6581
Copy link
Owner Author

Reported by entertheyoni on 2013-04-05 12:32:45

@Beep6581
Copy link
Owner Author

Issue 1778 removed from the blocking issues, because it's half solved (i.e. not as cleanly
as it should for Windows).

Reported by natureh.510 on 2013-04-10 10:22:14

@Beep6581
Copy link
Owner Author

Should issue 1770 be part of the blocking issues? I estimate 4-5 days of developement
time, but we should add at least 3 more days for testing, etc...

Do you plan to make a 4.1 release some day?

Reported by natureh.510 on 2013-04-10 10:28:13

@Beep6581
Copy link
Owner Author

Great, I'll just wait for Michael to commit issue 1799 and I'll do issue 38 while waiting.

4.0.11 is mostly a bugfix release for 4.0.10.

4.1 as soon as we're happily stable... If 4.0.11 is stable after the world tests it
for a month then we can do 4.1 next month :]

Issue 1770 should not be rushed, so let's leave that for the next release.

Reported by entertheyoni on 2013-04-10 10:34:36

@Beep6581
Copy link
Owner Author

I committed 1815, and temporarily removed Skintone Profiles, until I create good working
ones (still experimenting).

Reported by michaelezra000 on 2013-04-11 02:53:53

@Beep6581
Copy link
Owner Author

DrSlony, I'd like to commit a FadePack (FP) with quite a few profiles which give a finished
stylized look. Please coordinate with me before tagging 4.0.11. Thanks!:)

Reported by michaelezra000 on 2013-04-20 01:34:32

@Beep6581
Copy link
Owner Author

Looks like there are no imminent changes pending and we're at a stable point, and it's
May 1, so I'd like to tag in a few hours.

Reported by entertheyoni on 2013-05-01 19:08:55

@Beep6581
Copy link
Owner Author

Would be nice to commit 1860

Reported by michaelezra000 on 2013-05-03 19:45:10

@Beep6581
Copy link
Owner Author

Yes, you could tag now. I'll try to investigate on issue 1772 this w.e., but I would
be surprised to find anything new :-/

Reported by natureh.510 on 2013-05-03 23:06:50

@Beep6581
Copy link
Owner Author

I will not get access to my machine until tomorrow, so if anyone can commit 1860, feel
free

Reported by michaelezra000 on 2013-05-03 23:43:45

@Beep6581
Copy link
Owner Author

1860 committed.

Sorry for the delay, I've had no time. I'll do it Sunday/Monday.

Reported by entertheyoni on 2013-05-04 23:27:00

@Beep6581
Copy link
Owner Author

Reported by entertheyoni on 2013-05-14 22:35:08

@Beep6581
Copy link
Owner Author

All blocked issues are solved.
I'm happy to tag (after the usual consistency, language file and manual updates). I
will definitely have time to do this on Friday, perhaps even tomorrow.
Would be nice, but not necessary, if the AMaZE speedup patch was included, if safe.
It is a requirement that 32-bit and 64-bit Windows builds appear within a day of tagging.

(I wanted to handle the 32-bit build myself but ran into an issue I have no idea how
to resolve: http://rawtherapee.com/forum/viewtopic.php?f=10&t=4597 )

Reported by entertheyoni on 2013-05-14 22:54:03

@Beep6581
Copy link
Owner Author

As I struggle to get a working win32 build, Hombre seems on the verge of stabilizing
the queue, so adding 1788. 1872 ready to be committed, adding here so I don't forget.

Other reminders for myself:
- buildRT.bat win.cmake
- PP3 resize & out ICC
- fix "colorfulnes" typo in default/Eng

Reported by entertheyoni on 2013-05-20 22:47:47

@Beep6581
Copy link
Owner Author

Just for my information: what has to be done to increment the minor version number,
i.e. producing a 4.1 release?

As a user, i generally think that an increment of the third version number represent
minor bugfix and is not worth a download and reinstall, and i guess that many people
will think like that.

Reported by natureh.510 on 2013-05-22 07:57:48

@Beep6581
Copy link
Owner Author

hg tag 4.0.11
or
hg tag 4.1

If the issue 1772 patch resolves the queue issue I'm fine with 4.1, otherwise 4.0.11.
What do you think?

Reported by entertheyoni on 2013-05-23 23:07:02

@Beep6581
Copy link
Owner Author

Ok. I'll make my best to solve the 32 bits issue by the w.e., but no promise. So it's
all about a delay. Go ahead with 4.0.11 now if you wish. Something tells me that we'll
need time to remove most bugs of issue 1772 :-/

Reported by natureh.510 on 2013-05-23 23:39:38

@Beep6581
Copy link
Owner Author

Queue patch removed as it's not ready, will go into a new tag.

Tagged 4.0.11. Well done everyone!

Please help make builds available ON OUR WEBSITE for Win and Mac within a day if possible!

Reported by entertheyoni on 2013-05-29 14:34:05

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant