Opened 4 years ago

Last modified 16 months ago

#15007 reopened defect

Allow to specify version for components rather than tor only

Reported by: krichter Owned by: gk
Priority: Medium Milestone:
Component: Internal Services/Service - trac Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If a component (e.g. "Tor browser") is selected in a bug report it makes more sense to specify the version of that component rather than the tor version because tor might not have to do anything with the issue at all.

Child Tickets

Change History (7)

comment:1 Changed 4 years ago by gk

Component: - Select a componentTrac
Owner: set to erinn

comment:2 Changed 4 years ago by arma

Owner: changed from erinn to gk
Status: newassigned

I gave gk admin privs for trac, so now he can do this himself.

comment:3 Changed 4 years ago by gk

Resolution: fixed
Status: assignedclosed

I created "Tor Browser alpha" and "Tor Browser stable". I am not convinced yet that we need something more fine-grained.

comment:4 Changed 4 years ago by krichter

I created "Tor Browser alpha" and "Tor Browser stable". I am not convinced yet that we need something more fine-grained.

The idea is to separate the metadata from the ticket full text. If you agree with that, then adding trac version for each version of the software is necessary, otherwise it might even be non-constructive to let the reporter specify a non-constant value ("alpha", "stable") because the metadata is not only lost, but even errornous/misleading after a new release.

The thing about trac/the configuration of trac.torproject.org is that the availability of version values doesn't reflect the component (i.e. I don't need to see versions which don't apply to the selected component). -> Can you clarify whether this is a trac issue or a configuration issue, please? -> then I'd file a ticket for changing the issues described in this paragraph (as an issue of trac or an issue of this instance) and leave this issue open to change to (automatically generated) constant version numbers for the tor browser (and potentially a lot of other components) after the prerequisites are fulfilled.

comment:5 in reply to:  4 Changed 4 years ago by gk

Resolution: fixed
Status: closedreopened

Replying to krichter:

I created "Tor Browser alpha" and "Tor Browser stable". I am not convinced yet that we need something more fine-grained.

The idea is to separate the metadata from the ticket full text. If you agree with that, then adding trac version for each version of the software is necessary, otherwise it might even be non-constructive to let the reporter specify a non-constant value ("alpha", "stable") because the metadata is not only lost, but even errornous/misleading after a new release.

Yes, you are right about that. Maybe something like tor-browser-4.0-stable and tor-browser-4.5-alpha would be a better option then? I have to think about it a bit more. We are currently tracking everything with keywords and it is working so far.

comment:6 Changed 4 years ago by qbi

Component: TracService - trac

Move all tickets from trac to "Service - trac" component.

comment:7 Changed 16 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.