Please disregard this query. Martha has clarified via another channel that we don't need to do anything in the yum repo or the rpm's metadata, as long as release notes & marketing materials clearly identify the rpm as Technology Preview.
Thanks & apologies for the spam, Nick On Thu, Nov 24, 2016 at 12:36 PM, Nick Boldt <[email protected]> wrote: > In RHDEVDOCS-120 [1], I asked what we should do to label the new Red > Hat JBoss Developer Studio rpm package as a Technology Preview. > > This RPM is being released in concert with the upcoming RH SCL 2.3 > release, but will be available for install from a separate yum repo > such as this site [2]. > > Robert suggested I ask you for advice. > > [1] > https://issues.jboss.org/browse/RHDEVDOCS-120?focusedCommentId=13327430&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13327430 > [2] https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/ > > Details in the above JIRA. > > I'm happy to make changes to the RPM metadata and the HTML page, but I > need to do *so before EOD today*, as we're already into code freeze > and I plan to build the final bits tonight & sign them tomorrow. > > Thanks in advance, > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com _______________________________________________ SCLorg mailing list [email protected] https://www.redhat.com/mailman/listinfo/sclorg
