Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #8821 define and enforce immutable tags
Actions
Summary
Empty
define and enforce immutable tags
Empty
Empty
Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#8821
Manuel Vacelet (vaceletm)
2016-03-23 14:52
2016-01-29 12:18
4653

References
Artifact links
Referencing story #8821

Artifact Tracker v5

epic #8812 Multiple svn repositories per project
rel #8869 8.13

Git commit

tuleap/tuleap/stable

Immutable TAG, create admin interface 9b898b8e15
User avatar Marie Ange Garnier (marieange) , 9 years ago
Activate pre-commit-hook mechanism b7f3ba06e8
User avatar Marie Ange Garnier (marieange) , 9 years ago
Immutable TAG, update admin interface adding whitelist fb3de4a9b8
User avatar Marie Ange Garnier (marieange) , 9 years ago
Move section presenter into a dedicated file fb0f91f60e
User avatar Marie Ange Garnier (marieange) , 9 years ago
Referenced by story #8821

Other

gerrit #5287
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)9 years ago

The specs are simple do at svn plugin / repository level what is possible in core svn at repository level.

As of today, only project admins can administrate repositories in svn plugin

User avatar
Nouha Terzi (terzino)9 years ago
Hello team,

Could you please share with us the spec for this story?
At least could you please tell us if the tags will be managed repo per repo or for whole project? And what about the svn admin? Are they repo per repo or by project?
thank you for your answers?
close
by