You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt T Stam (JIRA)" <ju...@ws.apache.org> on 2011/04/28 01:01:03 UTC
[jira] [Created] (JUDDI-470) Remove old released from dist
Remove old released from dist
-----------------------------
Key: JUDDI-470
URL: https://issues.apache.org/jira/browse/JUDDI-470
Project: jUDDI
Issue Type: Task
Reporter: Kurt T Stam
Assignee: Kurt T Stam
PMC members,
As the ASF grows in size, so does the total size of the distribution
artefacts we ask our mirror community to support for us. The larger this
total size, the greater the strain on both ASF infrastructure and on the
mirroring system.
As per the release guidelines [1], only current releases should be
available at http://www.apache.org/dist/. Monitoring of
http://www.apache.org/dist/ [2] shows that some projects are not
removing old releases. This is placing an unnecessary strain on both ASF
infrastructure and on our mirror volunteers.
Thanks to those PMCs that have been removing old releases from their
distribution directory. The infrastructure appreciates you keeping on
top of this.
PMCs that have not been removing old releases are required to review
their current distribution directory and remove any old releases.
- PMCs using svnpubsub should remove old releases via svn.
- PMCs not using svnpubsub should remove old releases directly from
/www/www.apache.org/dist/<tlp> on people.apache.org at. Note that any
deletions may take up to 24 hours to replicate to http://www.apache.org/dist
In both cases it may take longer for changes to replicate to mirrors.
Old releases removed from http://www.apache.org/dist/ are not lost.
Release are automatically copied to http://archive.apache.org/dist/ and
are never deleted.
This inevitably raises the question what is a current release and what
is an old release. To some extent, this varies from project to project
but typically it amounts to the following:
a) latest release of the current branch
b) latest stable release of the current branch
c) latest stable release of previous branches
It is hard to give concrete examples that apply to all projects since
each project is free to use its own release numbering scheme. However, a
project that includes versions 2.1.0, 2.1.1 and 2.1.2 in its release
directory almost certainly has some cleaning up to do. A project that
includes 1.0.6, 1.1.5 and 2.0.7 probably doesn't.
If you have any questions about how to manage your distribution
directory please contact the infrastructure team.
Thanks in advance,
Mark
on behalf of the ASF Infrastructure Team
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JUDDI-470) Remove old releases from dist
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam updated JUDDI-470:
------------------------------
Fix Version/s: 3.1.0
> Remove old releases from dist
> -----------------------------
>
> Key: JUDDI-470
> URL: https://issues.apache.org/jira/browse/JUDDI-470
> Project: jUDDI
> Issue Type: Task
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.1.0
>
>
> PMC members,
> As the ASF grows in size, so does the total size of the distribution
> artefacts we ask our mirror community to support for us. The larger this
> total size, the greater the strain on both ASF infrastructure and on the
> mirroring system.
> As per the release guidelines [1], only current releases should be
> available at http://www.apache.org/dist/. Monitoring of
> http://www.apache.org/dist/ [2] shows that some projects are not
> removing old releases. This is placing an unnecessary strain on both ASF
> infrastructure and on our mirror volunteers.
> Thanks to those PMCs that have been removing old releases from their
> distribution directory. The infrastructure appreciates you keeping on
> top of this.
> PMCs that have not been removing old releases are required to review
> their current distribution directory and remove any old releases.
> - PMCs using svnpubsub should remove old releases via svn.
> - PMCs not using svnpubsub should remove old releases directly from
> /www/www.apache.org/dist/<tlp> on people.apache.org at. Note that any
> deletions may take up to 24 hours to replicate to http://www.apache.org/dist
> In both cases it may take longer for changes to replicate to mirrors.
> Old releases removed from http://www.apache.org/dist/ are not lost.
> Release are automatically copied to http://archive.apache.org/dist/ and
> are never deleted.
> This inevitably raises the question what is a current release and what
> is an old release. To some extent, this varies from project to project
> but typically it amounts to the following:
> a) latest release of the current branch
> b) latest stable release of the current branch
> c) latest stable release of previous branches
> It is hard to give concrete examples that apply to all projects since
> each project is free to use its own release numbering scheme. However, a
> project that includes versions 2.1.0, 2.1.1 and 2.1.2 in its release
> directory almost certainly has some cleaning up to do. A project that
> includes 1.0.6, 1.1.5 and 2.0.7 probably doesn't.
> If you have any questions about how to manage your distribution
> directory please contact the infrastructure team.
> Thanks in advance,
> Mark
> on behalf of the ASF Infrastructure Team
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JUDDI-470) Remove old releases from dist
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam updated JUDDI-470:
------------------------------
Summary: Remove old releases from dist (was: Remove old released from dist)
> Remove old releases from dist
> -----------------------------
>
> Key: JUDDI-470
> URL: https://issues.apache.org/jira/browse/JUDDI-470
> Project: jUDDI
> Issue Type: Task
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
>
> PMC members,
> As the ASF grows in size, so does the total size of the distribution
> artefacts we ask our mirror community to support for us. The larger this
> total size, the greater the strain on both ASF infrastructure and on the
> mirroring system.
> As per the release guidelines [1], only current releases should be
> available at http://www.apache.org/dist/. Monitoring of
> http://www.apache.org/dist/ [2] shows that some projects are not
> removing old releases. This is placing an unnecessary strain on both ASF
> infrastructure and on our mirror volunteers.
> Thanks to those PMCs that have been removing old releases from their
> distribution directory. The infrastructure appreciates you keeping on
> top of this.
> PMCs that have not been removing old releases are required to review
> their current distribution directory and remove any old releases.
> - PMCs using svnpubsub should remove old releases via svn.
> - PMCs not using svnpubsub should remove old releases directly from
> /www/www.apache.org/dist/<tlp> on people.apache.org at. Note that any
> deletions may take up to 24 hours to replicate to http://www.apache.org/dist
> In both cases it may take longer for changes to replicate to mirrors.
> Old releases removed from http://www.apache.org/dist/ are not lost.
> Release are automatically copied to http://archive.apache.org/dist/ and
> are never deleted.
> This inevitably raises the question what is a current release and what
> is an old release. To some extent, this varies from project to project
> but typically it amounts to the following:
> a) latest release of the current branch
> b) latest stable release of the current branch
> c) latest stable release of previous branches
> It is hard to give concrete examples that apply to all projects since
> each project is free to use its own release numbering scheme. However, a
> project that includes versions 2.1.0, 2.1.1 and 2.1.2 in its release
> directory almost certainly has some cleaning up to do. A project that
> includes 1.0.6, 1.1.5 and 2.0.7 probably doesn't.
> If you have any questions about how to manage your distribution
> directory please contact the infrastructure team.
> Thanks in advance,
> Mark
> on behalf of the ASF Infrastructure Team
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (JUDDI-470) Remove old releases from dist
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam closed JUDDI-470.
-----------------------------
> Remove old releases from dist
> -----------------------------
>
> Key: JUDDI-470
> URL: https://issues.apache.org/jira/browse/JUDDI-470
> Project: jUDDI
> Issue Type: Task
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.1.0
>
>
> PMC members,
> As the ASF grows in size, so does the total size of the distribution
> artefacts we ask our mirror community to support for us. The larger this
> total size, the greater the strain on both ASF infrastructure and on the
> mirroring system.
> As per the release guidelines [1], only current releases should be
> available at http://www.apache.org/dist/. Monitoring of
> http://www.apache.org/dist/ [2] shows that some projects are not
> removing old releases. This is placing an unnecessary strain on both ASF
> infrastructure and on our mirror volunteers.
> Thanks to those PMCs that have been removing old releases from their
> distribution directory. The infrastructure appreciates you keeping on
> top of this.
> PMCs that have not been removing old releases are required to review
> their current distribution directory and remove any old releases.
> - PMCs using svnpubsub should remove old releases via svn.
> - PMCs not using svnpubsub should remove old releases directly from
> /www/www.apache.org/dist/<tlp> on people.apache.org at. Note that any
> deletions may take up to 24 hours to replicate to http://www.apache.org/dist
> In both cases it may take longer for changes to replicate to mirrors.
> Old releases removed from http://www.apache.org/dist/ are not lost.
> Release are automatically copied to http://archive.apache.org/dist/ and
> are never deleted.
> This inevitably raises the question what is a current release and what
> is an old release. To some extent, this varies from project to project
> but typically it amounts to the following:
> a) latest release of the current branch
> b) latest stable release of the current branch
> c) latest stable release of previous branches
> It is hard to give concrete examples that apply to all projects since
> each project is free to use its own release numbering scheme. However, a
> project that includes versions 2.1.0, 2.1.1 and 2.1.2 in its release
> directory almost certainly has some cleaning up to do. A project that
> includes 1.0.6, 1.1.5 and 2.0.7 probably doesn't.
> If you have any questions about how to manage your distribution
> directory please contact the infrastructure team.
> Thanks in advance,
> Mark
> on behalf of the ASF Infrastructure Team
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (JUDDI-470) Remove old releases from dist
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam resolved JUDDI-470.
-------------------------------
Resolution: Fixed
> Remove old releases from dist
> -----------------------------
>
> Key: JUDDI-470
> URL: https://issues.apache.org/jira/browse/JUDDI-470
> Project: jUDDI
> Issue Type: Task
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.1.0
>
>
> PMC members,
> As the ASF grows in size, so does the total size of the distribution
> artefacts we ask our mirror community to support for us. The larger this
> total size, the greater the strain on both ASF infrastructure and on the
> mirroring system.
> As per the release guidelines [1], only current releases should be
> available at http://www.apache.org/dist/. Monitoring of
> http://www.apache.org/dist/ [2] shows that some projects are not
> removing old releases. This is placing an unnecessary strain on both ASF
> infrastructure and on our mirror volunteers.
> Thanks to those PMCs that have been removing old releases from their
> distribution directory. The infrastructure appreciates you keeping on
> top of this.
> PMCs that have not been removing old releases are required to review
> their current distribution directory and remove any old releases.
> - PMCs using svnpubsub should remove old releases via svn.
> - PMCs not using svnpubsub should remove old releases directly from
> /www/www.apache.org/dist/<tlp> on people.apache.org at. Note that any
> deletions may take up to 24 hours to replicate to http://www.apache.org/dist
> In both cases it may take longer for changes to replicate to mirrors.
> Old releases removed from http://www.apache.org/dist/ are not lost.
> Release are automatically copied to http://archive.apache.org/dist/ and
> are never deleted.
> This inevitably raises the question what is a current release and what
> is an old release. To some extent, this varies from project to project
> but typically it amounts to the following:
> a) latest release of the current branch
> b) latest stable release of the current branch
> c) latest stable release of previous branches
> It is hard to give concrete examples that apply to all projects since
> each project is free to use its own release numbering scheme. However, a
> project that includes versions 2.1.0, 2.1.1 and 2.1.2 in its release
> directory almost certainly has some cleaning up to do. A project that
> includes 1.0.6, 1.1.5 and 2.0.7 probably doesn't.
> If you have any questions about how to manage your distribution
> directory please contact the infrastructure team.
> Thanks in advance,
> Mark
> on behalf of the ASF Infrastructure Team
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JUDDI-470) Remove old releases from dist
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048706#comment-13048706 ]
Kurt T Stam commented on JUDDI-470:
-----------------------------------
Done and will go live when we push out the site changes for 3.1.0.
> Remove old releases from dist
> -----------------------------
>
> Key: JUDDI-470
> URL: https://issues.apache.org/jira/browse/JUDDI-470
> Project: jUDDI
> Issue Type: Task
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.1.0
>
>
> PMC members,
> As the ASF grows in size, so does the total size of the distribution
> artefacts we ask our mirror community to support for us. The larger this
> total size, the greater the strain on both ASF infrastructure and on the
> mirroring system.
> As per the release guidelines [1], only current releases should be
> available at http://www.apache.org/dist/. Monitoring of
> http://www.apache.org/dist/ [2] shows that some projects are not
> removing old releases. This is placing an unnecessary strain on both ASF
> infrastructure and on our mirror volunteers.
> Thanks to those PMCs that have been removing old releases from their
> distribution directory. The infrastructure appreciates you keeping on
> top of this.
> PMCs that have not been removing old releases are required to review
> their current distribution directory and remove any old releases.
> - PMCs using svnpubsub should remove old releases via svn.
> - PMCs not using svnpubsub should remove old releases directly from
> /www/www.apache.org/dist/<tlp> on people.apache.org at. Note that any
> deletions may take up to 24 hours to replicate to http://www.apache.org/dist
> In both cases it may take longer for changes to replicate to mirrors.
> Old releases removed from http://www.apache.org/dist/ are not lost.
> Release are automatically copied to http://archive.apache.org/dist/ and
> are never deleted.
> This inevitably raises the question what is a current release and what
> is an old release. To some extent, this varies from project to project
> but typically it amounts to the following:
> a) latest release of the current branch
> b) latest stable release of the current branch
> c) latest stable release of previous branches
> It is hard to give concrete examples that apply to all projects since
> each project is free to use its own release numbering scheme. However, a
> project that includes versions 2.1.0, 2.1.1 and 2.1.2 in its release
> directory almost certainly has some cleaning up to do. A project that
> includes 1.0.6, 1.1.5 and 2.0.7 probably doesn't.
> If you have any questions about how to manage your distribution
> directory please contact the infrastructure team.
> Thanks in advance,
> Mark
> on behalf of the ASF Infrastructure Team
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira