Maybe we could think of using a 0.6.0/snapshots repository, and then
when a build get ready to go to a juno milestone, copy it into
0.6.0/milestone repo, and when a build gets ready to be released,
copy it into 0.6.0/releases repository.
On 04/05/2012 05:19 PM, Bob Brodt wrote:
Works for me. Does this cause any problems with the
builds targeted for juno between now and its scheduled release
date?
Hi all,
What about using numbered versions? It would be a pity to have
the /juno release working only on juno whereas there is no API
change that prevent it from running on Helios, Indigo...
IMHO a better pattern would be to use versionned releases and
then to say version x.y.z has for minimal requirement Indigo,
x.y,z+1 has for minimal requirement juno... And the best thing
would be to provide new features without adding dependencies
on the "newest" stuff, so that BPEL tools consumers could use
newer version without having to update their platform.
Thoughts?
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
_______________________________________________
bpel-dev mailing list
bpel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/bpel-dev
|
