Hi,
this week we had a bit of reports about regressions and memory leaks
so I'm not too comfortable releasing 1.6.0 without fixing them.
Here is the list of things I'd like to see fixed (of course, it's
wide open to discussion):
http://jira.codehaus.org/browse/GEOS-1643
http://jira.codehaus.org/browse/GEOS-1656
http://jira.codehaus.org/browse/GEOS-1657 (*)
http://jira.codehaus.org/browse/GEOS-1667 (regression)
http://jira.codehaus.org/browse/GEOS-1668
http://jira.codehaus.org/browse/GEOS-1669 (*)
http://jira.codehaus.org/browse/GEOS-1663 (*)
http://jira.codehaus.org/browse/GEOS-1654 (*)
(*) means I'm not too sure about this one, maybe we should just
leave it to 1.6.1... but it's annoying 
What others developer are thinking about it?
Oh, we should also decide which documentation issues we'll handle
by 1.6.0... now there are too many.
Another thing is the gt2 2.4.0 release, which we'll delay
for another week at least.
Opinions?
Cheers
Andrea
Hi Andrea,
I had the same concerns last week and indeed was going to try and
summarize the status of the issues... but you have already done that
nicely!! :).
I too don't think we should release 1.6.0 official with these types of
problems. Perhaps we should try to prioritize them as critical (which i
think you have already done) and push the rest off if they are not too
major.
Andrea Aime wrote:
Hi,
this week we had a bit of reports about regressions and memory leaks
so I'm not too comfortable releasing 1.6.0 without fixing them.
Here is the list of things I'd like to see fixed (of course, it's
wide open to discussion):
http://jira.codehaus.org/browse/GEOS-1643
http://jira.codehaus.org/browse/GEOS-1656
http://jira.codehaus.org/browse/GEOS-1657 (*)
http://jira.codehaus.org/browse/GEOS-1667 (regression)
http://jira.codehaus.org/browse/GEOS-1668
http://jira.codehaus.org/browse/GEOS-1669 (*)
http://jira.codehaus.org/browse/GEOS-1663 (*)
http://jira.codehaus.org/browse/GEOS-1654 (*)
(*) means I'm not too sure about this one, maybe we should just
leave it to 1.6.1... but it's annoying
What others developer are thinking about it?
Oh, we should also decide which documentation issues we'll handle
by 1.6.0... now there are too many.
Another thing is the gt2 2.4.0 release, which we'll delay
for another week at least.
Opinions?
Cheers
Andrea
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4007,478b92aa91367180515871!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira ha scritto:
Hi Andrea,
I had the same concerns last week and indeed was going to try and
summarize the status of the issues... but you have already done that
nicely!! :).
I too don't think we should release 1.6.0 official with these types of
problems. Perhaps we should try to prioritize them as critical (which i
think you have already done) and push the rest off if they are not too
major.
Hem, no, I still haven't prioritized them because I'm not too
sure about which issues people might want to have fixed by the next rc.
I have proposed my candidates, others might propose others, and we
may end up with too many issues to fix.
What are your pet peeves? What about the other developer ones?
To recap mines are:
http://jira.codehaus.org/browse/GEOS-1643
http://jira.codehaus.org/browse/GEOS-1656
http://jira.codehaus.org/browse/GEOS-1657 (*)
http://jira.codehaus.org/browse/GEOS-1667 (regression)
http://jira.codehaus.org/browse/GEOS-1668
http://jira.codehaus.org/browse/GEOS-1669 (*)
http://jira.codehaus.org/browse/GEOS-1663 (*)
http://jira.codehaus.org/browse/GEOS-1654 (*)
(*) means I'm not too sure about this one, maybe we should just
leave it to 1.6.1... but it's annoying
Cheers
Andrea
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi Andrea,
I had the same concerns last week and indeed was going to try and
summarize the status of the issues... but you have already done that
nicely!! :).
I too don't think we should release 1.6.0 official with these types of
problems. Perhaps we should try to prioritize them as critical (which i
think you have already done) and push the rest off if they are not too
major.
Hem, no, I still haven't prioritized them because I'm not too
sure about which issues people might want to have fixed by the next rc.
I have proposed my candidates, others might propose others, and we
may end up with too many issues to fix.
What are your pet peeves? What about the other developer ones?
To recap mines are:
http://jira.codehaus.org/browse/GEOS-1643
+1 on this. It's minor and shouldn't break anything else
http://jira.codehaus.org/browse/GEOS-1656
Hmmm... Yeah, that's pretty bad. +1
http://jira.codehaus.org/browse/GEOS-1657 (*)
-1, should wait to 1.6.1, imho
http://jira.codehaus.org/browse/GEOS-1667 (regression)
+0. If it's easy to fix +1. If it's a big pain then no.
http://jira.codehaus.org/browse/GEOS-1668
+1
http://jira.codehaus.org/browse/GEOS-1669 (*)
+0, if it's an easy fix then sure.
http://jira.codehaus.org/browse/GEOS-1663 (*)
+0, if it's easy and we have time.
http://jira.codehaus.org/browse/GEOS-1654 (*)
+1
We should update jira tomorrow in the meeting and dole out tasks. So others sound in if you have opinions.
Chris
(*) means I'm not too sure about this one, maybe we should just
leave it to 1.6.1... but it's annoying
Cheers
Andrea
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4005,478ba41a125691096210785!