Dear committers,
FYI, I’ll make the 2.10.x dev branch and 2.10.0RC0 release [1] this afternoon, so if you have any important pending commits, commit now !
Cheers.
Francois
[1] http://trac.osgeo.org/geonetwork/wiki/proposals/release2.10.0
Francois,
A little late now, but I would have liked to see the html5 UI code
(https://github.com/geonetwork/core-geonetwork/pull/81) committed into the
2.10Rc0 - oh well maybe this can be done in 2.10Rc1....
Good to see this is moving along as planned
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/2-10-x-dev-branch-tp5047853p5048372.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.
Francois,
I noticed that you updated trac with the new milestones. But I believe it
would be better if you deleted the 2.10.0 milestone and rename "v2.9.0" to
"V2.10.0". This way all the 2.9.0 tickets will automatically be moved to the
2.10 milestone which is where I think they belong.
The only issue with this approach is that the 2.9.0 is not renamed in the
history "http://trac.edgewall.org/ticket/4582"\.
What do other think - should rename it or move the tickets to the 2.10.0
release?
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/2-10-x-dev-branch-tp5047853p5048373.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.
Now that I think about it, I think it would be better to delete "v2.10.0
RC0" instead of "v2.10.0" and rename "2.9.0" to "v2.10.0 RC0" .
Have a good weekend.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/2-10-x-dev-branch-tp5047853p5048374.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.
Ian, I made the change - but still was not convinced of removing a milestone last week because there is probably some links to trac using 2.9.0.
Then I need to move all tickets to 2.11.0 or 2.10.RC1 manually … no option to update all tickets at a time.
Francois.
···
2013/4/20 ianwallen <ianwallen@anonymised.com.22…>
Now that I think about it, I think it would be better to delete “v2.10.0
RC0” instead of “v2.10.0” and rename “2.9.0” to “v2.10.0 RC0” .Have a good weekend.
–
View this message in context: http://osgeo-org.1560.x6.nabble.com/2-10-x-dev-branch-tp5047853p5048374.htmlSent from the GeoNetwork developer mailing list archive at Nabble.com.
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
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,
Looks good for now. I could move all the tickets - the problem is that when
I do, it mail bombs the developers mailing list.
Have you ever considered the following configuration.
- Create a special development account in trac. i.e. (geonetwork-devel)
- Update the preference for that user so that the email address for the user
is the newsgroup email address "geonetwork-devel@…"
- Update all the milestones to default this user instead of the email
address.
Then in the future if you need to perform an bulk change, you can edit the
user account (geonetwork-devel) preference and remove the email or sent it
temporary to something else. Perform the bulk changes. Then reset the email
address back to the original "geonetwork-devel@…". This would avoid mail
bombing the mailing list. It would still mail the users of the assigned
tickets and the cc users but I don't beleive there are many of these
tickets.
Of course the other option would be to edit the trac.ini and disable the
notifications while reassigning milestones.
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/2-10-x-dev-branch-tp5047853p5048791.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.
Ian, thanks for the suggestions
2013/4/22 ianwallen <ianwallen@anonymised.com>:
Francois,
Looks good for now. I could move all the tickets - the problem is that when
I do, it mail bombs the developers mailing list.Have you ever considered the following configuration.
- Create a special development account in trac. i.e. (geonetwork-devel)
- Update the preference for that user so that the email address for the user
is the newsgroup email address "geonetwork-devel@…"
- Update all the milestones to default this user instead of the email
address.
I'm not a trac expert, but I don't see how we could set up this new
account on geonetwork trac which only use osgeo ldap for users AFAIK.
Then in the future if you need to perform an bulk change, you can edit the
user account (geonetwork-devel) preference and remove the email or sent it
temporary to something else. Perform the bulk changes. Then reset the email
address back to the original "geonetwork-devel@…". This would avoid mail
bombing the mailing list. It would still mail the users of the assigned
tickets and the cc users but I don't beleive there are many of these
tickets.Of course the other option would be to edit the trac.ini and disable the
notifications while reassigning milestones.
And I'm not sure we could have access to trac.ini.
Francois
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/2-10-x-dev-branch-tp5047853p5048791.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
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
On Sat, Apr 20, 2013 at 1:06 AM, ianwallen <ianwallen@anonymised.com> wrote:
Francois,
A little late now, but I would have liked to see the html5 UI code
(https://github.com/geonetwork/core-geonetwork/pull/81) committed into the
2.10Rc0 - oh well maybe this can be done in 2.10Rc1....Good to see this is moving along as planned
Hi,
I have added some more documentation about UIs to help this new UI go forward:
https://github.com/geonetwork/core-doc-sources/pull/8
Is there anything else I can do to help this go on? What is still
pending so we can include it on some 2.10 version?