[jira] Created: (FOR-1068) plugins need to be managed via the ASF mirror system

View: New views
6 Messages — Rating Filter:   Alert me  

[jira] Created: (FOR-1068) plugins need to be managed via the ASF mirror system

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

plugins need to be managed via the ASF mirror system
----------------------------------------------------

                 Key: FOR-1068
                 URL: https://issues.apache.org/jira/browse/FOR-1068
             Project: Forrest
          Issue Type: Bug
          Components: Plugins (general issues), Project administration
            Reporter: David Crossley


Forrest Plugins need to be deployed and downloaded via the ASF mirror system. See http://www.apache.org/dev/mirrors.html

There are a number of reasons for this, e.g. being kind to the infrastructure; faster local access. However, the main reason is that this is where official PMC releases are required to be.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FOR-1068) plugins need to be managed via the ASF mirror system

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ https://issues.apache.org/jira/browse/FOR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565281#action_12565281 ]

David Crossley commented on FOR-1068:
-------------------------------------

One solution might be to use Apache Ant and Apache Ivy, coupled with the ASF mirror system. See http://www.apache.org/dev/mirrors.html

To start a demo, i followed the above doc to create a script which determines (using GeoIP) the nearest available mirrors for a particular client.
http://people.apache.org/~crossley/ivy-forrest-plugin/mirrors--xml.cgi
which generates an xml file. The first listed is the preferred mirror, then other available mirrors, then the two default mirrors.

Our Ant build could transform this to generate an Ivy "resolvers" file to list each mirrored artefact using a "url resolver". Ivy would then manage the plugin download and do the md5 checksum.

> plugins need to be managed via the ASF mirror system
> ----------------------------------------------------
>
>                 Key: FOR-1068
>                 URL: https://issues.apache.org/jira/browse/FOR-1068
>             Project: Forrest
>          Issue Type: Bug
>          Components: Plugins (general issues), Project administration
>            Reporter: David Crossley
>
> Forrest Plugins need to be deployed and downloaded via the ASF mirror system. See http://www.apache.org/dev/mirrors.html
> There are a number of reasons for this, e.g. being kind to the infrastructure; faster local access. However, the main reason is that this is where official PMC releases are required to be.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FOR-1068) plugins need to be managed via the ASF mirror system

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ https://issues.apache.org/jira/browse/FOR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565282#action_12565282 ]

David Crossley commented on FOR-1068:
-------------------------------------

The other aspect of this issue is to define a plugin release procedure for the Forrest PMC to follow. This would be needed before any plugin (even test ones) can be published via the mirrors.

> plugins need to be managed via the ASF mirror system
> ----------------------------------------------------
>
>                 Key: FOR-1068
>                 URL: https://issues.apache.org/jira/browse/FOR-1068
>             Project: Forrest
>          Issue Type: Bug
>          Components: Plugins (general issues), Project administration
>            Reporter: David Crossley
>
> Forrest Plugins need to be deployed and downloaded via the ASF mirror system. See http://www.apache.org/dev/mirrors.html
> There are a number of reasons for this, e.g. being kind to the infrastructure; faster local access. However, the main reason is that this is where official PMC releases are required to be.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FOR-1068) plugins need to be managed via the ASF mirror system

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ https://issues.apache.org/jira/browse/FOR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634545#action_12634545 ]

David Crossley commented on FOR-1068:
-------------------------------------

Some notes from the archives (of course there might be more) ...

Re: clean up the plugins
http://markmail.org/message/o7v5ptu6ycmgox3d
2005-04-05

Re: Releasing plugins
http://markmail.org/message/ck3ykgj6kkztgb66
2005-12-21

Re: Managing plugin releases
http://markmail.org/message/jubpqrc47vt3kfg4
2006-07-26

Re: content of release [was: Re: review list of scheduled issues for 0.8 release]
http://markmail.org/message/y43ykeo3hopi4bq3
2006-11-23


> plugins need to be managed via the ASF mirror system
> ----------------------------------------------------
>
>                 Key: FOR-1068
>                 URL: https://issues.apache.org/jira/browse/FOR-1068
>             Project: Forrest
>          Issue Type: Bug
>          Components: Plugins (general issues), Project administration
>            Reporter: David Crossley
>
> Forrest Plugins need to be deployed and downloaded via the ASF mirror system. See http://www.apache.org/dev/mirrors.html
> There are a number of reasons for this, e.g. being kind to the infrastructure; faster local access. However, the main reason is that this is where official PMC releases are required to be.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FOR-1068) plugins need to be managed via the ASF mirror system

by JIRA jira@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


    [ https://issues.apache.org/jira/browse/FOR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634547#action_12634547 ]

David Crossley commented on FOR-1068:
-------------------------------------

I have made some local progress on this issue. I have a demonstration Ant build that finds the nearest mirror (list of preferred mirrors) try each until it gets the artefact, then get its signature and checksum from the main dist area.

> plugins need to be managed via the ASF mirror system
> ----------------------------------------------------
>
>                 Key: FOR-1068
>                 URL: https://issues.apache.org/jira/browse/FOR-1068
>             Project: Forrest
>          Issue Type: Bug
>          Components: Plugins (general issues), Project administration
>            Reporter: David Crossley
>
> Forrest Plugins need to be deployed and downloaded via the ASF mirror system. See http://www.apache.org/dev/mirrors.html
> There are a number of reasons for this, e.g. being kind to the infrastructure; faster local access. However, the main reason is that this is where official PMC releases are required to be.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Commented: (FOR-1068) plugins need to be managed via the ASF mirror system

by rgardler :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

David Crossley (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/FOR-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634547#action_12634547 ]
>
> David Crossley commented on FOR-1068:
> -------------------------------------
>
> I have made some local progress on this issue. I have a demonstration Ant build that finds the nearest mirror (list of preferred mirrors) try each until it gets the artefact, then get its signature and checksum from the main dist area.

Kudos to David!

Ross
LightInTheBox - Buy quality products at wholesale price!