delta/gitlab/gitlab-ce.git/app/models/milestone.rb, branch api-shared-groups

use has_many relationship with events

2016-07-01T13:34:10+00:00

fixing events for import/export

2016-06-29T08:35:26+00:00

Address Yorick's feedback

2016-05-19T04:45:25+00:00

Signed-off-by: Rémy Coutable

Merge remote-tracking branch 'origin/master' into eReGeBe/gitlab-ce-feature/milestone-md

2016-05-19T04:40:33+00:00

Signed-off-by: Rémy Coutable

Return a relation with Postgres

2016-05-16T09:25:24+00:00

Postgres only needs to select a single column, so that can used as a
sub-query where `Milestone.upcoming_ids_by_projects` is actually used in
`IssuableFinder`.

MySQL needs to select the `due_date` column because it's used in the
`HAVING` clause, so it has to return an array of IDs.

Make upcoming milestone work across projects

2016-05-16T09:25:24+00:00

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).

Merge branch 'remove-annotate-gem' into 'master'

2016-05-10T09:08:30+00:00


Remove the annotate gem and delete old annotations

In 8278b763d96ef10c6494409b18b7eb541463af29 the default behaviour of annotation
has changes, which was causing a lot of noise in diffs. We decided in #17382
that it is better to get rid of the whole annotate gem, and instead let people
look at schema.rb for the columns in a table.

Fixes: #17382 

/cc @yorickpeterse 

See merge request !4099

Remove the annotate gem and delete old annotations

2016-05-09T16:00:28+00:00

In 8278b763d96ef10c6494409b18b7eb541463af29 the default behaviour of annotation
has changes, which was causing a lot of noise in diffs. We decided in #17382
that it is better to get rid of the whole annotate gem, and instead let people
look at schema.rb for the columns in a table.

Fixes: #17382

Merge branch 'issue_15394' into 'master'

2016-05-09T15:47:48+00:00


Sanitize milestones and labels titles

fixes #15394 

See merge request !4046

Make model sanitization methods one liners

2016-05-09T15:00:32+00:00