Page History

...

I think in the stage repository we should limit the access. Nobody should allow to download the artifacts in the staging repositories other than the developers,QA people, archiva admin user ,and the the guy who have the permission for the promotion.
Here for the QA, promotion and the developers i am going to use current archiva roles(Repository Manager and Repository Observer) and assign the permission for them.

I think by default it is the repository manager's task to create the stage repositories and attach it to the main repository that he want to add the staging functionality.But those permissions should be configured to any role according to the requirements.

Creating Roles for this staging repository

...

• implementing the read action and the write actions and assign them to the developer(role)and the QA person(role) as mentioned in above.existing roles.
  (Repository Manager and Repository Observer)

• implementing the promotion role.(only the merging based on the assumption that new artifact is being deployed.Not a update version)

...