[GeoNetwork-devel] release 2.10.1 next week

Hi all, we've been discussing with some of you of making a 2.10.1
minor release next week.
This release will include quite a number of fix [1]. One major issue
which should be fixed is the user log off when exception occurs.

If you've any other fix to apply, let us know.

Cheers.

Francois

[1] https://github.com/geonetwork/core-geonetwork/issues?milestone=7&page=1&state=closed

Hi,

I would like to know if there is a policy when creating a new issue : what milestone should we generally assign the issue to ?

···

On Wed, Jul 17, 2013 at 8:10 AM, Francois Prunayre <fx.prunayre@anonymised.com.> wrote:

Hi all, we’ve been discussing with some of you of making a 2.10.1
minor release next week.
This release will include quite a number of fix [1]. One major issue
which should be fixed is the user log off when exception occurs.

If you’ve any other fix to apply, let us know.

Cheers.

Francois

[1] https://github.com/geonetwork/core-geonetwork/issues?milestone=7&page=1&state=closed


See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk


GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork


Florent Gravin
Camptocamp - Chambéry
0479444492

Hello Florent,

2013/7/17 Florent Gravin <florent.gravin@anonymised.com>:

Hi,

I would like to know if there is a policy when creating a new issue : what
milestone should we generally assign the issue to ?

I would say:

1) if the issue is a bug or minor feature in a specific release (eg.
2.10.0), set milestone to the next minor (eg. 2.10.1, if on develop
set 2.11.0)
2) if the issue is a major feature and you know that it could be done
for next major release, set milestone to the next major (eg. 2.11.0)
3) if the issue is a major feature and no funding/time available, set
milestone to future release
4) if you don't know, set no milestone

Cheers.

Francois

On Wed, Jul 17, 2013 at 8:10 AM, Francois Prunayre <fx.prunayre@anonymised.com>
wrote:

Hi all, we've been discussing with some of you of making a 2.10.1
minor release next week.
This release will include quite a number of fix [1]. One major issue
which should be fixed is the user log off when exception occurs.

If you've any other fix to apply, let us know.

Cheers.

Francois

[1]
https://github.com/geonetwork/core-geonetwork/issues?milestone=7&page=1&state=closed

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!

http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

--
Florent Gravin
Camptocamp - Chambéry
0479444492