You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sis.apache.org by Martin Desruisseaux <ma...@geomatys.com> on 2018/06/19 17:06:53 UTC
Proposed development branch: geoapi-4.0
Hello all
Following on the discussion about what could be the name of the
development branch (formerly "JDK8"), I propose "geoapi-4.0", for
consistency with another branch named "geoapi-3.1". More details on
those two branches are given there:
http://sis.staging.apache.org/branches.html
I'm tempted to delete the other branches since they are stalled and
should not be used for more development (in part because of the Git
history rewrite, but also because SIS has evolved since the last commit
on those branches). Those branches are still available on Subversion; if
their development restart, we would probably have to port the code to
latest commit on the development branch anyway.
Is there any comment or thing that we should change? I think that master
history can not be changed anymore, but for everything else it is still
time to change before the development resumes that normal speed.
Martin
Re: Proposed development branch: geoapi-4.0
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Le 20/06/2018 à 15:18, Bruno P. Kinoshita a écrit :
> (…) having the tags in SVN only, as well as the new tags in git is OK
> for me.
>
I rebased the last 3 tags (0.6, 0.7, 0.8). Rebasing older tags would
have been more work, so I deleted them and would rather put a note
somewhere referring to SVN history. Anyway, I'm tempted to delete all
"pre-migration" tags after 1.0 release since I'm not 100% sure that they
are correct (only the SVN tags are sure).
Removing old references has apparently reduced git repository size by
about 20% compared to the size before this pruning effort.
Martin
Re: Proposed development branch: geoapi-4.0
Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br.INVALID>.
As I am learning Apache SIS for a project, and not really interested about older releases (maybe the current stable only?), having the tags in SVN only, as well as the new tags in git is OK for me.
Not sure about other users, but if developer/contributor bandwidth is restricted, perhaps just leave a note somewhere in the project docs pointing to the SVN tags, and/or put a ticket in JIRA maybe for some day?
CheersBruno
From: Martin Desruisseaux <ma...@geomatys.com>
To: dev@sis.apache.org
Sent: Wednesday, 20 June 2018 9:38 PM
Subject: Re: Proposed development branch: geoapi-4.0
Le 19/06/2018 à 22:22, Bruno P. Kinoshita a écrit :
> And I'm OK wih the removal of other branches. My real interest is on
> the development version, and tags only.
>
Branches removed from Git repository (still available on SVN). JDK9
branch has been re-created but is not for day-to-day development (until
all modularization issues have been resolved).
About the tags on Git: they are still referencing the old history. It
could be fixed, but this would require some work. Is it sufficient to
said that all tags prior SIS 1.0 should be fetched from SVN, or do we
need those tags on Git too?
Martin
Re: Proposed development branch: geoapi-4.0
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Le 19/06/2018 à 22:22, Bruno P. Kinoshita a écrit :
> And I'm OK wih the removal of other branches. My real interest is on
> the development version, and tags only.
>
Branches removed from Git repository (still available on SVN). JDK9
branch has been re-created but is not for day-to-day development (until
all modularization issues have been resolved).
About the tags on Git: they are still referencing the old history. It
could be fixed, but this would require some work. Is it sufficient to
said that all tags prior SIS 1.0 should be fetched from SVN, or do we
need those tags on Git too?
Martin
Re: Proposed development branch: geoapi-4.0
Posted by Martin Desruisseaux <ma...@geomatys.com>.
Le 19/06/2018 à 22:22, Bruno P. Kinoshita a écrit :
> And as I'm still learning by readind docs and code, will report/update
> docs that need to be updated.
>
Thanks! Speaking about reading documentation, there is two sources that
I found valuable:
For the model behind following packages:
* org.opengis.metadata
* org.apache.sis.metadata.iso
I recommend the NOAA wiki:
https://geo-ide.noaa.gov/wiki/index.php?title=Category:ISO_19115
I found it useful because the ISO standard just gives a succinct
description of each element. It is sometime hard to guess how we are
supposed to use them. The NOAA wiki explains in more details: the
purpose, best practice, etc.
For the model behind following packages:
* org.opengis.referencing
* org.apache.sis.referencing
I recommend OGC topic 2, "Spatial referencing by coordinates", in
particular annex B, "Context for modelling of spatial referencing by
coordinates" and annex C, "Geodetic concepts":
http://portal.opengeospatial.org/files/?artifact_id=39049
Those two annexes help to understand why Coordinate Reference System
classes are designed that way, why apparently simple solutions like
using WGS 84 as a universal pivot does not work, etc.
Regards,
Martin
Re: Proposed development branch: geoapi-4.0
Posted by "Bruno P. Kinoshita" <ki...@apache.org>.
+1 to geoapi-4.0
And I'm OK wih the removal of other branches. My real interest is on the development version, and tags only.
And as I'm still learning by readind docs and code, will report/update docs that need to be updated.
Thanks!Bruno
Sent from Yahoo Mail on Android
On Wed, 20 Jun 2018 at 5:07, Martin Desruisseaux<ma...@geomatys.com> wrote: Hello all
Following on the discussion about what could be the name of the
development branch (formerly "JDK8"), I propose "geoapi-4.0", for
consistency with another branch named "geoapi-3.1". More details on
those two branches are given there:
http://sis.staging.apache.org/branches.html
I'm tempted to delete the other branches since they are stalled and
should not be used for more development (in part because of the Git
history rewrite, but also because SIS has evolved since the last commit
on those branches). Those branches are still available on Subversion; if
their development restart, we would probably have to port the code to
latest commit on the development branch anyway.
Is there any comment or thing that we should change? I think that master
history can not be changed anymore, but for everything else it is still
time to change before the development resumes that normal speed.
Martin