5/7/2023 0 Comments Kokua viewer beata![]() ![]() Next, LL-VIEWER-RELEASE-TIP is merged into Kokua-NORLV. Our workflow starts with lindenlab/viewer master branch which is assigned branch LL-VIEWER-RELEASE-TIP within kokua-release repository. Open the repository and notice branches named Kokua-MKRLV and Kokua-NORLV these represent our most used branches. We use SmartGit for graphical display of our repositories. Now is when you should clone your fork to your local file system. The repository name will default to kokua-release but can be named as desired. On bitbucket fork kokua-release to your Bitbucket account. Kokua-MKRLV is the closest we have to a master branch and if you clone kokua-release repository it will default to Kokua-MKRLV as that is the most popular Kokua variant (and also usually the most recently committed to since it gets updated in the last stage of the work flow below). We do not specify a master branch because the Kokua repo maintains three different releases so there is no single "master". Please open a jira issue and attach the file to the issue.Ĭontributions by frequent contributors or Kokua Team members requires a formalized work flow as outlined below. ![]() Before trying to build Kokua make sure that you can successfully build the standard LL Viewer.Ĭontributing one patch with less than 3 files touched can be submitted as a diff or patch file. In buildable form and also the limited resources of the current team. This is due in part to the use of licenced components which we cannot share Please note: We do not provide support for self-building outside of the active Kokua team. ![]()
0 Comments
Leave a Reply. |