[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #3827 [Tor Browser]: torbrowser lacks changelog
#3827: torbrowser lacks changelog
-------------------------+--------------------------------------------------
Reporter: phobos | Owner: mikeperry
Type: defect | Status: new
Priority: major | Milestone: TorBrowserBundle 2.2.x-stable
Component: Tor Browser | Version:
Keywords: | Parent:
Points: | Actualpoints:
-------------------------+--------------------------------------------------
Comment(by erinn):
Well, who are the changelogs for? I think the answer to that helps decide
the format. Changelogs for developers are way different from changelogs
for users. I'd been using the git repo as a 'dev changelog', and leaving
only obvious high-level changes in the README/changelog in the bundle
itself.
I'm happy to add more detail though. But in the case of prefs.js changes,
which are actually mikeperry-driven (usually), and other such things, I
think we should adopt a tor-repo-esque situation where if someone
contributes a change, they also contribute a well-summarized changes file.
As for the patches, those are documented within the patches themselves,
and that is the appropriate place according to the HACKING doc in
torbrowser.git/maint-2.2. And with past releases, I think we should begin
relatively "new" with maint-2.2, go through and look through git commits &
the changelog itself, and flesh out the missing pieces in a doc that is
not HACKING, but something more appropriately named (not changelog.omnibus
either, but... well, maybe!)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3827#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs