Let's release 2.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Let's release 2.1

Augustin Trancart
Hi everyone,

Since the release of 2.0.0, a lot of works has been done on itowns :
- pointcloud from potreeconverter support has been added
- 3dtiles support has been greatly improved (or added, I don't remember when
initial support got merged :-D) : pnts and b3dm support, batch table, gltf...
- WFS, geojson, gpx, kml support, and solutions to "rasterize" them.
- better integration solution for custom controls and other updatable elements
through "frame requesters"
- Our set of examples is getting bigger and bigger :-)
- countless bug fixes...

As we are going to communicate a lot on itowns and these new features, I propose
to release a v2.1.0 release before the end of the week. Let's have a npm package
ready for people to experiment.

If you guys are ok with that, I'll do it on Thursday or Friday. If it's too
short for your very important bugfix/feature/refacto, don't worry: as long as
your change don't break the API, we can release as many minor or patch version
as needed to stabilize this v2.1.

After that, I guess we should discuss one day  about the rythm of release, if we
maintain a bugfix branch, and other questions related to the cycles of life of
itowns. Until that, I propose that every change landing in master would be for a
version 3, and I'll create a v2.1 branch for eventual backported bugfixes.

Cheers,

--
Augustin Trancart - Oslandia
[hidden email]


_______________________________________________
iTowns-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/itowns-dev

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Let's release 2.1

Alexandre Devaux
Hi all,

I'm totally up for that, let's release a 2.1 in the next days!
As you propose we should try to review/incorporate a maximum number of PR before friday.

See you!


--
Alexandre Devaux
Chargé d'Etudes et de Recherche
Laboratoire MATIS, IGN
Tel: 01 43 98 85 73

________________________________________
De : iTowns-dev [[hidden email]] de la part de [hidden email] [[hidden email]]
Date d'envoi : mardi 12 septembre 2017 21:00
À : [hidden email]
Objet : iTowns-dev Digest, Vol 15, Issue 1

Send iTowns-dev mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.osgeo.org/mailman/listinfo/itowns-dev
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of iTowns-dev digest..."


Today's Topics:

   1. Let's release 2.1 (Augustin Trancart)


----------------------------------------------------------------------

Message: 1
Date: Tue, 12 Sep 2017 19:33:27 +0200
From: Augustin Trancart <[hidden email]>
To: "[hidden email]" <[hidden email]>
Subject: [iTowns-dev] Let's release 2.1
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

Hi everyone,

Since the release of 2.0.0, a lot of works has been done on itowns :
- pointcloud from potreeconverter support has been added
- 3dtiles support has been greatly improved (or added, I don't remember when
initial support got merged :-D) : pnts and b3dm support, batch table, gltf...
- WFS, geojson, gpx, kml support, and solutions to "rasterize" them.
- better integration solution for custom controls and other updatable elements
through "frame requesters"
- Our set of examples is getting bigger and bigger :-)
- countless bug fixes...

As we are going to communicate a lot on itowns and these new features, I propose
to release a v2.1.0 release before the end of the week. Let's have a npm package
ready for people to experiment.

If you guys are ok with that, I'll do it on Thursday or Friday. If it's too
short for your very important bugfix/feature/refacto, don't worry: as long as
your change don't break the API, we can release as many minor or patch version
as needed to stabilize this v2.1.

After that, I guess we should discuss one day  about the rythm of release, if we
maintain a bugfix branch, and other questions related to the cycles of life of
itowns. Until that, I propose that every change landing in master would be for a
version 3, and I'll create a v2.1 branch for eventual backported bugfixes.

Cheers,

--
Augustin Trancart - Oslandia
[hidden email]

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osgeo.org/pipermail/itowns-dev/attachments/20170912/c0d1a19b/attachment-0001.sig>

------------------------------

Subject: Digest Footer

_______________________________________________
iTowns-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/itowns-dev


------------------------------

End of iTowns-dev Digest, Vol 15, Issue 1
*****************************************
_______________________________________________
iTowns-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/itowns-dev