Re: Module retirement
jena-fuseki1 and jena-csv code retired. You can delete the target/ directoru in each area after the git pull to free on that disk space. Andy On 13/12/2018 11:50, Andy Seaborne wrote: We can send a message to users@ to alert them to the upcoming changes. spatial is still in discussion. SDB and jena-maven-tools (move command line schemagen to jena-cmds) are also potential retirements, but not in the 3.10.0 timeframe. Are there any other modules to put on the list to attract attention? This isn't a definite "will be retired"; it is a "the project is looking at the status of". I think we should throw the net quite widely - we need feedback and interest and indeed contributions for modules to be worth the effort. Draft message coming up. Detailed process: First step - remove jena-fuseki1 and jena-csv from build; see PR#508. Then delete the code before 3.10, leaving just the directory and a README saying "Gone!" and say you can pull from git history. These stubs can exist for 3.10.0 release and sometime we can delete the module stubs entirely. Sound good? Andy On 29/11/2018 17:08, ajs6f wrote: Sorry for the noise, but I just realized that I said the opposite of what I meant to! My only concern is that we should do it before people have a chance to fork should have read, My only concern is that we should do it AFTER people have a chance to fork ajs6f On Nov 29, 2018, at 11:48 AM, ajs6f wrote: I'd prefer (2). It's clean and it _uses_ VC instead of working around it. My only concern is that we should do it before people have a chance to fork, because they'll want to do that as late as possible. But we can ameliorate that by just making a couple of loud announcements first. We might want also to make a point of pointing at replacements, even if they seem obvious to us. ajs6f On Nov 29, 2018, at 11:45 AM, Andy Seaborne wrote: Let's retire some modules: jena-spatial [+] jena-fuseki1 jena-csv by not including them in the next release; they should all work but there isn't a way to signal "deprecation" other than by talking about it (which we've done) and doing it. There are several ways to go about this. 1/ have an area "archived/" with the modules moved there. This leaves them in the source-release and browsable in git. 2/ Delete from git. Maybe leave a file somewhere to record the commit ids. 3/ A new separate git-repo for "jena-misc" https://git-wip-us.apache.org/repos/asf/jena-misc.asf (or use gitbox and put it on github mirroed back to ASF.) and maybe some others. I think (1) is not definite enough. Thoughts/suggestions/... Andy [+] jena-spatial :: this is in jena-fuseki-webapp [INFO] +- org.apache.jena:jena-spatial:jar:3.10.0-SNAPSHOT:compile [INFO] | +- org.apache.lucene:lucene-spatial:jar:7.4.0:compile [INFO] | +- org.apache.lucene:lucene-spatial-extras:jar:7.4.0:compile [INFO] | | +- org.apache.lucene:lucene-spatial3d:jar:7.4.0:compile [INFO] | | \- io.sgr:s2-geometry-library-java:jar:1.0.0:compile [INFO] | \- org.locationtech.spatial4j:spatial4j:jar:0.6:compile
Re: Module retirement
We can send a message to users@ to alert them to the upcoming changes. spatial is still in discussion. SDB and jena-maven-tools (move command line schemagen to jena-cmds) are also potential retirements, but not in the 3.10.0 timeframe. Are there any other modules to put on the list to attract attention? This isn't a definite "will be retired"; it is a "the project is looking at the status of". I think we should throw the net quite widely - we need feedback and interest and indeed contributions for modules to be worth the effort. Draft message coming up. Detailed process: First step - remove jena-fuseki1 and jena-csv from build; see PR#508. Then delete the code before 3.10, leaving just the directory and a README saying "Gone!" and say you can pull from git history. These stubs can exist for 3.10.0 release and sometime we can delete the module stubs entirely. Sound good? Andy On 29/11/2018 17:08, ajs6f wrote: Sorry for the noise, but I just realized that I said the opposite of what I meant to! My only concern is that we should do it before people have a chance to fork should have read, My only concern is that we should do it AFTER people have a chance to fork ajs6f On Nov 29, 2018, at 11:48 AM, ajs6f wrote: I'd prefer (2). It's clean and it _uses_ VC instead of working around it. My only concern is that we should do it before people have a chance to fork, because they'll want to do that as late as possible. But we can ameliorate that by just making a couple of loud announcements first. We might want also to make a point of pointing at replacements, even if they seem obvious to us. ajs6f On Nov 29, 2018, at 11:45 AM, Andy Seaborne wrote: Let's retire some modules: jena-spatial [+] jena-fuseki1 jena-csv by not including them in the next release; they should all work but there isn't a way to signal "deprecation" other than by talking about it (which we've done) and doing it. There are several ways to go about this. 1/ have an area "archived/" with the modules moved there. This leaves them in the source-release and browsable in git. 2/ Delete from git. Maybe leave a file somewhere to record the commit ids. 3/ A new separate git-repo for "jena-misc" https://git-wip-us.apache.org/repos/asf/jena-misc.asf (or use gitbox and put it on github mirroed back to ASF.) and maybe some others. I think (1) is not definite enough. Thoughts/suggestions/... Andy [+] jena-spatial :: this is in jena-fuseki-webapp [INFO] +- org.apache.jena:jena-spatial:jar:3.10.0-SNAPSHOT:compile [INFO] | +- org.apache.lucene:lucene-spatial:jar:7.4.0:compile [INFO] | +- org.apache.lucene:lucene-spatial-extras:jar:7.4.0:compile [INFO] | | +- org.apache.lucene:lucene-spatial3d:jar:7.4.0:compile [INFO] | | \- io.sgr:s2-geometry-library-java:jar:1.0.0:compile [INFO] | \- org.locationtech.spatial4j:spatial4j:jar:0.6:compile
Re: Module retirement
Sorry for the noise, but I just realized that I said the opposite of what I meant to! >> My only concern is that we should do it before people have a chance to fork should have read, > My only concern is that we should do it AFTER people have a chance to fork ajs6f > On Nov 29, 2018, at 11:48 AM, ajs6f wrote: > > I'd prefer (2). It's clean and it _uses_ VC instead of working around it. > > My only concern is that we should do it before people have a chance to fork, > because they'll want to do that as late as possible. But we can ameliorate > that by just making a couple of loud announcements first. We might want also > to make a point of pointing at replacements, even if they seem obvious to us. > > ajs6f > >> On Nov 29, 2018, at 11:45 AM, Andy Seaborne wrote: >> >> Let's retire some modules: >> >> jena-spatial [+] >> jena-fuseki1 >> jena-csv >> >> by not including them in the next release; they should all work but there >> isn't a way to signal "deprecation" other than by talking about it (which >> we've done) and doing it. >> >> There are several ways to go about this. >> >> 1/ have an area "archived/" with the modules moved there. >> This leaves them in the source-release and browsable in git. >> >> 2/ Delete from git. Maybe leave a file somewhere to record the commit ids. >> >> 3/ A new separate git-repo for "jena-misc" >> https://git-wip-us.apache.org/repos/asf/jena-misc.asf >> (or use gitbox and put it on github mirroed back to ASF.) >> >> and maybe some others. >> >> I think (1) is not definite enough. >> >> Thoughts/suggestions/... >> >> Andy >> >> [+] >> jena-spatial :: this is in jena-fuseki-webapp >> [INFO] +- org.apache.jena:jena-spatial:jar:3.10.0-SNAPSHOT:compile >> [INFO] | +- org.apache.lucene:lucene-spatial:jar:7.4.0:compile >> [INFO] | +- org.apache.lucene:lucene-spatial-extras:jar:7.4.0:compile >> [INFO] | | +- org.apache.lucene:lucene-spatial3d:jar:7.4.0:compile >> [INFO] | | \- io.sgr:s2-geometry-library-java:jar:1.0.0:compile >> [INFO] | \- org.locationtech.spatial4j:spatial4j:jar:0.6:compile >
Re: Module retirement
I'd prefer (2). It's clean and it _uses_ VC instead of working around it. My only concern is that we should do it before people have a chance to fork, because they'll want to do that as late as possible. But we can ameliorate that by just making a couple of loud announcements first. We might want also to make a point of pointing at replacements, even if they seem obvious to us. ajs6f > On Nov 29, 2018, at 11:45 AM, Andy Seaborne wrote: > > Let's retire some modules: > > jena-spatial [+] > jena-fuseki1 > jena-csv > > by not including them in the next release; they should all work but there > isn't a way to signal "deprecation" other than by talking about it (which > we've done) and doing it. > > There are several ways to go about this. > > 1/ have an area "archived/" with the modules moved there. > This leaves them in the source-release and browsable in git. > > 2/ Delete from git. Maybe leave a file somewhere to record the commit ids. > > 3/ A new separate git-repo for "jena-misc" > https://git-wip-us.apache.org/repos/asf/jena-misc.asf > (or use gitbox and put it on github mirroed back to ASF.) > > and maybe some others. > > I think (1) is not definite enough. > > Thoughts/suggestions/... > >Andy > > [+] > jena-spatial :: this is in jena-fuseki-webapp > [INFO] +- org.apache.jena:jena-spatial:jar:3.10.0-SNAPSHOT:compile > [INFO] | +- org.apache.lucene:lucene-spatial:jar:7.4.0:compile > [INFO] | +- org.apache.lucene:lucene-spatial-extras:jar:7.4.0:compile > [INFO] | | +- org.apache.lucene:lucene-spatial3d:jar:7.4.0:compile > [INFO] | | \- io.sgr:s2-geometry-library-java:jar:1.0.0:compile > [INFO] | \- org.locationtech.spatial4j:spatial4j:jar:0.6:compile
Module retirement
Let's retire some modules: jena-spatial [+] jena-fuseki1 jena-csv by not including them in the next release; they should all work but there isn't a way to signal "deprecation" other than by talking about it (which we've done) and doing it. There are several ways to go about this. 1/ have an area "archived/" with the modules moved there. This leaves them in the source-release and browsable in git. 2/ Delete from git. Maybe leave a file somewhere to record the commit ids. 3/ A new separate git-repo for "jena-misc" https://git-wip-us.apache.org/repos/asf/jena-misc.asf (or use gitbox and put it on github mirroed back to ASF.) and maybe some others. I think (1) is not definite enough. Thoughts/suggestions/... Andy [+] jena-spatial :: this is in jena-fuseki-webapp [INFO] +- org.apache.jena:jena-spatial:jar:3.10.0-SNAPSHOT:compile [INFO] | +- org.apache.lucene:lucene-spatial:jar:7.4.0:compile [INFO] | +- org.apache.lucene:lucene-spatial-extras:jar:7.4.0:compile [INFO] | | +- org.apache.lucene:lucene-spatial3d:jar:7.4.0:compile [INFO] | | \- io.sgr:s2-geometry-library-java:jar:1.0.0:compile [INFO] | \- org.locationtech.spatial4j:spatial4j:jar:0.6:compile
