You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "sebb@apache.org (JIRA)" <ji...@apache.org> on 2009/12/08 21:13:53 UTC

[jira] Created: (CAMEL-2268) No files for release 2.1.0

No files for release 2.1.0
--------------------------

                 Key: CAMEL-2268
                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
             Project: Apache Camel
          Issue Type: Bug
          Components: website
    Affects Versions: 2.1.0
         Environment: http://camel.apache.org/camel-210-release.html
            Reporter: sebb@apache.org
            Priority: Blocker


The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.

The latest release found is 2.0.0.

The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.

Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS

Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56371#action_56371 ] 

Hadrian Zbarcea commented on CAMEL-2268:
----------------------------------------

Fair enough. I will make the changes you recommend. I will also look into archiving old releases.

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Task
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56345#action_56345 ] 

Claus Ibsen commented on CAMEL-2268:
------------------------------------

I have added a link to the KEYS from the download page
{code}
h3. Keys
The {{KEYS}} used to sign the release can be found [here|http://www.apache.org/dist/camel/apache-camel/KEYS].
{code}

Will take some hours before its synced to the static html pages

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Priority: Blocker
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Resolved: (CAMEL-2268) No files for release 2.1.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-2268.
--------------------------------

    Fix Version/s: 2.5.0
                       (was: 2.1.0)
       Resolution: Won't Fix

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Task
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebbASF
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.5.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56344#action_56344 ] 

Claus Ibsen commented on CAMEL-2268:
------------------------------------

The 2.1 release is already in the Apache dist
http://www.apache.org/dist/camel/apache-camel/

Its the mirrors that hasnt propagated the release. Hadrian is checking out why but its surely an Apache infra issue and not Camel specific

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Priority: Blocker
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "sebb@apache.org (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56366#action_56366 ] 

sebb@apache.org commented on CAMEL-2268:
----------------------------------------

I'm sorry if you think my wording was impolite. I was just trying to state the ASF policy as I understand it.  I was obviously too terse.

Only software releases that have been approved by the PMC are allowed to be published to the general public.
AIUI this is vital for legal reasons.

SVN and Snapshots can only be published to the developer community.

BTW I think OpenJPA is wrong too. For a better example, see HTTPD - http://httpd.apache.org/ - the SVN link is only provided on developer pages.

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Task
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Assigned: (CAMEL-2268) No files for release 2.1.0

Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea reassigned CAMEL-2268:
--------------------------------------

    Assignee: Hadrian Zbarcea

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Task
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56346#action_56346 ] 

Claus Ibsen commented on CAMEL-2268:
------------------------------------

The mirrors seems to be propagated now.

I can find 2.1.0 in Sweden, Czech, Hong Kong, Holland etc.
http://websiterra.com/friends/apache/camel/apache-camel/2.1.0/
http://mirror.pearsys.com/camel/apache-camel/2.1.0/
http://apache.hippo.nl/camel/apache-camel/

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Priority: Blocker
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Resolved: (CAMEL-2268) No files for release 2.1.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-2268.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Priority: Blocker
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56369#action_56369 ] 

Claus Ibsen commented on CAMEL-2268:
------------------------------------

What if we create a sub page on download named - Developer download - or something like that.

And then post a link from the download page to that page? Then the download page will only have releases.

And I do believe if this was such a major problem, directions would have been given from the board etc. and not by an individual who we do not know who is and have newer been in touch with this community before. 

Lets start over and try to fix that download page.

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Task
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "sebb@apache.org (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56370#action_56370 ] 

sebb@apache.org commented on CAMEL-2268:
----------------------------------------

Thanks for posting the URL. This contains the text:

bq. Test Packages are not Apache releases. All releases require due process and official approval. Test packages are for testing ongoing development and should only be discussed on the project development lists.

AFAICT this means that the details of such releases should be kept off public download pages.

I think it's important to make a distinction between developer information and user information which is aimed at the public.
So I think it would be better to keep the download page for official downloads only.

The Camel home page already has a "Developers" section which includes SVN links already. You could add a page for Snapshots, but please ensure that you add suitable disclaimers, for example as done by JMeter:  http://people.apache.org/builds/jakarta-jmeter/nightly/

Re: "Releases in Progress" - IMO this is not really applicable to the general public, and belongs in the "Developers" section.
However, so long as there are no links to software downloads, the descriptions of new features etc could be left where they are.
I still think it would be better in the Developers section though.

As to direction from the board - I agree.

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Task
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56363#action_56363 ] 

Claus Ibsen commented on CAMEL-2268:
------------------------------------

Sebb Apache is community over code and users like that they can find the latest releases and in progress releases on that page.
And instructions how to get hold of them if using maven etc.

Other Apache projects do the same, for example OpenJPA
http://openjpa.apache.org/downloads.html

You have never been involved with the Camel community before and now you step in and creates a bit of disturbance. 
We are glad that you point out some issues with a link to KEYS etc. but due respect you could have expressed this in a nicer and more collaborate and understanding way.

Dont you think you should appreciate how well the Camel community is going than trying to tell how the download page should look like?

Also when you community you do not use a signature in mail etc. or you JIRA account is just an anonym email which makes it a bit suspect to be in dialog with you.

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Priority: Blocker
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "Hadrian Zbarcea (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56368#action_56368 ] 

Hadrian Zbarcea commented on CAMEL-2268:
----------------------------------------

@Sebastian,

We appreciate your passion and your desire to improve things and as long as communication stays within the limits of decency and respect, we're all good. I don't think any boundaries were crossed :).

