[iTowns-dev] iTowns-dev Digest, Vol 13, Issue 2
Mirela.Konini at ign.fr
Sun Jun 25 13:47:08 PDT 2017
Of course I do agree to release soon.
I think at least check elevation values (#332), miniglobe (#239) and obviously documentation (#322) must be included.
De : iTowns-dev [itowns-dev-bounces at lists.osgeo.org] de la part de itowns-dev-request at lists.osgeo.org [itowns-dev-request at lists.osgeo.org]
Date d'envoi : vendredi 23 juin 2017 21:00
À : itowns-dev at lists.osgeo.org
Objet : iTowns-dev Digest, Vol 13, Issue 2
Send iTowns-dev mailing list submissions to
itowns-dev at lists.osgeo.org
To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
itowns-dev-request at lists.osgeo.org
You can reach the person managing the list at
itowns-dev-owner at lists.osgeo.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of iTowns-dev digest..."
1. Re: Let's release v2.0 ! (Vincent Picavet (ml))
Date: Fri, 23 Jun 2017 11:19:45 +0200
From: "Vincent Picavet (ml)" <vincent.ml at oslandia.com>
To: "itowns-dev at lists.osgeo.org" <itowns-dev at lists.osgeo.org>
Subject: Re: [iTowns-dev] Let's release v2.0 !
Message-ID: <347e6275-dd87-b353-1e7b-772cd1ee1bc2 at oslandia.com>
Content-Type: text/plain; charset=utf-8
No objection to this proposal, should we therefore plan for the release
on the 5th of July ?
If still no disagreement, I will set this date for the GitHub milestone,
and we will start working on the required tasks for release.
On 16/06/2017 15:14, Vincent Picavet (ml) wrote:
> Hi all,
> We announced last year that iTowns 2.0 would be released at the end of
> 2016. We are now mid-2017, and it is more than time to release !
> We had to refactor and clean up a lot of things before being able to
> release. With the PRs merged lately, the master branch is now stable,
> the architecture is good, and we have the basic set of features we need
> to be able to go out in the wild.
> We agreed before on a "release soon, release often" strategy, let's do
> that, we are very very close to being ready.
> Our timeframe for the release is shortening though :
> - if we do not release before the summer, we take a huge risk of not
> being able to release before october, with the vacations of most of the
> developers, and the busy period of september. This would mean almost a
> year delay, which is not acceptable
> - two main opensource GIS events take place this summer, FOSS4G-Europe
> and FOSS4G international in Boston. This is the best time to communicate
> on new products, and again, if we miss this opportunity, it would mean a
> long delay before such communication opportunities arise again
> I therefore propose to set the date for the release on the 5th of July,
> This schedule allows to polish up things between now and the 5th, and
> also prepare additional elements for the release ( website,
> communication announcement & such).
> If there is no strong disagreement before next tuesday with credible
> alternative proposals, I propose to stick to this plan, and get ready
> for its implementation : create GH milestones, PR and issues triaging,
> start work for communication and demos.
> This does not prevent to work on further features, examples,
> documentation and all the great things required to make itowns better.
> Once the v2.0 has been released, we can enter a real "release soon,
> release often" mode, improving this piece of software with short iterations.
> What do you think about planning ahead the release after 2.0, fixing the
> schedule sometime in september ?
> Bottom line : if you have things you really want to be in v2.0, get down
> to work now, and before the 5th of July. Otherwise do not worry, you
> will still get opportunity to have the work released in the next version
> Best regards,
> iTowns-dev mailing list
> iTowns-dev at lists.osgeo.org
Subject: Digest Footer
iTowns-dev mailing list
iTowns-dev at lists.osgeo.org
End of iTowns-dev Digest, Vol 13, Issue 2
More information about the iTowns-dev