Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
OpenWalnut Core
OpenWalnut Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 44
    • Issues 44
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • OpenWalnut
  • OpenWalnut CoreOpenWalnut Core
  • Issues
  • #363

Closed
Open
Opened May 08, 2017 by Alexander Wiebel@wiebel
  • Report abuse
  • New issue
Report abuse New issue

-RM-43-MR-Do we want tickets l for the release process in the new issue tracker?

I am talking about the following tickets in the old system: #497 Check Performance for 1.3 new task blocker OpenWalnut 1.3 #498 Release OpenWalnut 1.3 new task blocker OpenWalnut 1.3 #499 Create tarball for 1.3 release and test it new task blocker OpenWalnut 1.3 #500 Check ReleaseToDo for 1.3 new task blocker OpenWalnut 1.3

The new release amanger should decide this.

(from redmine: created on 2011-09-12, closed on 2011-09-15)

To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
OpenWalnut 1.3
Milestone
OpenWalnut 1.3
Assign milestone
Time tracking
None
Due date
None
1
Labels
Bug
Assign labels
  • View project labels
Reference: openwalnut/openwalnut#363