-
Notifications
You must be signed in to change notification settings - Fork 78
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
Roadmap for v1.0 #150
Comments
If you want to get hdrmerge into Debian you need to find someone who packages it (or do it yourself). I fear I'm not the right person, I'm absolutely not into the HDR business and didn't even know about hdrmerge until now. What you probably also want to do are signed releases: https://wiki.debian.org/Creating%20signed%20GitHub%20releases |
Is there a plan for another minor release before 1.0 ? |
@luzpaz i will tag a new release around the time I tag the RawTherapee 5.7 release - very soon. The word "minor" doesn't really play any part here - it is what it is, and we may as well call it 1.0 since it has been used successfully for a long time, it is feature-complete for what it does, and there are no new features on the horizon. |
@fanckush but your changes will fix problems, so I'm ambivalent about releasing a 1.0 now :) Fact is that HDRMerge needs a new release, but considering that there is light at the end of the tunnel to get the issues you listed fixed, I think we should release v0.6 instead, which gives us time to test your changes and then release v1.0 once your fixes are finalized. What do you think? |
@Beep6581 that makes total sense. all i want to have is a version of HDRMerge with the current fixes as a safe point :) 0.6 sounds great! |
meanwhile https://packages.debian.org/hdrmerge |
5 years no release... any news on releasing? |
@Floessie meanwhile Debian 12 is frozen and I missed to use |
It's time we made a new stable release.
@heckflosse @Hombre57 @Floessie please tag issues you'd like included in the next release with the v1.0 milestone.
The text was updated successfully, but these errors were encountered: