Re: AP v1.4.1: Dependency Building: Broken

--001485f0e778d7a750046acc6ad3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

>
> Unfortunately not. Imagine someone has 1.4.1 installed and installs
> your package. 1.4.1 would still look for the apkg-installer file. So
> the first release I can "really" fix it is 1.6.


I had a feeling you might write something like that :-).  I should've taken
more time to think it through.


>  That's good to hear. Anyway I've released 1.4.2 just now (still some
> problems with the developer tools, give me a second).


Thanks for releasing v1.4.2, which I'll test in the near future.  I'll let
you know whether or not I find any bugs.

I wonder if breaking bugs like this should increment minor version, or if we
> need another number.
>
> Something like that:
>
> major.minor.patch.build
> <very big changes>.<big changes>.<breaking bug fixes>.<nice to have bug
> fixes>
>
> And make it so only change of the last number can be ignored.


I think that's a good idea, but we'd wanna avoid the Firefox v2 style of
versioning overkill: v2.0.0.20.

--001485f0e778d7a750046acc6ad3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"borde=
r-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-le=
ft: 1ex;">Unfortunately not. Imagine someone has 1.4.1 installed and instal=
ls<br>



your package. 1.4.1 would still look for the apkg-installer file. So<br>
the first release I can &quot;really&quot; fix it is 1.6.</blockquote><div>=
<br>I had a feeling you might write something like that :-).=C2=A0 I should=
&#39;ve taken more time to think it through.<br>=C2=A0<br></div><blockquote=
 class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); =
margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">



<div>
</div>That&#39;s good to hear. Anyway I&#39;ve released 1.4.2 just now (sti=
ll some<br>
problems with the developer tools, give me a second).</blockquote><div><br>=
Thanks for releasing v1.4.2, which I&#39;ll test in the near future.=C2=A0 =
I&#39;ll let you know whether or not I find any bugs.<br><br><blockquote st=
yle=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex=
; padding-left: 1ex;" class=3D"gmail_quote">


I wonder if breaking bugs like this should increment minor version, or if w=
e need another number.<br><br>
Something like that:<br><br>
major.minor.patch.build<br>
&lt;very big changes&gt;.&lt;big changes&gt;.&lt;breaking bug fixes&gt;.&lt=
;nice to have bug fixes&gt;<br><br>
And make it so only change of the last number can be ignored.</blockquote><=
div><br>I think that&#39;s a good idea, but we&#39;d wanna avoid the Firefo=
x v2 style of versioning overkill: v2.0.0.20.<br><br></div>


</div></div>

--001485f0e778d7a750046acc6ad3--