On 2/11/15 9:52 AM, Dicebot wrote:
On Wednesday, 11 February 2015 at 17:23:36 UTC, Jacob Carlborg wrote:
On 2015-02-11 17:51, Dicebot wrote:
Small added effort for release manager to update submodules in meta-repo
upon new releases. Can't really imagine anything else right now.
You're thinking the meta repository is only update on each release? Or
would an automated approach be a good idea?
Yes. Updating it all the time to master creates a lot of noise in
history for little practical benefit (updating to latest master is one
command). For matching different repository history Vladimir maintains
special repo in bitbucket with commits populated by a bot - but it is a
different thing.
What does "update" mean in this context? I was expecting the projects to
be more or less up to date. -- Andrei