I have a branch where I'm using a single branch: https://github.com/clebertsuconic/activemq-website/tree/test
The only concern I have so far is that any time I build, I get a change into a schema: Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) typechange: content/schema/core/activemq-core.xsd Although I would consider that anyone would check stuff before committing.. Any ideas? On Wed, Oct 2, 2019 at 1:03 PM Justin Bertram <[email protected]> wrote: > > If it's simpler and documented that sounds like a win to me. > > > Justin > > On Wed, Oct 2, 2019 at 11:41 AM Robbie Gemmell <[email protected]> > wrote: > > > On Wed, 2 Oct 2019 at 16:47, Clebert Suconic <[email protected]> > > wrote: > > > > > > On Wed, Oct 2, 2019 at 10:44 AM Robbie Gemmell <[email protected]> > > wrote: > > > > Thats what we do at Qpid and what I've seen other > > > > projects do, I find it simpler overall. > > > > > > Tl;DR: > > > I'm all +10000000 on this... what we need to change on infra. > > > > > > Can we keep the history from master > > > > > > We wouldnt need to change much to get everything on the same branch I > > dont think, and it seems like we can do so without infra: I just tried > > on your last commit as a test and was able to force-push the asf-site > > branch in the website repo. > > > > So basically it seems it needs something like: repopulate the asf-site > > branch (or a test branch) with the master history locally, simplify > > the build script to only build and nothing else, fix up the .gitignore > > file appropriately, build things, commit, and [force] push. > > > > Assuming of course others agree that it is what should happen? > > > > Robbie > > -- Clebert Suconic
