Re: AP v1.4.2: Dependency Building: Still Broken

On Fri, May 29, 2009 at 11:28 AM, Jan Niklas Hasse <[email protected]> wrote=
:
> On Fri, May 29, 2009 at 8:34 AM, Chris Giles <[email protected]> wrote=
:
>>> Yeah. I think a good idea would be just to accept AutopackageTargets
>>> with 3 numbers.
>>
>> Yep, let's do that.=C2=A0 I use the same approach for my applications.
>
> Okay, I'll try to implement that (Should be just changing a few lines
> in makepackage, right?).

>> I think that's a good idea: throw away the intermediate testing subversi=
on
>> approach.
>
> Isak, what do you think?

Well, the obvious argument against it is that "stable" releases will
be more unstable than they already are. Bigger chance of nasty bugs to
hit end users.

It will also make the introduction of large changes much harder, since
there would be no intermediate release to put them in.

That said, given the limited amount of manpower - both developers and
testers - it maybe sane to skip the unstable release series since I
guess very few actually tests it.

>> Just make sure that the remote dependency resolution feature is tested
>> before each release and you'll keep me happy.=C2=A0 I'm sorry to write t=
hat it
>> still appears to be broken in v1.4.2.

Jan Niklas: to help reduce these kind of problems, you should go for a
release candidate and then Chris could've tested it by setting
AUTOPACKAGE_RUNTIME to this new version without the release having to
hit end users.

-Isak

---------------------------------------------------------------------
To unsubscribe, e-mail: autopackage-dev-unsubscribe-OfajU3CKLf1/[email protected]
For additional commands, e-mail: autopackage-dev-help-OfajU3CKLf1/[email protected]