archetypes project in autorelease

Michael Vorburger <vorburger@...>

[forking previous thread "Re: [opendaylight-dev] [release] [OpenDaylight TSC] [releng] Fluorine branch cutting" into a new thread specifically re archetypes and autorelease follow-up]

On Mon, Aug 13, 2018 at 2:06 PM Anil Belur <abelur@...> wrote:
On Mon, Aug 13, 2018 at 4:38 PM Michael Vorburger <vorburger@...> wrote:
On Aug 11, 2018, at 6:07 AM, Robert Varga <nite@...> wrote:
Everything is go, bu archetypes need and branching...
archetypes merged. How come this project was missed before? Should it be in autorelease? (It currently is not, according to

Anil, will you do the branching on archetypes? Does it need to be added somewhere to not be forgotten next time?

Micheal, Any project which is not a part of AR is presumably a self managed project, and therefore branch cutting need to be performed be the PTL.
Let me know if archetypes needs to be included in AR, I do remember this was included in stable/oxygen, but am not aware as to what changed in between?

I just tried to search the git log for when it was removed, but couldn't find anything... then found and related discussions on thread "adding archetypes to autorelease" where apparently it was concluded that archetypes project should not be in autorelease? I don't really understand why - it's a project which like any other has dependencies, and sometimes we do things which break it (which happened in a previous bump and again here last week during the Neon bump), which we could detect earlier instead of after if we included it.

So IMHO archetypes should definitely be in autorelease. Is anyone really against adding it?


Join { to automatically receive all group messages.