Opened 3 years ago

Closed 3 years ago

#24123 closed defect (fixed)

Add comment to tor-browser-bundle.git changelog to indicate deprecation

Reported by: arthuredelstein Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Right now the alpha branch has already transitioned to tor-browser-build.git, so it would be nice to indicate that in the changelog. We can make a similar comment once the release branch has made the switch as well. Suggested by arma.

Child Tickets

Change History (4)

comment:1 Changed 3 years ago by gk

Cc: arma added
Status: newneeds_information

07:53 <+GeKo> armadev: i don't understand what you want in #24123. The big note in the README that got added is not enough?
07:54 <+GeKo> you want to have a similar note in the changelog file?
07:54 <+GeKo> does not seem to be the right place for such a note to me
07:56 <+GeKo> plus we updated the tor browser hacking document pointing to the new system

comment:2 Changed 3 years ago by mcs

Have some people bookmarked the ChangeLog.txt file? That would be an argument for adding a note there. But since the branch that is used changes over time a simple bookmark would only work for a while. I guess the concern is that people know how to go find the changelog and may not realize the location has changed. Should we start placing ChangeLog.txt on when we make a new release?

comment:3 Changed 3 years ago by arma

Ah ha -- I did indeed just go to the same url that my browser already knew. So I had no idea that some words had been written somewhere else that I didn't know to look at.

Maybe a more thorough (ongoing) fix is in order here? Like, when you say "changelog" in each blog post, make that a link?

comment:4 Changed 3 years ago by gk

Resolution: fixed
Status: needs_informationclosed

Okay, we are doing the "link to the actual changelog in the blog post" now.

Note: See TracTickets for help on using tickets.