Re: [tor-bugs] #20000 [Core Tor/Tor]: Improve our release process: we need fewer surprises.

2017-06-30 Thread Tor Bug Tracker & Wiki
#2: Improve our release process: we need fewer surprises.
--+--
 Reporter:  nickm |  Owner:
 Type:  project   | Status:  closed
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 I believe 0.3.0 and 0.3.1 have been going much much better, due to
 sticking with deadlines, sharing the work, etc.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #20000 [Core Tor/Tor]: Improve our release process: we need fewer surprises.

2016-08-26 Thread Tor Bug Tracker & Wiki
#2: Improve our release process: we need fewer surprises.
--+
 Reporter:  nickm |  Owner:
 Type:  project   | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Description changed by nickm:

Old description:



New description:

 Apologies for submitting this with no text: I wanted to grab ticket #2
 while it was available.

 This ticket will be about ways to improve our release process.  My current
 major complaints about the last series have been:

   * 0.2.9 began too large, and took too long to get clarity on must vs
 should vs could.
   * 0.2.9 had us delay our freeze date by 1.5 months. Should we have seen
 that coming earlier?
   * During the 0.2.9 series, we managed to "forget about" too many items
 and have them "appear" on our radar with less flexibility than we'd like.
   * 0.2.8 took far too long between freeze and stability. Why?
   * 0.2.8 has had a nonzero number of post-release regressions
   * 0.2.7.7 never shipped, and probably shouldn't ship as it stands.
   * 0.2.7 is in a zombie state right now.
   * 0.2.7 shipped with a nonworking ed25519 voting algorithm.
   * Versions earlier than 0.2.7 should really be starting to decommision.
 Why are they still around? What can we do to get more uptake?

--

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #20000 [Core Tor/Tor]: Improve our release process: we need fewer surprises.

2016-08-26 Thread Tor Bug Tracker & Wiki
#2: Improve our release process: we need fewer surprises.
--+
 Reporter:  nickm |  Owner:
 Type:  project   | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs