Developer catchup: 3.0.3-SNAPSHOT, downloads and more

There has been a lot going on and the PRs are very active, but not very much chatter outside of PSC video chat.

Here is a bunch of updates all around build care and feeding :slight_smile:

versions and revisions

I just wanted to report back that 3.0.3-SNAPSHOT landed on the 3.0.x branch, and the the workflow should now be maven standard : 3.0.3-SNAPSHOT → 3.0.3 → 3.0.4-SNAPSHOT for the next release.

@groldan also had the suggestion that we look at Maven CI Friendly Versions so we do not have to update 300 some files each release… The idea the root pom.xml gets <version>${revision}</version>, combined with a flatten-maven-plugin addition. It is a bit magic, but should be simpler to maintain (revision is one of only three properties called out for special processing to be used for this purpose).

With that in mind I would like to propose the same maven versioning system for GeoTools and GeoWebCache :slight_smile:

Downloads?

@tbarsballe is there any update on download locations? Right now the release scripts above are still sending content to SF. Also not sure if they started deleting things or not…

The osgeo ticket is from last year so I am not sure what is going on :slight_smile:

As I understand it you have collected prior downloads, but the most recent releases were uploaded to SF (and should probably be backed up).

Module Status

An interesitng one here, introducing assembly check so that each plugin is verified that it includes module status entry:

ImageN 1.0 incoming

ImageN 0.9.3 went out .. all the way to maven central. I started talking with Eclipse Folks to remind myself what the formal release process looks like.

The 0.9.3 update addresses most of the battle experience testing, what is left is goals and comforts.

  • Modernize the code base with Vector, Generics and Concurrency
    Updated with a weather report on which of these ideas has any possibility of success. The big one of using List rather than Vecotr is a bust, as ParameterBlock from JDK is responsble for the use of Vector.

    However introducing generics can work well, especially for internal and private code.

  • ParameterBlockImageN type narrow landed in 0.9.3 nad is quite sucessful in making more reable code examples. I would like to make a PR to geotools to take advantage of this change.

Increasing test coverage to 60%:

JTS 1.21.0 incoming

After the success in ImageN releasing on maven central, I am working with Martin on an update for JTS. I expect this to land prior to the next release cycle - and be very stable because it is Martin (and retired Martin is even more stable).

Regarding the download locations:

  • The most recent applicable osgeo ticket is this one: https://trac.osgeo.org/osgeo/ticket/3543#comment:3
  • I haven’t yet gotten a clear answer to my question of whether we’re fine to go ahead and use downloads.osgeo.org for active releases and not just archive (as that was something that got tacked on later). I’ve been meaning to follow up on the lists this (and a few other items) since we haven’t had time to cover this in the PSC meetings in a bit, but haven’t quite gotten around to it. Given the ticket’s closed completed (as we did get the archive moved over), I figure we’ve got two options:
    • I could open a new ticket for just that question
    • Or, given the SAC is busy and everything is mostly self-serve anyways, we just go ahead and switch over on our own - we should have all the necessary accesses (only one I’m uncertain about is if the jenkins osgeo job has the right permissions to publish releases - I think it should, but this hasn’t been tested).
  • In either case, I still need to update the downloads site template + prior release pages (and we’ll need to test + upgrade the jenkins release scripts too), so for the current release I’d say stick to sourceforge.

Cheers,

Torben

The current releases are done, so the coast is clear if we wish to self-serve and make a PR updating the website to point to the new location.