+1.
Thanks for bringing this up, Justin. Does the developer manual address
this matter?
I find commit messages with only the Jira key to be a lot less helpful
than they could be. Developers, please think of another developer
looking at a long log listing. Or a maintainer considering your pull
Sounds great Justin.
>From the 8.1 release:
- the readme for stable release linking off to the "latest" docs. While I think
I fixed this could you keep an eye out.
- We also had some upload to source forge troubles with the release scripts.
Tag me in if you need a hand.
--
Jody Garnett
On Tue
Frank War
Frank War
Hi folks,
I have been noticing a few commit messages go by with no comment except for
the jira number they are related. While this is efficient (less typing) it
is also cumbersome for someone reviewing, or analyzing history to have to
go back to jira to figure out what the context. At least a sent
Sebastian
Sebastian
Sebastian
Sebastian
Hi all,
As discussed in todays skype meeting the plan is to push out the final
geoserver 2.2 release this week. This means releasing GeoTools 8.2
in conjunction. Any objections to doing so in the next couple of days?
Thanks.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise
GeoServer/GeoTools meeting September 17 2012
Participants
--
Alessio Fabiani
Andrea Aime
Ben Caradoc-Davies
Jukka Rahkonen
Justin Deoliveria
Simone Giannecchini
Chris Holmes
Agenda
-
* 2.2.0 final
* CAS
* Test
Making good progress on the following and will have a pull request ready
shortly:
-
http://docs.codehaus.org/display/GEOTOOLS/Java+7+try-with-resource+compatibility
- http://docs.codehaus.org/display/GEOTOOLS/FeatureCollection+revolution
I can also push this up as a branch for downstream apps to
12 matches
Mail list logo