Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WINDUP-2079 - prepare for 4.1.0.Final release. #641

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

johnsteele
Copy link

@nickboldt I pretty much copied the compositeArtifacts.xml && compositeContent.xml && p2.index from /jbosstools/oxygen/stable/updates/rhamt/

@nickboldt nickboldt self-requested a review June 19, 2018 23:39
Copy link
Member

@nickboldt nickboldt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your 4.1.0.Final content should not be in a rolling content folder like "master".

http://download.jboss.org/jbosstools/oxygen/stable/updates/rhamt/ has a 4.0.1.Final folder under it, which is linked from the composite*.xml files.

Similarly, http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ has 4.0.0.* pre-Final milestones, and the 4.0.0.Final site is linked from the composite*.xml files.

Why use master?

Also, I can't merge these until your content is published to a folder under these, or else the composite site will be invalid.

http://download.jboss.org/jbosstools/photon/stable/updates/rhamt/
or
http://download.jboss.org/jbosstools/photon/development/updates/rhamt/

Do you plan to release a pre-Final 4.1.0 milestone, or will you just do a stable Final release? If you're not going to do alpha/beta milestone releases, there's no point even bothering with /development/ URLs, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants