[ 
https://issues.apache.org/jira/browse/KARAF-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jamie goodyear updated KARAF-1716:
----------------------------------

    Description: 
In preparation for the actual Karaf 3.0.0 release a 'beta' cut will be made, 
labelled as "karaf-3.0.0.RC1".

Note:
The goals of this RC include:

o Insuring that infrastructure is updated to handle a new Major version (nexus, 
hudson).
o Re-organizing the website to handle 2.x and 3.x instructions, demos, 
documentation
o Insure that all modules pass RAT testing, and that they can be uploaded to 
repo without being flagged for snapshots or licensing issues.
o And possibly most importantly - this artifact once produced will be used to 
help validate if any last minute changes need to be affected before the 'dot 
oh' cut is made. Platform integration testing for RC1 should be greatly 
encouraged, as should testing of features/tooling be made a priority.


  was:
In preparation for the actual Karaf 3.0.0 release a 'beta' cut will be made, 
labelled as "karaf-3.0.0.RC1".

Note:
The goals of this RC include:

o Insuring that infrastructure is updated to handle a new Major version (nexus, 
hudson).
o Re-organizing the website to handle 2.x and 3.x instructions, demos, 
documentation
o Insure that all modules pass RAT testing, and that they can be uploaded to 
repo without being flagged for snapshots or licensing issues.


    
> Apache Karaf 3.0.0.RC1 
> -----------------------
>
>                 Key: KARAF-1716
>                 URL: https://issues.apache.org/jira/browse/KARAF-1716
>             Project: Karaf
>          Issue Type: Task
>            Reporter: Jamie goodyear
>             Fix For: 3.0.0.RC1
>
>
> In preparation for the actual Karaf 3.0.0 release a 'beta' cut will be made, 
> labelled as "karaf-3.0.0.RC1".
> Note:
> The goals of this RC include:
> o Insuring that infrastructure is updated to handle a new Major version 
> (nexus, hudson).
> o Re-organizing the website to handle 2.x and 3.x instructions, demos, 
> documentation
> o Insure that all modules pass RAT testing, and that they can be uploaded to 
> repo without being flagged for snapshots or licensing issues.
> o And possibly most importantly - this artifact once produced will be used to 
> help validate if any last minute changes need to be affected before the 'dot 
> oh' cut is made. Platform integration testing for RC1 should be greatly 
> encouraged, as should testing of features/tooling be made a priority.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to