I completely agree with Dave here. Let’s get the work done in master. Once we have our solution functioning to the point where we are ready to label it we can at that time choose to either: label master, move the stable label.
/ Chris On 06/09/16 15:02, "[email protected] on behalf of Dave Neary" <[email protected] on behalf of [email protected]> wrote: Hi Hongbo, Since Dovetail is not participating in the C release, we should not have a C release branch, I think - I would suggest that we work in master only. I do not understand why we would need to be on a C branch to run our test suite against a C release branch. Thanks, Dave. On 09/05/2016 11:46 PM, Tianhongbo wrote: > Hi Bin: > > > > thanks. > > > > Yes, we need the help from Aric. > > > > Also, we need the suggestion from Aric. > > > > Best Regards > > > > hongbo > > > > *From:*HU, BIN [mailto:[email protected]] > *Sent:* 2016年9月6日11:44 > *To:* Tianhongbo; 'TECH-DISCUSS OPNFV' > *Subject:* RE: [opnfv-tech-discuss] [dovetail]issures and suggestion: to > upload the dovetail codes to the git/gerrit > > > > I think you need to work with Aric to create stable/colorado branch. > > > > Then cherrypick those C Release stuff from master to stable/colorado. > > > > Bin > > *From:* [email protected] > <mailto:[email protected]> > [mailto:[email protected]] *On Behalf Of > *Tianhongbo > *Sent:* Monday, September 05, 2016 8:37 PM > *To:* 'TECH-DISCUSS OPNFV' <[email protected] > <mailto:[email protected]>> > *Subject:* [opnfv-tech-discuss] [dovetail]issures and suggestion: to > upload the dovetail codes to the git/gerrit > > > > Hi dovetailers: > > > > Now, we are trying to upload the documents and scripts to the dovetail > repos. > > But , there are at least two branches: master and C release. The master > branch will be used for the D release. > > The goal of the dovetail is to test against the C release now and to > test against the D release in future. The problem comes: where can we > put the documents and scripts? > > There will be no problem with the documents. But there will be the > issues with the scripts. > > If we merge the script in the master, we cannot use the scripts to test > the C release. > > If we merge the scripts in the C release branch, we cannot use the > scripts for the D release. > > Meanwhile, the C release branch was frozen, we cannot edit the scripts > in the C release branch now. > > > > Objection for the dovetail scripts: > > 1. The codes will be used in future（next will be used for D release） > > 2. The first version of dovetail is used to test C release > > > > > > Do you have any idea to handle these problem? > > > > I have a suggestion: > > > > When we commit the patches to the master, we can try our best to merge > in the master branch. These will be used for the future release. > > Meanwhile, cherry pick the patches to the C release. If the C release > was frozen, cherry pick the patches to the dovetail branch. > > > > > > > > Any comments are welcome. > > > > Best regards > > > > hongbo > > > > _______________________________________________ > opnfv-tech-discuss mailing list > [email protected] > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338 _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
