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
I think you're right. I'll pull the the translations, tag release and
run the machinery!
On Tue, Aug 23, 2016 at 09:58:27AM +0200, Sebastiaan Couwenberg wrote:
> On 01/04/16 20:31, Ladislav Laska wrote:
> > I've decided to roll out 0.18.3 milestone later this month. The progress
> > can be
> >
On 01/04/16 20:31, Ladislav Laska wrote:
I've decided to roll out 0.18.3 milestone later this month. The progress can be
seen on github milestone:
https://github.com/openstreetmap/merkaartor/milestones/0.18.3
0.18.3-rc1 has been out for some time now, and there are no open issues
for the