[jbosstools-issues] [JBoss JIRA] (JBIDE-26323) Add JBoss Tools 4.9.0.AM1 to list of releases on tools.jboss.org

Nick Boldt (JIRA) issues at jboss.org
Tue Aug 28 15:07:00 EDT 2018


    [ https://issues.jboss.org/browse/JBIDE-26323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625311#comment-13625311 ] 

Nick Boldt edited comment on JBIDE-26323 at 8/28/18 3:06 PM:
-------------------------------------------------------------

I guess Mat didn't run any of the publishing scripts to copy from staging to development while I was on PTO / in Europe for the Che F2F. 

I see stuff in stage, but not in prod. http://download.jboss.org/jbosstools/photon/staging/updates/core/

Why didn't you say anything the first week of August? I think we were all three NOT on PTO that week. I guess I assumed that if anything went wrong, you would contact me and him to get it sorted. 

(Checking my old sent mail, it appears I may have implied accidentally that the staging steps were all that Mat was required to do in my absence -- not the release steps too. If that's the case, I'll try to be more explicit next time.)

Now that it's 28 days later, do we need to bother releasing AM1 after AM2? Who would ever want to download it when there's a newer version?

We could:

a) retarget the N&N files so they're for AM2 instead of AM1, or
b) omit the links to zips in products.yaml for the AM1 release (so at least the 'coming soon' label goes away), or
c) teach you how to run the scripts that copy from stage to prod, so you can run the Jenkins jobs to make sure AM1 is released. 

WDYT? 



was (Author: nickboldt):
I guess Mat didn't run any of the publishing scripts to copy from staging to development while I was on PTO / in Europe for the Che F2F. 

I see stuff in stage, but not in prod. http://download.jboss.org/jbosstools/photon/staging/updates/core/

Why didn't you say anything the first week of August? I think we were all three NOT on PTO that week. I guess I assumed that if anything went wrong, you would contact me and him to get it sorted. 

Now that it's 28 days later, do we need to bother releasing AM1 after AM2? Who would ever want to download it when there's a newer version?

We could:

a) retarget the N&N files so they're for AM2 instead of AM1, or
b) omit the links to zips in products.yaml for the AM1 release (so at least the 'coming soon' label goes away), or
c) teach you how to run the scripts that copy from stage to prod, so you can run the Jenkins jobs to make sure AM1 is released. 

WDYT? 


> Add JBoss Tools 4.9.0.AM1 to list of releases on tools.jboss.org
> ----------------------------------------------------------------
>
>                 Key: JBIDE-26323
>                 URL: https://issues.jboss.org/browse/JBIDE-26323
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: website
>    Affects Versions: 4.9.0.AM1
>            Reporter: Jeff MAURY
>            Assignee: Jeff MAURY
>             Fix For: 4.9.0.AM3
>
>         Attachments: screenshot-1.png
>
>
> I noticed 4.9.0.AM1 was not defined in website causing this release to appear as 'Coming soon' even after 4.9.0.AM2 is out.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jbosstools-issues mailing list