[darktable-dev] Plan for dt 3.6
Hello, The plan for 3.6 was sent recently, as a reminder: - release - T0 : July 3rd - code freeze - T0-10 : June 23rd - start create binaries - string freeze - T0-12 : June 11th - start translation - feature freeze - T0-30 : June 1st - only code fix - safe mode - T0-45 : mid-May - only safe simple code So today we are entering "string freeze" mode where only bug fix can be integrated and no more string changes. This means that all translators can start finalizing the translation work. The dead line is June 23rd. Thanks to all for making this 3.6 release very exiting ! Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Plan for dt 3.6 - Feature Freeze
Hello, The plan for 3.6 was sent recently, as a reminder: - release - T0 : July 3rd - code freeze - T0-10 : June 23rd - start create binaries - string freeze - T0-12 : June 11th - start translation - feature freeze - T0-30 : June 1st - only code fix - safe mode - T0-45 : mid-May - only safe simple code So today we are entering "feature freeze" where only bug fix can be integrated. If you want to help to finalize the release you can look at the known issues that we want to fix for 3.6: https://github.com/darktable-org/darktable/milestone/18 Thanks to all for making this 3.6 release very exiting ! Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Plan for dt 3.6
Hello, The plan for 3.6 was sent recently, as a reminder: - release - T0 : July 3rd - code freeze - T0-10 : June 23rd - start create binaries - string freeze - T0-12 : June 11th - start translation - feature freeze - T0-30 : June 1st - only code fix - safe mode - T0-45 : mid-May - only safe simple code So today we are entering "safe mode" where only safe new features will be considered for integration. A reminder for all devs, please look at your current PR and see if it can still be merged or not. Do not hesitate to start a discussion on the PR about possible merging for 3.6. There is a small window of 15 days for integrating new feature afterward only bug fix will be considered. Thanks to all for making this 3.6 release very exiting ! Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Plan for dt 3.6
Hello, We have been discussion the plan for dt 3.6, here it is: - release- T0: July 3rd - code freeze- T0-10 : June 23rd - start create binaries - string freeze - T0-12 : June 11th - start translation - feature freeze - T0-30 : June 1st - only code fix - safe mode - T0-45 : mid-May - only safe simple code So if you are cooking something to be merged be sure to propose it before June especially if this needs some days before to review. I also take the opportunity to remind all translators that it is possible (and advised) to keep the translation up-to-date as there is many strings change. The procedure to do that simply using the up-to- date darktable.pot is documented here: https://github.com/darktable-org/darktable/wiki/Translations Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
[darktable-dev] Plan for dt 3.6
Hello, We have been discussion the plan for dt 3.6, here it is: - release- T0: July 3rd - code freeze- T0-10 : June 23rd - start create binaries - string freeze - T0-12 : June 11th - start translation - feature freeze - T0-30 : June 1st - only code fix - safe mode - T0-45 : mid-May - only safe simple code So if you are cooking something to be merged be sure to propose it before June especially if this needs some days before to review. I also take the opportunity to remind all translators that it is possible (and advised) to keep the translation up-to-date as there is many strings change. The procedure to do that simply using the up-to- date darktable.pot is documented here: https://github.com/darktable-org/darktable/wiki/Translations Regards, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
