Sorry to not attend to yesterday's IRC meeting.
Reading the discussion, one comment about trac :
01:38:20 heikki_: there are also 21 tickets seem to have no milestone
at all .. assign to 2.6.2 too ?
01:44:13 ticheler: teh 21 with no milestone need careful review
01:44:18 ticheler: many are outdated
We could create a milestone named something like "GeoNetwork future
release" for tickets which are accepted but nobody could take them
yet.
What do you think ?
Francois
Hi Francois,
Good idea! I will make such a milestone. Still the tickets need reviewing to kick out outdated ones. Also, what to do with defects? Those should go to a next milestone unless we decide we won't fix them. Maybe they even became invalid due to some other development.
Cheers,
Jeroen
On 10 nov 2010, at 08:59, Francois Prunayre wrote:
Sorry to not attend to yesterday's IRC meeting.
Reading the discussion, one comment about trac :
01:38:20 heikki_: there are also 21 tickets seem to have no milestone
at all .. assign to 2.6.2 too ?
01:44:13 ticheler: teh 21 with no milestone need careful review
01:44:18 ticheler: many are outdatedWe could create a milestone named something like "GeoNetwork future
release" for tickets which are accepted but nobody could take them
yet.What do you think ?
Francois
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
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
2010/11/10 Jeroen Ticheler <jeroen.ticheler@anonymised.com>:
Hi Francois,
Good idea! I will make such a milestone. Still the tickets need reviewing to kick out outdated ones. Also, what to do with defects? Those should go to a next milestone unless we decide we won't fix them. Maybe they even became invalid due to some other development.
They should go to next milestone at every realse until they're fixed
or obsolete due to new development as far as we accept them ?
Francois
Cheers,
JeroenOn 10 nov 2010, at 08:59, Francois Prunayre wrote:
Sorry to not attend to yesterday's IRC meeting.
Reading the discussion, one comment about trac :
01:38:20 heikki_: there are also 21 tickets seem to have no milestone
at all .. assign to 2.6.2 too ?
01:44:13 ticheler: teh 21 with no milestone need careful review
01:44:18 ticheler: many are outdatedWe could create a milestone named something like "GeoNetwork future
release" for tickets which are accepted but nobody could take them
yet.What do you think ?
Francois
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
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