Luis, That is not how the vote went - the TSC voted to drop TSDR from Nitrogen. Maybe you & others got confused about the options & wrongly voted for them to be dropped? Please see the vote below:
colindixon: #startvote shall the TSC give TSDR until EOD tomorrow (8/18) to get patches for autorelease and int/dist or drop them from nitrogen? drop, abstain, friday [10:36am] odl_meetbot: Begin voting on: shall the TSC give TSDR until EOD tomorrow (8/18) to get patches for autorelease and int/dist or drop them from nitrogen? Valid vote options are drop, abstain, friday. [10:36am] odl_meetbot: Vote using '#vote OPTION'. Only your last vote counts. [10:36am] rovarga: #vote drop [10:37am] jamoluhrsen: #vote drop [10:37am] skitt: #vote drop [10:37am] anipbu: #vote drop [10:37am] colindixon: #vote abstain [10:37am] lori: #vote abstain [10:37am] shague: #vote drop [10:37am] zxiiro: #drop [10:37am] edwarnicke: #vote abstain [10:37am] zxiiro: #vote drop [10:37am] LuisGomez: #vote drop [10:37am] vishnoianil: #vote drop [10:37am] abhijitkumbhare: #vote friday [10:37am] colindixon: #endvote [10:37am] odl_meetbot: Voted on "shall the TSC give TSDR until EOD tomorrow (8/18) to get patches for autorelease and int/dist or drop them from nitrogen?" Results are [10:37am] odl_meetbot: abstain (3): colindixon, lori, edwarnicke [10:37am] odl_meetbot: drop (8): rovarga, skitt, anipbu, LuisGomez, shague, jamoluhrsen, zxiiro, vishnoianil [10:37am] odl_meetbot: friday (1): abhijitkumbhare [10:38am] colindixon: #agreed we will drop TSDR from Nitrogen based on the TSC assessment of risk in adding them back [10:38am] Regards, Abhijit On Thu, Aug 17, 2017 at 1:08 PM, Luis Gomez <ece...@gmail.com> wrote: > YuLing, > > Today TSC decided to give TSDR until EOD tomorrow (8/18) to get patches > for autorelease and int/dist. I would suggest to push the patches today if > you can to avoid last minute surprises. > > BR/Luis > > > > On Aug 17, 2017, at 12:47 PM, YuLing Chen <yulingche...@gmail.com> > wrote: > > > > Hi An and Colin, > > > > We really would like to get TSDR back to Nitrogen...is there still > chance for us to do so? > > > > As what I mentioned, we've got Karaf upgrade completed and merged. The > only remaining task is adding it to integration/distribution. We can finish > it tonight. > > > > Would it still be possible for us to catch the Nitrogen train? > > > > Thanks, > > > > YuLing > > > > On Thu, Aug 17, 2017 at 12:26 AM, YuLing Chen <yulingche...@gmail.com> > wrote: > > Hi An, > > > > Sorry for the delay and this news. > > > > Actually, I've just merged TSDR karaf 4 migration, but seems to the > Oxygen branch. > > > > https://git.opendaylight.org/gerrit/#/c/60916/ > > > > > > Is it too late to get into Nitrogen? > > > > We were about to add TSDR to integration/distribution...should we still > continue with that effort? In Oxygen or Nitrogen branch? > > > > Thanks, > > YuLing > > > > On Wed, Aug 16, 2017 at 4:35 PM, An Ho <an...@huawei.com> wrote: > > +Add CONTROLLER team. > > > > Hi Tom Pantelis and Robert Varga, > > > > Please help investigate this issue blocking Carbon SR2. Several > projects are having issues with their 3node tests. We believe > https://git.opendaylight.org/gerrit/#/c/61433/ is causing problems in > 3node tests. Please let us know if we can revert the patch or provide a > new patch to fix the blocking issue. > > > > Best Regards, > > An Ho > > > > > > -----Original Message----- > > From: release-boun...@lists.opendaylight.org [mailto: > release-boun...@lists.opendaylight.org] On Behalf Of Sam Hague > > Sent: Wednesday, August 16, 2017 3:55 PM > > To: Robert Varga; Jamo Luhrsen; Stephen Kitt; Release ( > rele...@lists.opendaylight.org) > > Subject: Re: [release] https://git.opendaylight.org/gerrit/#/c/61433/ > causing problems in 3node tests > > > > forgot to include release list > > > > looks like multiple projects are having 3node issues: openflowplugin, > > netvirt, controller and vtn. > > > > On Wed, Aug 16, 2017 at 6:42 PM, Sam Hague <sha...@redhat.com> wrote: > > > Robert, > > > > > > the patch seems to be causing issues for the 3node ha tests [1]. Over > > > half the test fails now ever since that patch went in. Any idea how it > > > could produce the following exception? This repeats all through the > > > tests. > > > > > > java.lang.IllegalStateException: Store tree > > > org.opendaylight.yangtools.yang.data.api.schema.tree.spi. > MaterializedContainerNode@38ce1623 > > > and candidate base > > > org.opendaylight.yangtools.yang.data.api.schema.tree.spi. > MaterializedContainerNode@78447ed8 > > > differ. > > > TransactionCommitFailedException{message=canCommit encountered an > > > unexpected failure, errorList=[RpcError [message=canCommit encountered > > > an unexpected failure, severity=ERROR, > > > > > > > > > Thanks, Sam > > > > > > [1] https://jenkins.opendaylight.org/releng/view/netvirt-csit/ > job/netvirt-csit-3node-openstack-ocata-upstream-stateful-carbon/93/ > > _______________________________________________ > > release mailing list > > rele...@lists.opendaylight.org > > https://lists.opendaylight.org/mailman/listinfo/release > > _______________________________________________ > > release mailing list > > rele...@lists.opendaylight.org > > https://lists.opendaylight.org/mailman/listinfo/release > > > > > > _______________________________________________ > > release mailing list > > rele...@lists.opendaylight.org > > https://lists.opendaylight.org/mailman/listinfo/release > > _______________________________________________ > controller-dev mailing list > controller-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/controller-dev >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
