There have been a number of recent improvements to Ingres’s Subversion repository and community issue tracking located at http://code.ingres.com and http://bugs.ingres.com respectively. The following changes were made:
- Common authentication back-end
- SSL for login
- Improved synchronization from Piccolo
Common authentication back-end
From the time the code for the Ingres DBMS server was published in Subversion, the authentication and authorization mechanism was distinct from that of the rest of the Ingres Community. This meant that those with commit access would need to maintain separate accounts. Alex Trofast and Andrew Ross have converted the authentication system for both http://code.ingres.com and http://bugs.ingres.com to use the same system for the wiki and forums.
SSL for login
Previously only the Community Forum and Wiki had SSL (https) logins, now the bugs and code site do as well. For the time being you can access them both in plain-text mode but at some point secure logins will be required. The updated URLs are – https://code.ingres.com and https://bugs.ingres.com. Note that for the time being the sites are signed using a self-signed certificate. This will change in due course but for the time being you may be required to acknowledge that the certificate has not been validated against any of the root Certificate Authorities.
Improved synchronization from Piccolo
Probably the most important out of the 3 changes is the improved sync up between Ingres’s internal source code system, Piccolo and the external Subversion server. Changes are now replicated out every 15 minutes from Piccolo, assuming there is something to propagate. The process for merging changes from Subversion into Piccolo is still being worked on. So now we have up to date Ingres code in the wild, so to speak.
Popularity: 7% [?]
