1. Topics
  2. archetypes project in autorelease

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
https://git.opendaylight.org/gerrit/#/c/75136/ and branching...
archetypes https://git.opendaylight.org/gerrit/#/c/75136/ merged. How come this project was missed before? Should it be in autorelease? (It currently is not, according to https://github.com/opendaylight/releng-autorelease.)

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 https://jira.linuxfoundation.org/browse/RELENG-893 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 https://jira.linuxfoundation.org/browse/RELENG-894 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?

Thanks,
Anil 
Robert Varga
 

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.

Regards,
Robert

?
signature.asc

Thanh Ha <thanh.ha@...>
 

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.

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.

Regards,
Thanh
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.
 
Regards,
Thanh
Robert Varga
 

On 13/08/18 15:24, Thanh Ha wrote:
On Mon, Aug 13, 2018 at 5:55 AM Robert Varga <nite@...
<mailto: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.

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.
+1.

Regards,
Robert

?
signature.asc

Anil Belur
 


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.

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.


+1

Thanks,
Anil 
1 - 6 of 6