[tor-bugs] #2620 [Vidalia]: Vidalia 0.2.11 release and future workflow
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Thu Feb 24 16:19:09 UTC 2011
#2620: Vidalia 0.2.11 release and future workflow
---------------------+------------------------------------------------------
Reporter: chiiph | Owner: chiiph
Type: task | Status: needs_review
Priority: normal | Milestone:
Component: Vidalia | Version:
Keywords: | Parent:
Points: | Actualpoints:
---------------------+------------------------------------------------------
Comment(by chiiph):
Replying to [comment:13 edmanm]:
> Replying to [comment:11 chiiph]:
> > I don't quite understand this: you are ok with everything being in
git, and you want to review changes in Vidalia-stable? and you are ok with
Vidalia-alpha releases?
>
> Alright, let me try to rephrase again: I think having a branch for you
and whoever else wants to work on big changes is a great idea. I think
releasing big changes without review is a bad idea for now, even if you
just call it an alpha. I think git is annoying, but if that's what y'all
want to use then I won't whine about it (well, at least not too much ;).
Clearer?
It's not like the plan is to release a new alpha version every week. Every
change will have its testing period, they aren't going to get to alpha as
soon as they are committed to the repo. The idea behind this is to not
stop the developing process and have people testing the new features.
I've already seen people wanting to test Vidalia's new features, but when
I said "clone the repo and build it" they run away.
>
> Now, admittedly I don't have the bandwidth available at the moment to
review changes with the frequency that you want for regular releases,
which is why I seem to have this same conversation with various people
every few weeks. So if you want to "damn the torpedos" and release
anything and everything as an "alpha", I'm not going to whine about it.
You'll get your feedback on whether things break that way, hopefully
people don't mind if things do break, and what doesn't break can
eventually make its way to "stable". At that point, there's not much point
in me reviewing it again, since it's already been released in some "alpha"
build. I was just trying to help avoid releasing broken stuff in the first
place.
The alpha releases aren't thought as: "lets see if someone complains of
some breakage, if not, we can assume it works", it's more because, for
example with the GUI, people
already have complained, so lets see what they think about this new
approach.
Since you don't have the bandwidth at this moment, but a couple of us do,
we are just trying to figure out a way for this to workout.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2620#comment:14>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list