Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
scriptorium
scriptorium
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • degrowth
  • scriptoriumscriptorium
  • Issues
  • #217

Closed
Open
Opened Feb 04, 2018 by jon richter@yala
  • Report abuse
  • New issue
Report abuse New issue

There is no release process

Currently patches are developed on feature branches and then merged into deployment. From there they are pushed to production.

Unfortunately we missed #216 and as such have no versioning and release cycle at hands, which would allow to identify spikes in development much more easier in retrospect.

Assignee
Assign to
Long-term stability of the conference platform
Milestone
Long-term stability of the conference platform
Assign milestone
Time tracking
None
Due date
None
1
Labels
deployment
Assign labels
  • View project labels
Reference: degrowth/scriptorium#217