[GeoNetwork-devel] More re-targetting milstones

I believe the following needs to be done in order to cleanup the millstones
in Trac

- Reasign all the active v2.6.4 tickets to the v2.6.5 millstone (4 Tickets)
- close the v2.6.4 millstone as it is passed.
- Reasign all the active v2.8.0 RC0 tickets to the v2.8.0 RC1 or v2.8.0
millstone (4 Tickets)
- close the v2.8.0 RC0 millstone as it is passed.
- Reasign all the active v2.7.0 tickets to the v2.8.0 RC1 or v2.8.0 or
v2.9.0 millstone (54 Tickets)
- close the v2.7.0 millstone as it is passed.

Any objections with me doing this? (I cannot close the millstones - I will
need someone else to do this)

Also, is there a way to do this so that it does not send emails to the
newsgroups?

Thanks

--
View this message in context: http://osgeo-org.1560.n6.nabble.com/More-re-targetting-milstones-tp5004238.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

Hi Ian

Thanks for the ticket review, the plan sounds good to me. Related to this:

- Reasign all the active v2.7.0 tickets to the v2.8.0 RC1 or v2.8.0 or v2.9.0 millstone (54 Tickets)

Not sure about what is the best for this. I think should be fine to set milestone v2.8.0 RC1, except for enhancement issues (set to 2.9.0). What does others think about this?

About closing milestones, I checked and seem also not allowed to do this, can’t help on this.

Regards,
Jose García

On Tue, Sep 25, 2012 at 1:03 PM, ianwallen <ianwallen@anonymised.com> wrote:

I believe the following needs to be done in order to cleanup the millstones
in Trac

  • Reasign all the active v2.6.4 tickets to the v2.6.5 millstone (4 Tickets)
  • close the v2.6.4 millstone as it is passed.
  • Reasign all the active v2.8.0 RC0 tickets to the v2.8.0 RC1 or v2.8.0
    millstone (4 Tickets)
  • close the v2.8.0 RC0 millstone as it is passed.
  • Reasign all the active v2.7.0 tickets to the v2.8.0 RC1 or v2.8.0 or
    v2.9.0 millstone (54 Tickets)
  • close the v2.7.0 millstone as it is passed.

Any objections with me doing this? (I cannot close the millstones - I will
need someone else to do this)

Also, is there a way to do this so that it does not send emails to the
newsgroups?

Thanks


View this message in context: http://osgeo-org.1560.n6.nabble.com/More-re-targetting-milstones-tp5004238.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.


Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/


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


GeoCat Bridge for ArcGIS allows instant publishing of data and metadata on GeoServer and GeoNetwork. Visit http://geocat.net for details.


Jose García
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
http://GeoCat.net

Hi Ian and José

2012/9/25 Jose Garcia <jose.garcia@anonymised.com>:

Hi Ian

Thanks for the ticket review, the plan sounds good to me. Related to this:

I agree that it would be good to do some cleanup.

I've marked as completed 2.6.4, 2.8.0RC0 & RC1 and added a 2.8.0 RC2.

Cheers.

Francois

- Reasign all the active v2.7.0 tickets to the v2.8.0 RC1 or v2.8.0 or
v2.9.0 millstone (54 Tickets)
Not sure about what is the best for this. I think should be fine to set
milestone v2.8.0 RC1, except for enhancement issues (set to 2.9.0). What
does others think about this?
About closing milestones, I checked and seem also not allowed to do this,
can't help on this.

Regards,
Jose García

On Tue, Sep 25, 2012 at 1:03 PM, ianwallen <ianwallen@anonymised.com> wrote:

I believe the following needs to be done in order to cleanup the
millstones
in Trac

- Reasign all the active v2.6.4 tickets to the v2.6.5 millstone (4
Tickets)
- close the v2.6.4 millstone as it is passed.
- Reasign all the active v2.8.0 RC0 tickets to the v2.8.0 RC1 or v2.8.0
millstone (4 Tickets)
- close the v2.8.0 RC0 millstone as it is passed.
- Reasign all the active v2.7.0 tickets to the v2.8.0 RC1 or v2.8.0 or
v2.9.0 millstone (54 Tickets)
- close the v2.7.0 millstone as it is passed.

Any objections with me doing this? (I cannot close the millstones - I will
need someone else to do this)

Also, is there a way to do this so that it does not send emails to the
newsgroups?

Thanks

--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/More-re-targetting-milstones-tp5004238.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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

--
GeoCat Bridge for ArcGIS allows instant publishing of data and metadata on
GeoServer and GeoNetwork. Visit http://geocat.net for details.
_________________________
Jose García
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
http://GeoCat.net

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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

Francois,

Can you also close the 2.7 as well.

I will start moving the tickets later on today.

Since no options were given to avoid mail bombing the newsgroup when the
changes are done - I'm going to apologize in advance. Sorry : )

Thanks.

--
View this message in context: http://osgeo-org.1560.n6.nabble.com/More-re-targetting-milstones-tp5004238p5004330.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.