#29723 closed defect (implemented)

Document next steps and/or tickets remaining

Reported by: juga Owned by: juga
Priority: Medium Milestone: sbws: 1.1.x-final
Component: Core Tor/sbws Version: sbws: 1.0.5
Severity: Normal Keywords: no-changes-version, docs
Cc: gaba Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:


Since soon i'll have less time to work on this, gaba proposed i create a document explaining which would be the next steps.
This would be basically the open tickets, but probably it requires some other explanation and/or (re-)assign milestones to tickets, close some or open others.

Child Tickets

Change History (6)

comment:1 Changed 16 months ago by juga

Owner: set to juga
Status: newassigned

Started to close old tickets and open new tickets, also as part of #28589

comment:2 Changed 16 months ago by juga

Cc: gaba added; juga removed

comment:3 Changed 16 months ago by juga

Keywords: no-changes-version added

Add keyword to help planify releases/milestones.
Tickets that doesn't imply a change of version are tickets which do not affect the code (docs, tests) and some time of refactors.

comment:4 Changed 16 months ago by juga

Keywords: docs added

Add keyword. docs are tickets that affect to documentation

comment:6 Changed 16 months ago by juga

Resolution: implemented
Status: assignedclosed

I guess i can assume this as done, and elaborate more the wiki page in the next weeks/as needed.

Note: See TracTickets for help on using tickets.