I was just updating the schedule, based on what I remembered of the
discussion. This is why it is in the meeting notes so we can sort this out.
So if we go the other way are we looking at a November release?
On Wed, Jun 15, 2016 at 12:16 PM Simone Giannecchini <
simone.giannecch...@geo-solutions.it> wrote:
> Hi All,
> one thing strikes me here:
> "We are looking at a short release cycle due to release delays of 2.9."
>
> Looking as in "yeah, that would be a bad idea"? :)
>
> What is the rationale behind making the life of 2.9 shorter? Its birth
> was difficult hence I would expect extra care before moving to 2.10.
> The clients I talk to do not usually rush towards new releases so
> making a release shorter does not help with building more confidence,
> I am afraid.
>
>
>
> Regards,
> Simone Giannecchini
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> ==
> Ing. Simone Giannecchini
> @simogeo
> Founder/Director
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 333 8128928
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate.
> Il loro utilizzo è consentito esclusivamente al destinatario del
> messaggio, per le finalità indicate nel messaggio stesso. Qualora
> riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
> cortesemente di darcene notizia via e-mail e di procedere alla
> distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
> Conservare il messaggio stesso, divulgarlo anche in parte,
> distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
> diverse, costituisce comportamento contrario ai principi dettati dal
> D.Lgs. 196/2003.
>
> The information in this message and/or attachments, is intended solely
> for the attention and use of the named addressee(s) and may be
> confidential or proprietary in nature or covered by the provisions of
> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
> Data Protection Code).Any use not in accord with its purpose, any
> disclosure, reproduction, copying, distribution, or either
> dissemination, either whole or partial, is strictly forbidden except
> previous formal approval of the named addressee(s). If you are not the
> intended recipient, please contact immediately the sender by
> telephone, fax or e-mail and delete the information in this message
> that has been received in error. The sender does not give any warranty
> or accept liability as the content, accuracy or completeness of sent
> messages and accepts no responsibility for changes made after they
> were sent or for other risks which arise as a result of e-mail
> transmission, viruses, etc.
>
>
> On Tue, Jun 14, 2016 at 10:47 PM, Ben Caradoc-Davies <b...@transient.nz>
> wrote:
> > GeoTools / GeoServer Meeting 2016-06-14
> > =======================================
> >
> > Attending
> > ---------
> >
> > Ben Caradoc-Davies
> > Jody Garnett
> > Torben Barsballe
> >
> > Apologies
> > ---------
> >
> > Ian Turton
> >
> > Agenda
> > ------
> >
> > - GeoServer OSGeo Project Officer
> > - Release schedule
> > - OSGeo update
> > - Upgrade to NetCDF-Java 4.6.6
> > - ImageMosaic refactoring part 1
> > - Pull requests
> >
> > Actions
> > -------
> >
> > - Jody: encourage updates to docs/jira to record Simone as GeoServer
> > project officer
> > - Alessandro and Andrea: release 14.4 / 2.8.4
> >
> > Actions from last meeting
> > -------------------------
> >
> > - Ben to email list to ask for more PMC votes on OSGeo copyright header
> > legal advice [DONE]
> > - Jody: Contact Justin to declare GeoTools copyright header policy
> > change done, merge in change to developers guide [DONE]
> >
> > GeoServer OSGeo Project Officer
> > -------------------------------
> >
> > Simone Giannecchini has volunteered:
> > - OSGeo board updated
> > - website:
> > http://www.osgeo.org/content/foundation/board_and_officers.html (done)
> > - wiki: https://wiki.osgeo.org/wiki/Contacts (done)
> > - jira: https://osgeo-org.atlassian.net/projects/GEOS (not yet)
> >
> > Release schedule
> > ----------------
> >
> > Updated the release schedule:
> > https://github.com/geoserver/geoserver/wiki/Release-Schedule
> >
> > We are looking at a short release cycle due to release delays of 2.9.
> >
> > - Alessandro and Andrea have (been) volunteered to release 14.4 / 2.8.4
> >
> > Release priorities/ideas/mad plans for GeoServer 2.10 release timeframe:
> > - Jody and Devon are taking a run at GeoTools codebase prior to foss4g
> > workshop in August. Intend to update library for Java 8 syntax.
> > - Status endpoint is collecting more and more sanity checks (expect GUI
> > during 2.10.x timeframe?)
> https://osgeo-org.atlassian.net/browse/GEOS-4585
> > https://osgeo-org.atlassian.net/browse/GEOS-7567
> > - ImageMosaic api refactor ongoing
> > - VectorTiles documentation
> >
> > OSGeo update
> > ------------
> >
> > Board has been informed of new GeoServer project officer.
> >
> > Board approved asking for legal advice on GeoTools header policy.
> > Ben/Jody are working with Michael Smith on this one....
> >
> > OSGeo Marketing committee has asked how they can help:
> > - GeoTools: Encourage committers, always encourage committers
> > - GeoServer: Encourage participation, testing, updated handouts?
> >
> > General discussion on where we get new developers? From
> > companies/organizations, submitting a few pull requests, ...
> >
> > How can we be more sticky as a community? Our "community" modules is one
> > attempt on this front, not so useful now with github.
> >
> > Our pull reviews can be ... harsh "no discussion, no jira, no party"
> > (but more directed at longstanding developers cutting corners). We do a
> > better job meeting new developers half way, but time is limited. Can be
> > intimidating to find a good test case example to copy from; perhaps we
> > can make a short list.
> >
> > Predictable release tick/tock between stable/maintenance helps attract
> > contributions (if not volunteers). As does our open process.
> >
> > Larger proposals get stuck in review, try many small proposals.
> >
> > Upgrade to NetCDF-Java 4.6.6
> > ----------------------------
> >
> > Targeting 2.9.x backport for July 2.9.1 release.
> >
> > [GEOT-5434] Upgrade to NetCDF-Java 4.6.6
> > https://osgeo-org.atlassian.net/browse/GEOT-5434
> >
> > ImageMosaic refactoring part 1
> > ------------------------------
> >
> >
> https://github.com/geotools/geotools/wiki/Refactor-ImageMosaic-Index-and-Catalog-management-for-improved-extensibility
> >
> > Should add Ben's summary to the docs: proposal provides why, pull
> > request provides what.
> >
> > Notes:
> > - This is a smaller proposal easier to follow
> > - The last section has gone beyond strict API interface change and has a
> > fair bit of discussion (is this needed?)
> > - Needs links to Jira and mailing list discussions
> >
> > Pull requests Roundup
> > ---------------------
> >
> > - Many pull requests were reviewed, and some merged
> >
> >
> > --
> > Ben Caradoc-Davies <b...@transient.nz>
> > Director
> > Transient Software Limited <http://transient.nz/>
> > New Zealand
> >
> >
> ------------------------------------------------------------------------------
> > What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> > patterns at an interface-level. Reveals which users, apps, and protocols
> are
> > consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> > J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> > reports.
> http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
> > _______________________________________________
> > GeoTools-Devel mailing list
> > GeoTools-Devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.
> http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
> _______________________________________________
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
--
--
Jody Garnett
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
