I'll take a look into it, thanks!
On Tue, Sep 06, 2016 at 03:34:19PM +0200, Sebastiaan Couwenberg wrote:
> On 09/06/2016 02:46 PM, Ladislav Laska wrote:
> > Yes, I expected some trouble. I didn't want to go the 0.18.3.1 way, as
> > I'm unsure what else would break with the next version number.
>
On 09/06/2016 02:46 PM, Ladislav Laska wrote:
> Yes, I expected some trouble. I didn't want to go the 0.18.3.1 way, as
> I'm unsure what else would break with the next version number.
>
> In the future, I will use x.y.z as major.minor.patch in hopes to release
> new features with major/minor
Yes, I expected some trouble. I didn't want to go the 0.18.3.1 way, as
I'm unsure what else would break with the next version number.
In the future, I will use x.y.z as major.minor.patch in hopes to release
new features with major/minor change and use patch for bug fixing
releases only.
By the
Hi!
I have just finished the Windows build and published the 0.18.3 release.
See http://merkaartor.be .
I had some issues with build system and had to make an alternative. I
also took the opportunity to get in a few last minute fixes.
Unfortunately, 0.18.3 tag was on another commit for some time
