So how are we feeling about 2.1.0? RC1 has been out 1.5 weeks. Can we put together a schedule for 2.1.0? Do we need another RC? I haven’t been following the lists super closely, but I haven’t seen any blockers yet. But we’ve also had some smaller fixes I think. Do we put out another RC and make it a true candidate for release? Go for 2.1.0 if there’s nothing blocker in the next few days? I’m more than open for anything, just want to keep things moving. And it’d be good to not be in an RC nether-region.
Sounds like we are on track Chris; any feedback or problems on the user list to worry about?
Jody
On 28/01/2011, at 7:23 AM, Chris Holmes wrote:
So how are we feeling about 2.1.0? RC1 has been out 1.5 weeks. Can we put together a schedule for 2.1.0? Do we need another RC? I haven't been following the lists super closely, but I haven't seen any blockers yet. But we've also had some smaller fixes I think. Do we put out another RC and make it a true candidate for release? Go for 2.1.0 if there's nothing blocker in the next few days? I'm more than open for anything, just want to keep things moving. And it'd be good to not be in an RC nether-region.
I’m in both user and developer mailing list as most of the time check the codes while developing GIS solution in limited time period. Some of the features released in this GeoServer 2.1 series are key/important features for GIS solution i worked/i consider such as
The disk quota functionality with geowebcache which safeguard most of the deployment disk space management easily.
WMS 1.3 and fixes done on WMS rendering, additional fonts support…
SLD enhancement and more DPI support for Map generation.
I am really keen to looking forward to see GeoServer final release.
In meantime, another small consideration for you all. It is update oracle jdbc driver file which avoid manual patching work i do these days with release. Current oracle jdbc jar is ojdbc14.jar (which is Oracle 10.2.0.2.0 and JDK 1.4.2_08 version). As long as current Geo-Server requires Java 1.5 or latter version, better bundle with latest version of Oracle JDBC driver…ojdbc5.jar from Oracle 11g release 2.
Sounds like we are on track Chris; any feedback or problems on the user list to worry about?
Jody
On 28/01/2011, at 7:23 AM, Chris Holmes wrote:
So how are we feeling about 2.1.0? RC1 has been out 1.5 weeks. Can we put together a schedule for 2.1.0? Do we need another RC? I haven’t been following the lists super closely, but I haven’t seen any blockers yet. But we’ve also had some smaller fixes I think. Do we put out another RC and make it a true candidate for release? Go for 2.1.0 if there’s nothing blocker in the next few days? I’m more than open for anything, just want to keep things moving. And it’d be good to not be in an RC nether-region.
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d
On Thu, Jan 27, 2011 at 10:23 PM, Chris Holmes <cholmes@anonymised.com> wrote:
So how are we feeling about 2.1.0? RC1 has been out 1.5 weeks. Can we put
together a schedule for 2.1.0? Do we need another RC? I haven't been
following the lists super closely, but I haven't seen any blockers yet. But
we've also had some smaller fixes I think. Do we put out another RC and
make it a true candidate for release? Go for 2.1.0 if there's nothing
blocker in the next few days? I'm more than open for anything, just want to
keep things moving. And it'd be good to not be in an RC nether-region.
We definitely need another RC imho, as there has been quite a bit of changes
since last one and a couple them are important bug fixes:
Given our current situation we should probably try to build automatic
exclusions
that turn off the direct render path for those cases (unless someone
comes up with
a real fix real quick)
Cheers
Andrea
--
Ing. Andrea Aime
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
On Fri, Jan 28, 2011 at 8:59 AM, Andrea Aime
<andrea.aime@anonymised.com> wrote:
On Thu, Jan 27, 2011 at 10:23 PM, Chris Holmes <cholmes@anonymised.com> wrote:
So how are we feeling about 2.1.0? RC1 has been out 1.5 weeks. Can we put
together a schedule for 2.1.0? Do we need another RC? I haven't been
following the lists super closely, but I haven't seen any blockers yet. But
we've also had some smaller fixes I think. Do we put out another RC and
make it a true candidate for release? Go for 2.1.0 if there's nothing
blocker in the next few days? I'm more than open for anything, just want to
keep things moving. And it'd be good to not be in an RC nether-region.
We definitely need another RC imho, as there has been quite a bit of changes
since last one and a couple them are important bug fixes:
Sounds reasonable. I can check with our resourcing to figure out when we could put time in to a release, but if anyone else wants to step up sooner for RC2 that’d be awesome.
I think we should also all agree on what the policy is for the RC. Justin tried to raise this discussion last time but it fizzled by the time he put the release out. Ended up OK, but I don’t think we got clarity on what fixes could go in, and what criteria we’d use to call something a .0 release. I think whatever we come up with we should formalize as a policy for future releases.
So how are we feeling about 2.1.0? RC1 has been out 1.5 weeks. Can we put
together a schedule for 2.1.0? Do we need another RC? I haven’t been
following the lists super closely, but I haven’t seen any blockers yet. But
we’ve also had some smaller fixes I think. Do we put out another RC and
make it a true candidate for release? Go for 2.1.0 if there’s nothing
blocker in the next few days? I’m more than open for anything, just want to
keep things moving. And it’d be good to not be in an RC nether-region.
We definitely need another RC imho, as there has been quite a bit of changes
since last one and a couple them are important bug fixes:
Given our current situation we should probably try to build automatic
exclusions
that turn off the direct render path for those cases (unless someone
comes up with
a real fix real quick)
Cheers
Andrea
–
Ing. Andrea Aime
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy