An error occurred fetching the project authors.
  1. 16 May, 2016 1 commit
    • Sean McGivern's avatar
      Make upcoming milestone work across projects · 750b2ff0
      Sean McGivern authored
      Before: we took the next milestone due across all projects in the
      search and found issues whose milestone title matched that
      one. Problems:
      
      1. The milestone could be closed.
      2. Different projects have milestones with different schedules.
      3. Different projects have milestones with different titles.
      4. Different projects can have milestones with different schedules, but
         the _same_ title. That means we could show issues from a past
         milestone, or one that's far in the future.
      
      After: gather the ID of the next milestone on each project we're looking
      at, and find issues with those milestone IDs. Problems:
      
      1. For a lot of projects, this can return a lot of IDs.
      2. The SQL query has to be different between Postgres and MySQL, because
         MySQL is much more lenient with HAVING: as well as the columns
         appearing in GROUP BY or in aggregate clauses, MySQL allows them to
         appear in the SELECT list (un-aggregated).
      750b2ff0
  2. 15 May, 2016 1 commit
  3. 13 May, 2016 1 commit
  4. 12 May, 2016 9 commits
  5. 11 May, 2016 3 commits
    • Yorick Peterse's avatar
      Updated 8.7.4 CHANGELOG entries · c446a865
      Yorick Peterse authored
      [ci skip]
      c446a865
    • Sean McGivern's avatar
      Group commits by date in server timezone · d9574a7b
      Sean McGivern authored
      `Time#to_date` just takes the (timezone-less) year, date, and month, and
      creates a new date from that. Because the commits in the list are
      grouped by date, rather than chunked when the date changes, a commit can
      be shown in the wrong order if its CommitDate has a timezone-less date
      that's different to other commits around it.
      
      Convert all CommitDates to the server timezone before grouping, as that
      will at least produce consistent results. Users can still see a
      timestamp on the commit that doesn't match the date it's grouped under,
      because the timestamp shown uses the user's local timezone, and the
      grouping uses the server's timezone, but that was an issue anyway.
      d9574a7b
    • Sean McGivern's avatar
      Only generate repository push email once · 5f27e26b
      Sean McGivern authored
      The repository push email can be very expensive to generate, especially
      with syntax-highlighted diffs. Instead of generating the email for each
      recipient, generate one email object and reset the Message-Id and To
      headers for each recipient. (Cloning would also be expensive in the case
      of large emails, although probably not as bad as generating from
      scratch.)
      5f27e26b
  6. 10 May, 2016 7 commits
  7. 09 May, 2016 7 commits
  8. 08 May, 2016 1 commit
  9. 07 May, 2016 3 commits
  10. 06 May, 2016 3 commits
  11. 05 May, 2016 4 commits