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.
On Fri, Jan 28, 2011 at 2:59 AM, Andrea Aime
<[email protected]>wrote:
> On Thu, Jan 27, 2011 at 10:23 PM, Chris Holmes <[email protected]>
> 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:
>
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+GEOS+AND+fixVersion+%3D+%222.1-RC2%22+AND+status+in+%28Resolved%2C+Closed%29+ORDER+BY+due+ASC%2C+priority+DESC%2C+created+ASC
>
> (thinking about http://jira.codehaus.org/browse/GEOS-4329 and
> http://jira.codehaus.org/browse/GEOS-4306, we
> found later that the latter was also happening in other raster formats
> such as the GDAL based ones)
>
> I've also found another couple of regression in the direct raster path
> that I did not manage to report
> so far:
> http://jira.codehaus.org/browse/GEOS-4336
> http://jira.codehaus.org/browse/GEOS-4337
>
> 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
>
> phone: +39 0584962313
> fax: +39 0584962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -----------------------------------------------------
>
------------------------------------------------------------------------------
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
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
