elastic / package-storage

Package storage for packages served through the package registry service

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Decide what to put on the landing page of package-storage

ruflin opened this issue · comments

Currently the master branch is shown when landing on the package-storage page. It should be decided on what to show or which branch. See also conversation here: #116 (comment)

Honestly, I would be for removing master branch at all, not to confuse people. Simply set one of the others as default, e.g. snapshot. WDYT @ycombinator ?

This is one option. But I think there is some value in having a branch where we can put shared things across the branches like docs or scripts. I think @kuisathaverat also has this requirement for CI.

Yeah, I'm ++ for keeping the master branch to use for a landing page and also any other administrative information, scripts, etc. I would, however, make it very clear at the top of the README that no packages should go in this branch and then explain the rest of the branches, etc.

we need the master branch to manage the job definitions in the CI, we could rid of it by making an exception for this repo on the JJBB definition, not a big deal but outside of the regular standard. So we can do it but first, we have to change the job definitions to another branch.

I think we can close it now, as we're planning to move away from the Package Storage v1 so Github repository.