[Adium-devl] 1.2 ?!?
David Smith
catfish.man at gmail.com
Tue Dec 25 23:05:38 UTC 2007
On Dec 25, 2007, at 2:57 PM, Evan Schoenberg wrote:
>
> On Dec 25, 2007, at 4:03 PM, Colin Barrett wrote:
>
>> On Dec 25, 2007, at 11:32 AM, Evan Schoenberg wrote:
>>
>>> Trust our upstream friends a bit. A minor release of Adium - our
>>> changes - could carry a major libpurple upgrade -the Pidgin team's
>>> changes. We're all on the same team in a broader sense, but the
>>> separation of powers affords us fantastic benefits.
>>
>> I still don't understand why a minor release of Adium should have a
>> major release of libpurple in it. I trust the pidgin folks, but it
>> still makes little sense to take such large changes in dot releases.
>>
>> I have never understood why our micro releases are so huge, but I'm
>> not doing the releasing so I guess it's not up to me.
>
> Well, there a couple of problems at work.
>
> This idea of a micro release containing only micro features, while
> all major feature work takes place on trunk, is part of the problem.
> We end up with all major new features or fixes lumped into a single
> 'trunk', which ends up nearly-permanently blocking release of the
> 'next major version'.
>
> On the other hand, Adium 1.1 and 1.2 were both really Summer of Code
> driven, and that was also a mistake in some way... but I don't know
> how else it could be handled. Take a single person - no matter how
> dedicated or bright - and have them hack for a summer, with minimal
> supervision or code review or testing by third parties, and then
> arbitrarily merge all those changes and you get a significant problem.
I think we should double up on mentors next year, even if it means
accepting less students.
David
More information about the devel
mailing list