Re: [jdf-dev] EAP 6.2 Archetypes

Hi guys. I did: 1 - Prepared EAP 6.2 Archetypes: Synch: https://github.com/jboss-developer/jboss-eap-archetypes/commit/d532e54d6c... Tag: https://github.com/jboss-developer/jboss-eap-archetypes/releases/tag/6.2.... 2- Release EAP 6.2 Archetype in a staged repo: https://repository.jboss.org/nexus/content/repositories/jboss_releases_st... Now I need to know if will we let QE team work on this release or if should I promote this Archetypes based on the tests I made. I'm asking that because I consider it isn't a community release anymore so I think QE production tests should handle it. Thanks >> Em 09/12/13 17:43, Rafael Benevides escreveu: >>> Hi guys, >>> >>> Sorry for the wide audience but since EAP 6.2 was released last week, the archetypes ( https://github.com/jboss-developer/jboss-eap-archetypes ) was not even mentioned. >>> >>> Since Archetypes are part of the stacks, I'd like to know who in productization team should handle the archetypes? >>> >>> WFK 2.4 Archetypes was released to Maven Central after a period in a nexus staged repository being tested by WFK QE team. Can I assume that we will have the same approach for EAP 6.2 Archetypes? If so, there are some steps missing that it's needed and the time is flying. >>> >>> 1 - Prepare the EAP 6.2 Archetypes based on a EAP 6.2 Quickstarts tag >>> 2 - Release EAP 6.2 Archetype in a staged repo >>> 3 - QE test/fix cycle on the Archetypes >>> 4 - Promote the stage repo >>> 5 - Ask to Sonatype to include this new archetype groupId (org.jboss.archetype.eap) to be synched with Maven Central >>> 6 - Update stacks.yaml >>> >>> So the purpose of this email is bring EAP Archetypes under discussion (at least for this release) since Pete is preparing a plan that should work for next releases. >>> >>> -- >>> >>> Rafael Benevides | Senior Software Engineer >>> JBoss Developer >>> M: +55-61-9269-6576 >>> >>> <Mail Attachment.jpeg> >>> >>> Better technology. Faster innovation. Powered by community collaboration. >>> See how it works at www.redhat.com >>> >>> <Mail Attachment.png> <Mail Attachment.png> >> >