Migration issues tracking

[simahawk]

Proposal by @dreispt: "generating one issue per module to migrate with a "13.0-MIG" milestone, and then track the milestone?"

Original comment: OCA/stock-logistics-reporting#92 (comment)

Ongoing PR to make current issues update automatically: #97

CC @dreispt @sbidoul @pedrobaeza

[pedrobaeza]

As said, I don't like this: OCA/stock-logistics-reporting#92 (comment)

[sbidoul]

I personally like the idea of individual issues, for the simplicity and ease of cross-referencing using native GitHub features. I'd use a label instead of a milestone though.

[pedrobaeza]

Seriously 40 opened issue per version in repos like OCA/web? Please don't go that direction...

[dreispt]

@sbidoul or maybe a tag + a milestone?: [Migration] +[13.0]

I would be good to hear more opinion on the Issue per Branch vs Issue per Module.

My personally feeling is that the single issue is redundant (additional overhead) with a list of Issues, that would be automatically updated as they are being solved.

Having dozens or hundreds of issues and PRs is something we are already living with.

[legalsylvain]

Can be closed.
It seems we now have an issue per revision created by the bot. (Like OCA/pos#543)

By the way, agree with @pedrobaeza regarding the design per version and not by module.