[Adium-devl] 1.4a1 planning
Eric Richie
eric at adiumx.com
Sun Apr 12 22:01:55 UTC 2009
2009/4/12 Evan Schoenberg <evan.s at dreskin.net>:
>
> On Apr 12, 2009, at 4:17 PM, Zachary West wrote:
>
> On Fri, Apr 10, 2009 at 15:01, Jordan <jas8522 at gmail.com> wrote:
>
> Regardless of 1.3.4 happening or not, I think Eric is right about
>
> using the nightlies as 'alphas'.
>
> Update libpurple, throw in the localization fixes—that is 1.3's
> legacy. Just like our 10.2 users, we've got to say "enough is enough,
> you're using an older OS, use older software." 10.5 is being adopted
> faster than 10.3+ ever was, anyway. This is yet another reason why it
> should come after 1.4; it's just a maintenance release.
>
> The expectation or plan that 1.3.x would be maintained like 1.4 is
> being developed was a pipedream; I just don't see the developer muscle
> to maintain two separate, and nearly independent (due to massive code
> changes in 1.4) code bases at once. Especially given how few people
> are actively developing right now.
>
>
> I agree with Zac 100%. Pretending to maintain a codebase nobody on the
> development is using, porting fixes which required manual changes and
> merging to work, would be doing nobody any favors - least of all this small
> band of intrepid coders.
That's what I said anyway. My exact quote was "I'd rather release it and
call it dead." The it in this case being 1.3.4. If we were ready to
release it soon after the last meeting anyway, let's release it and
then wash our hands of the whole 1.3.x branch. I never pretended to
suggest we keep developing 1.3.x for eternity. It's just that we
already have fixes in that branch waiting for release so I'd like to
just take care of them with a release and be done with it.
> I think we should completely drop 1.3.x after 1.3.4, and it should
> really only contain minor changes anyway. None of this backporting
> fixes (even critical crashes that are fixed in 1.4).
Hells no. No backporting. That would be silly. Like I said above, I
just want to see us get the fixes we had already made out there.
More information about the devel
mailing list