I am rereading the official [Apache release guide|http://www.apache.org/dev/release.html] which mostly states what should be done, not what shouldn't.

In the Camel wiki space we do have an in progress folder that helps us capture the things that will be in the next release and way before the release itself. It helps us a lot and words very well for us. That is public information actually, as the wiki is viewable by everybody. I see no reason to change that, but from what I understand you don't have a problem with that, but with the fact that the whole in progress section is published to the public site, correct?

You point out to a few things that you consider violations of the apache policy, but it's not clear what exactly you suggest. I would appreciate if you could rephrase you comment as "please to this" instead of (or in addition to) "don't do that". Also part of the apache way is the "doer" attitude, so feel free to make some of the corrections yourself and know that you have our gratitude. In any event, I will work with you on this and make sure the Camel community is a good (nay, an exemplary) citizen of the Apache community.



> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Task
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Commented: (CAMEL-2268) No files for release 2.1.0

Posted by "sebb@apache.org (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56358#action_56358 ] 

sebb@apache.org commented on CAMEL-2268:
----------------------------------------

OK, I can see the 2.1.0 files now - not sure why they did not appear earlier, perhaps a caching problem.

However, there are still some major problems with the download pages.
Only releases that have been formally voted on and approved by the PMC should be listed on public pages.

- they should not advertise the SVN links; 
- should not contain Releases In Progress or SNAPSHOTS
- ALL the pages which have download links must have links to the KEYS file; and all downloads need a hash file, either MD5 or SHA1.


> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Priority: Blocker
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Updated: (CAMEL-2268) No files for release 2.1.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-2268:
-------------------------------

    Priority: Major  (was: Blocker)

Not a blocker

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Reopened: (CAMEL-2268) No files for release 2.1.0

Posted by "sebb@apache.org (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

sebb@apache.org reopened CAMEL-2268:
------------------------------------


> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>            Priority: Blocker
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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


[jira] Updated: (CAMEL-2268) No files for release 2.1.0

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-2268:
-------------------------------

    Issue Type: Task  (was: Bug)

> No files for release 2.1.0
> --------------------------
>
>                 Key: CAMEL-2268
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2268
>             Project: Apache Camel
>          Issue Type: Task
>          Components: website
>    Affects Versions: 2.1.0
>         Environment: http://camel.apache.org/camel-210-release.html
>            Reporter: sebb@apache.org
>             Fix For: 2.1.0
>
>
> The page http://camel.apache.org/camel-210-release.html refers to release 2.1.0, but as far as I can make out, there are no files in the distribution directory for this release.
> The latest release found is 2.0.0.
> The web-site should not be advertising releases that have not been uploaded - indeed the release should only be advertised once the archives have been added to most of the mirrors.
> Furthermore, the download section MUST carry a link to the KEYS file on the main Apache server, i.e.  http://www.apache.org/dist/camel/apache-camel/KEYS
> Also, the download page should not carry a link to SVN; SVN should only be advertised to developers.

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