deegree TMC Meeting (2012-10-30)
Attendees: TorstenFriebe, ReijerCopier, AndreasSchmitz, MarkusSchneider, JohannesWilden
1. Agenda
- Welcome and agenda review
- deegree community space actions
- Infrastructure/website issues
1.1. Define API and configuration compatibility process/guidelines / Version numbering schema used for deegree
Tracker issues: TMC tracker item #6393/TMC tracker item #6389
- It was decided to extend the discussion of the stability question at deegree community space.
A draft guideline has been created as a result of ticket TMC tracker item #6393.
- Discussion was initiated on the mailing list, but no feedback yet.
- There was some discussion in the meeting why the 3.x series doesn't have a stable API (evolving concepts).
- Some clarification seems to be required in order to define what "the API actually is".
- The issue of configuration migration paths between major versions was also brought up (there was none between 2.x and 3.0). How should this be treated between 3.x and 4.0?
1.2. Infrastructure/website issues
Tracker issues: deegree tracker item #450/deegree tracker item #457
- The wiki registration problems has been solved by re-enabling unsecured registration. Anti-spam mechanisms still need to be enabled (Captchas).
- The build server issues have not been solved yet. (this was fixed in the meantime).
- The Download page is missing the latest deegree-webservices version (3.2-pre11). (this was fixed in the meantime).
- The Documentation page is missing the latest 3.2 version (3.2-pre11). (this was fixed in the meantime).
It was noted that currently only lat/lon employees have the possibility to update the webpage and fix issues with the wiki and servers (build server, artifact server). JohannesWilden will be the responsible TMC person for the web page updates for now.
There was some technical discussion on means of automatically updating information on latest (pre) releases, deegree tracker item #461
1.3. Migrate issue tracker to JIRA
Tracker issue: TMC tracker item #6321
TMC is waiting for PSC's reaction on the latest comments on this issue.
1.4. Regular pre-release builds/quality assurance
Tracker issue: TMC tracker item #6294
- No updates. Maybe there will be a chance to discuss this at the community space.
1.5. Find a usable definition of "stable" for deegree modules
Tracker issue: TMC tracker item #6297
Postponed, as it depends on TMC tracker item #6298.
1.6. Prepare a suggestion for maintained components/modules
Tracker issue: TMC tracker item #6298
- No progress on getting the site running (for the autogenerated list of modules and their status), since the build server is down/broken.
1.7. Migrate source code to git, possibly using bitbucket
Tracker issue: TMC tracker item #6322
TMC is waiting for PSC's reaction on the latest comments on this issue.
1.8. Define actions for deegree 3.2 release/update the deegree 3 roadmap
Tracker issues: TMC tracker item #6391, TMC tracker item #6387
- The roadmap has been updated as far as this was possible.
- Discussion on the next steps has been started on the mailing list, but no feedback yet.
- It has been agreed to propose this as a discussion slot for the community space.
1.9. Propose process for dealing with feature requests in the deegree issue tracker
Tracker issue: TMC tracker item #1275
Implementing the proposed process depends on a final decision on switching the issue tracker.
- There was some discussion on implementing this process in Trac, but it seems to require a lot of effort.
- The tracker question should be discussed at the community space as well.