I agree to it. Having one package which deploys both backend and frontend is better
Sent from my iPhone > On 03-Dec-2020, at 7:09 PM, pau...@apache.org wrote: > > PMC members, PLEASE ONLY RESPOND ON THE DEV THREAD. > > > > Hi all, > > > > Please read all of this, I know it's a bit wordy.. > > > > We're pretty much there wrt to RC1 of CloudStack and the updated UI. We > have one issue remaining, and that is about the packaging and voting on > CloudStack 'engine' and its UI. > > The UI has been developed asynchronously, but at time of a CloudStack > release, we really need to be able have definite link between the two > codebases so that we release 'one thing' when we release CloudStack. > > > > A while back, I created a proposal [1], which I'd like to again put forward > as the default process unless there are any objections. > > > > In addition; > > > > 1. I think that the repo 'apache/cloudstack-primate' should be renamed to > '/apache/cloudstack-ui', to keep everything just 'cloudstack'. > > > > 2. In the repo RPM/DEB packaging make cloudstack-ui a dependency of > cloudstack - and finally, when creating the repo, include both the > 'cloudstack' and 'cloudstack-ui' RPMs/DEBs so that there is one repo > (http://download.cloudstack.org/centos7/4.15/) which contains both. > > > > PS - PMC members, PLEASE ONLY RESPOND ON THE DEV THREAD. > > > > [1] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=165222727 > > > > Kind regards > > > > Paul Angus >
