Re: archetypes project in autorelease

Michael Vorburger <vorburger@...>

On Mon, Aug 13, 2018 at 3:25 PM Thanh Ha <thanh.ha@...> wrote:
On Mon, Aug 13, 2018 at 5:55 AM Robert Varga <nite@...> wrote:
On 13/08/18 14:38, Michael Vorburger wrote:
> So IMHO archetypes should definitely be in autorelease. Is anyone really
> against adding it?

Depends on your point of view. It's not part of the distribution, so
there is no real requirement to have in AR.

This is something that was missed during creation review -- at that
point the project should have asked to join the release and its status
should've been clarified.

Personally I think archetypes should not be part of autorelease. This allows archetypes to be able to release at any point in time and that would be useful to provide patch fixes from archetype modules for supported release versions.

we're far from having any intention of doing that. This assumes a sort of much more frequently changing archetype - we're not. 
If the reason the archetypes project wants to be part of autorelease is because they want RelEng to version bump for them then I think that can be arranged via helpdesk ticket.

for me, the reason is to see impacts from changes made, such as the mdsal artifacts change which brought this up again, to be noticed earlier. Do other archetypes project commiters and interested parties have any views on this?

I've anyway raised a helpdesk ticket #59569 requesting releng to bump versions of archetype project on every release.

Join { to automatically receive all group messages.