Activity
From 2022-12-26 to 2022-12-28
2022-12-28
-
22:10 Feature #37712: Tree view for issues list
- I use the following Plugin for this request (Redmine 4)
https://www.redmine.org/plugins/redmine_subtask_list_accor... -
08:31 Patch #37867: Limit puma < 6.0.0 to avoid system test error
- I have opened a new issue. Please use #38135 for further discussion.
-
08:23 Patch #37867: Limit puma < 6.0.0 to avoid system test error
- Go MAEDA wrote:
> Redmine still supports Ruby 2.6, but the patch attachment:0001-Remove-puma-6.0.0-restriction.patch... -
08:12 Patch #37867: Limit puma < 6.0.0 to avoid system test error
- Redmine still supports Ruby 2.6, but the patch attachment:0001-Remove-puma-6.0.0-restriction.patch causes a compatibi...
-
08:27 Patch #38135 (Closed): Allow use of Puma 6.0.0 or later
- Since Capybara 3.37 and earlier did not support Puma 6, we have updated the Gemfile in r21934 to use Puma < 6.0.0.
... -
07:36 Feature #38134 (Closed): Drop Ruby 2.6 support
- The normal maintenance phase of Ruby 2.7 ended on 2022-04-22 (see https://www.ruby-lang.org/en/news/2022/04/12/ruby-2...
-
06:39 Feature #38099: Add Ruby 3.2 support
- Nokogiri 1.13.10 does not yet support Ruby 3.2. Waiting for the next release of Nokogiri....
-
04:05 Patch #38124 (Closed): Update csv, net-imap, net-pop, and net-smtp gems to the same versions shipped with Ruby 3.2.0
- Committed the patch.
-
01:36 Patch #38122 (Closed): Remove Bundler from requirements
- Committed the patch.
-
00:22 Defect #38127 (Closed): Email Config through linux
- See #38123#note-1. Do not repeat the same post.
2022-12-27
-
14:43 Patch #37867: Limit puma < 6.0.0 to avoid system test error
- Alexander Meindl wrote:
> This is fixed in Version 3.38.0 of capybara: https://github.com/teamcapybara/capybara/blob... -
11:31 Patch #37867: Limit puma < 6.0.0 to avoid system test error
- This is fixed in Version 3.38.0 of capybara: https://github.com/teamcapybara/capybara/blob/master/History.md#version-...
-
13:03 Defect #38127 (Closed): Email Config through linux
- Hi Team,
We need to do email configuration through linux server, Please help on this. -
09:47 Patch #38124 (Closed): Update csv, net-imap, net-pop, and net-smtp gems to the same versions shipped with Ruby 3.2.0
- This patch updates the Ruby Standard Gems used by Redmine to the same version included in Redmine 3.2.0.
See: http... -
09:26 Defect #38123 (Closed): Email Config through linux
-
09:26 Defect #38123: Email Config through linux
- Please use "forums":/projects/redmine/boards for questions. Issues are used to report a bug, suggest a new feature, o...
-
08:09 Defect #38123 (Closed): Email Config through linux
- Hi Team,
We need to configure email through linux server, which should listen by Redmine
We are using this tool... -
05:38 Patch #38122 (Closed): Remove Bundler from requirements
- In Ruby 2.6 and later, Bundler is installed by default. Redmine does not support Ruby versions earlier than 2.5, whic...
-
02:04 Patch #38121 (Closed): Update MiniMagick to 4.12
- Updated MiniMagick to 4.12 in r22004.
-
01:20 Patch #38121: Update MiniMagick to 4.12
- MiniMagick 4.11 and earlier have a compatibility issue with Ruby 3.2.
https://github.com/minimagick/minimagick/re... -
00:55 Patch #38121 (Closed): Update MiniMagick to 4.12
- https://rubygems.org/gems/mini_magick
2022-12-26
-
08:57 Defect #38118: Ruby 3.2: Markdown formatter warns "undefining the allocator of T_DATA class Redcarpet::Markdown"
- The fix for the issue is will be included in the next release of Redcarpet.
https://github.com/vmg/redcarpet/pull/721 -
08:43 Defect #38118 (Closed): Ruby 3.2: Markdown formatter warns "undefining the allocator of T_DATA class Redcarpet::Markdown"
- Markdown formatter displays a warning "undefining the allocator of T_DATA class Redcarpet::Markdown" with Ruby 3.2.
... -
02:51 Feature #38099: Add Ruby 3.2 support
- r22001 passes all tests with Ruby 3.2.
I will keep this issue open for a while, and if no new issues related to Ru... -
02:37 Defect #38100 (Closed): Ruby 3.2: Encoding::CompatibilityError when running ChangesetTest#test_invalid_utf8_sequences_in_comments_should_be_replaced_latin1
- Committed the fix as a part of #38099.
Also available in: Atom