Re: [opendaylight-dev] [release] [OpenDaylight TSC] [releng] Fluorine branch cutting

Michael Vorburger <vorburger@...>

On Mon, Aug 13, 2018 at 5:50 AM Luis Gomez <ecelgp@...> wrote:
This will take care of integration and distribution remaining changes for neon:

cool, now we just need to get autorelease to actually pass again... ;-) I'm still, right now, seeing various failures on from the following projects:

* lispflowmapping
* bgpcep
* netconf
* controller

I'll see if I can help with controller myself ASAP - hoping bgpcep and lispflowmapping and netconf fix their failures in autorelease...


On Aug 11, 2018, at 6:07 AM, Robert Varga <nite@...> wrote:

On 10/08/18 00:05, Michael Vorburger wrote:
On Thu, Aug 9, 2018 at 11:59 PM Michael Vorburger <vorburger@...
<mailto:vorburger@...>> wrote:

   On Thu, Aug 9, 2018 at 4:55 PM Anil Belur
   <abelur@... <mailto:abelur@...>> wrote:

       Hello Everyone,

       We have performed branch cutting today with the master branch
       blocked. The work is complete and the master branch (Neon) is
       now open for development again. 

       Note: A reminder for projects to rebase their existing master
       branch patches to ensure they are building against the post
       version bumped versions of code base.

   Thank you! But the distribution jobs are still broken
   - is someone looking into and going to fix those? Anil, not
   neccessarily looking at you - I'm guessing integration/distribution
   folks will know what where still needs bumping versions?

erm, oups, no wait, hit Send too early - perhaps more importantly than
distribution failures: at least genius is still completely broken
... I'm guessing we did not yet run deploy jobs on all projects (in
order of the dependency tree) to populate Nexus, yet?

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?

dev mailing list

Join { to automatically receive all group messages.