[Geoserver-devel] IRC Logs Sep 25th

        brent_ has anyone read GSIP 5?
  brent_ http://docs.codehaus.org/display/GEOS/GSIP+5+-+Release+process
  AlFa yes
  sigq Title: GSIP 5 - Release process - GeoServer - Confluence (at docs.codehaus.org)
  brent_ I would like to get it in action by mid to end of october
  brent_ if anyone has any feedback or comments post them on the page or bring them up here
  brent_ I would like the release process to be realistic; something that we can actually do
  -->| cholmes (n=chatzill@anonymised.com) has joined GeoServer
  AlFa I agree with the proposal, even because I am almost ready for WCS release :slight_smile:
  brent_ cool
  AlFa after we have discussed this topic I would like to ask something about the WCS release
  brent_ I will continue updating the GSIP and keep the discussion going on email. Hopefully in a couple weeks we will have a good version of it ready to vote on
  cholmes I made some comments on it today.
  brent_ k
  cholmes The one other problem I have with it is that the default is to fall back on the PSC...
  cholmes Which is made of volunteers....
  cholmes And we've had problems with geotools psc making releases in a timely fashion.
  brent_ right
  brent_ suggestions for that?
  cholmes The unspoken solution is that a TOPP employee does it, since that's what happens now.
  brent_ k
  cholmes We might just make it a bit more explicit. You can try to find someone to volunteer for the release Brent, but it will fall back on you.
  AlFa agree ... the release process for both geotools and geoserver is really too long
  cholmes Maybe once we have enough volunteers that a TOPP default is not needed we can change the wording to have the PSC be the default.
  cholmes I might also say (and Jody will probably argue against me), that a tag in geotools is sufficient if it's taking too darn long to release.
  brent_ yeh it could be hard to rely on a geotools realease
  brent_ ok, I will make sure this gets discussed more on the email list and in the next couple meetings as we make progress
  brent_ AlFa, you have the floor
  AlFa you have just cleared my concerns
  brent_ cool
  AlFa i.e. if a Geoserver release has to be done against a Geotools release
  AlFa I would like to better define this topic and understand very well what are the conditions for a Geoserver release
  AlFa Geoserver could be release against a Geotools tag for example?
  -->| cholmes_ (n=chatzill@anonymised.com) has joined GeoServer
  AlFa released
  cholmes_ (sorry, I got dropped)
  brent_ yeh that is what chris brought up, and I think it is a good idea that a tag would be fine
  brent_ ok I think that is all for this topic, anything else people want to discuss?
  AlFa I would like to ask if someone has some more details on OracleDataStore status, I know that is a Geotools problem, but I noticed that many users would like to use it on Geoserver
  asantokhee any progress with multidimensional coverages
  AlFa about multidim coverages, on our side we have scheduled the final analysis starting from the next month
  asantokhee allright allessio
  AlFa we have some more detailed ideas on how to proceed, and I think the procces won't take much time
  asantokhee cool
  cholmes_ oracle's not in great shape.
  AlFa actually we are fully focused on release the 2D Geoserver
  cholmes_ I look at it every once in awhile.
  asantokhee no pb
  cholmes_ checked it out this morning.
  AlFa that will be done at the end of this week
  cholmes_ I may have a fix in. But jody was talking about rewriting it.
  cholmes_ so maybe it'll be better than
  AlFa about OracleDataStore, I have seen a Justin email about the module mantainer ... but not understand very well what is going on
  cholmes_ I haven't seen his email I don't think. But basically we don't have a real modular maintainer.
  AlFa I see
  cholmes_ There have been one or two people who volunteered, but they never had the time to do it right.
  cholmes_ It's now a hodgepodge of different code. The best thing may be to have someone rewrite it, so they know all the code, and can fix/maintain it.
  AlFa k
  brent_ ok if there is nothing else, I'm going to call the meeting over
  -->| appetkov (n=appetkov@anonymised.com) has joined GeoServer
  asantokhee hi alex
  appetkov hello adit
  AlFa Hi Alex :slight_smile:
  appetkov Hello Alessio!!
  AlFa I would like also ask if there are some discussions or progresses on the problem pointed out by Gabriel and Justin regarding the request object
  jdeolive the service dispatching stuff?
  AlFa yes
  jdeolive nothing yet, we still have the various alternatives
  jdeolive do you have an opinion to throw in? the more the better
  |<-- cholmes has left freenode (Read error: 110 (Connection timed out))
  AlFa I have not yet thing deeply on the problem, I have an idea ... first I would like to ask what you guys are thinking about
  jdeolive we havent decided on anything yet
  jdeolive the email sums up the tradeoffs pretty well
  AlFa I have understood that the problem is that the KVPRequestReader and XMLRequestReader produce the same request object
  jdeolive in a sense, but its a bit more about how to design services, wether of not services should depend on a "request" object, or just be plain of java beans
  AlFa and we would like to not have two classes doing almost the same thing, is it right?
  jdeolive that is part of it yes
  AlFa a ok
  jdeolive what was your idea?
  |<-- asantokhee has left freenode (Read error: 145 (Connection timed out))
  AlFa not a precise idea yet ... however I will propose one on the email discussion
  AlFa I have to test something before coming out with a proposal
  jdeolive ok sounds great, your input would be very welcome
  jdeolive cool
  jdeolive thanks
  jdeolive i have to run, but look forward to your email
  jdeolive ciao