After the meeting Andrea, Adrian and Simone said: (22:01:34) *aaime:* Sorry, what is the issue about the javadocs? (22:02:52) *acuster:* there are two (22:03:20) *acuster:* one for 2.2.0 is to make sure that the Geotools javadocs point into GeoAPI 2.0 and not 2.1 (which was the case in the last RC) (22:03:56) *acuster:* another for future Gt releases, to possibly have a trimed version of GeoAPI containing the modules we use and not those we don't. (22:04:21) *acuster:* simboss, you around? (22:04:30) *aaime:* A trimmed down version of Geoapi is a bit unlikely for a simple reason (22:04:34) *simboss:* yeah (22:04:40) *aaime:* We want to have released geotools against released geoapi (22:04:43) *acuster:* your question about a timeline for 2.3 was good (22:04:55) *aaime:* Geoapi release can be done only with opengis consensus (22:05:02) *simboss:* did you have any doubts? :P (22:05:10) *acuster:* I'd encourage you to propose one for next week and see if we can't get 2.3 out by early september (22:05:13) *aaime:* So I highly doubt there will be a special release for geotools (22:05:30) *acuster:* well, there was talk of cutting a special release for trunk (22:05:32) *aaime:* Adrian, geoapi is an issue even for 2.3 (22:05:57) *aaime:* Because now trunk is depending on some damned geoapi binary snapshot that we don't even have the sources for (22:06:03) *acuster:* if you are cutting a "Geotools snapshot" then you can tweak that, right? (22:06:28) *acuster:* yes, i was trying to profit from that unfortunate situation (22:06:38) *aaime:* Yes... oh well, I think we could cut something from an official release (22:06:51) *aaime:* So that if anybody needs to works against geoapi full can simply swap jars (22:06:54) *acuster:* after having lost several afternoons lost reading an interface that was totally irrlevant (22:07:09) *aaime:* Having different snapshots can be a real bitch otherwise (22:07:18) *aaime:* See our recent experiece with Geoapi (22:07:56) *acuster:* apparently Geotools needs to get its act in gear in a big way (22:07:59) *aaime:* Adrian, I do simpathize. Yet, in my opinion the process is: (22:08:01) *aaime:* 1) have an identifiable and stable release of Geoapi (22:08:09) *aaime:* 2) cut at your leisure (22:08:32) *aaime:* Yes Adrian, there is a lot of confusion to be cleared up (22:08:38) *acuster:* 2.2.0 is going out against geoapi 2.0 (22:08:42) *aaime:* Thank you for pushing us the right way (22:08:47) *acuster:* we know what we use, we know what we don't (22:08:57) *acuster:* for 2.2.0 we are *not* going to mess with things (22:08:59) *aaime:* Yes, so I do believe we have a cut against 2.0 (22:09:16) *acuster:* but I don't see why the situation would be different for any other Geotools release (22:09:29) ****acuster* is *not* talking about trunk (22:09:34) *aaime:* You were speaking about releasing 2.3 (22:09:46) *aaime:* but we don't have a stable reference geoapi to work against (22:09:51) *aaime:* Sorry, I mixed two concerns (22:09:53) *acuster:* so when it becomes time to release, we enter freeze mode (22:10:11) *aaime:* Adrian, geoapi is under the control of a different PMC (22:10:18) *acuster:* yes, absolutely (22:10:23) *aaime:* We can't decide when they have to release (22:10:26) *aaime:* Althought we can push (22:10:29) *acuster:* right (22:10:52) *aaime:* This in my opinion is a problem that won't let us release 2.3 soon, that's all (22:11:16) *acuster:* why can't geoapi release once a month? (22:11:21) *aaime:* Geoapi trunk at the moment is in a state of flux (22:11:27) *acuster:* ah (22:11:31) *aaime:* 4 drivers for change working togheter (22:11:49) *aaime:* 4 different "push" to move geoapi forward on different aspects (22:11:59) *aaime:* The result is a highly instable mix (22:12:32) *aaime:* Jody and Justin may have both the will and power to put that to an halt, create a branch and push a release from that (22:12:34) *acuster:* simboss, you ought to figure out what you are going to need for 2.3 (22:12:51) *acuster:* and see if we can't grab what you need (22:12:51) *aaime:* But I don't see this as something that will be happening soon (22:13:17) *aaime:* Anyway, let's post this part of the discussion on the mailing list and see what Jody and Justin have to say
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
