bwauth improvements (ex-parent ticket for SoP planned tasks)

changed milestone to %sbws: unspecified

added component::core tor/sbws milestone::sbws: unspecified owner::juga priority::medium severity::normal status::assigned type::defect labels

Hi juga, please make the other trac tickets in your list of work into children of this task. You can make a ticket into a child of this ticket by setting its Parent ID to "#25925 (moved)".

I did it, but without "#", fixed. That has changed old parents of some bugs.

Trac:
Component: Core Tor/Tor to Core Tor/sbws

Now that SoP finished, should this ticket be closed?, should the remaining opened tickets be made:

• childs of a new parent ticket (PF?)
• assigned a component (what about having a tor-bwauth component and not just keyword?)
• tagged as tor-bwauth?
• leave orphan?

Replying to juga:

Now that SoP finished, should this ticket be closed?, should the remaining opened tickets be made:

• childs of a new parent ticket (PF?)

Some of these tasks are important, and others are not.

Let's:

• work out which tasks we need to do
• find out if any tasks are missing
• put the tasks we need to do under a new parent ticket

• assigned a component (what about having a tor-bwauth component and not just keyword?)

In Core Tor, we have a component for each piece of software. (The DirAuth component is for directory authority config changes.)

"tor-bwauth" is not a component, it's a group of related tasks in different components. These tasks are already assigned to Tor, sbws, Torflow, and Chutney.

• tagged as tor-bwauth?

Good idea! We can also tag them with bwauth-sop-2018 so we know which tasks used to be under this ticket.

• leave orphan?

If a task is not important, it can be an orphan.

Change title to reflect current situation. Not creating a new parent or changing children at the moment.

Trac:
Summary: Bandwidth scanner parent ticket for SoP planned tasks to bwauth improvements (ex-parent ticket for SoP planned tasks)

Trac:
Milestone: N/A to sbws: unspecified

I think this parent would be more useful to track only Core-Tor tickets, since sbws can be track by component. If you agree, i'll remove the children that are sbws and leave only the Core-Tor ones.

Replying to juga:

I think this parent would be more useful to track only Core-Tor tickets, since sbws can be track by component. If you agree, i'll remove the children that are sbws and leave only the Core-Tor ones.

Ok, that works.

Or you can just use a keyword to track Core Tor tickets. Whatever is easier for you.

mentioned in issue #25947 (moved)

mentioned in issue #26007 (moved)

mentioned in issue #26155 (moved)

mentioned in issue #26200 (moved)

mentioned in issue #26692 (moved)

mentioned in issue #26702 (moved)

mentioned in issue #26740 (moved)

mentioned in issue #26905 (moved)

mentioned in issue #28519 (moved)

mentioned in issue #28547 (moved)

mentioned in issue #28599 (moved)

mentioned in issue #28600 (moved)

moved to tpo/network-health/sbws#25925 (closed)