[jdf-dev] New release versions scheme

[Rafael Benevides]

Hi all,

We planned to discuss the new release schema on Judcon.

I think that for this kind of discussion it's important to identify the 
dependencies from our deliverables. I think that's important because it 
is probable that we will need to change the number of versions used 
until now and I also think that the new release version number should 
make sense to all artifacts.

Based on the attached diagram we can also discuss the release order. 
When JDF .Final release is near, the amount of work to make everything 
fit can be reduced if we follow the release cycle proposed:

- Release the BOMs
- Update the Stacks.yaml with new BOM version
- Update the Quickstarts to use the new BOM
- Update the Archetypes to use the new Quickstarts (with the new BOM)
- Update the Stacks.yaml with new Archetype version
- Finally release JDF site

Well, that's just a brainstorm and a initial point to begin the discussion.


-- 
Rafael Benevides | Senior Software Engineer
Red Hat Brazil
+55-61-9269-6576

Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Dependencies.png
Type: image/png
Size: 65058 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jdf-dev/attachments/20130417/af5fcaf5/attachment-0001.png