[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bpel-dev] Update sites and Builds
- From: Bob Brodt <bbrodt@xxxxxxxxxx>
- Date: Fri, 06 Apr 2012 11:17:24 -0400 (EDT)
- Delivered-to: email@example.com
Yes I think this is a better way to go (I should also follow this scheme for the BPMN2 editor, come to think of it...)
At some point we need to do a version 1.0.0 review and graduate the project out of incubation status. I'll work on this next week. I'd like to get this done before juno - will that be a problem?
I can also update the project website next week once we all agree on this. Do we need to archive the original bits currently being consumed by the JBoss and Petals Link builds on download.eclipse.org somewhere? Maybe keep the original update-site as-is?
----- Original Message -----
> Le 06/04/2012 15:46, Mickael Istria a Ãcrit :
> >> I updated the juno build to run on every commit.
> >> Juno update sites will be published to
> >> http://build.eclipse.org/soa/bpel/juno
> > This is where I do not agree: why calling this update-site /juno if
> > it
> > is tested as working also with helios?
> > This url is confusing for consumers, that's why I would prefer
> > numbered one. What about 0.8.0/release ? And a note on the site
> > saying
> > 0.8.0 compatible with helios/juno ?
> OK, it works for me.
> It is just we have not been very strict on the versions until now.
> I can update the repo location for the build:
> I will do the same in the b3 agregator.
> Vincent Zurczak
> RCP Developer & ESB Consultant
> Petals Link: http://www.petalslink.com
> My Blog: http://vzurczak.wordpress.com
> +33 (0) 4 76 96 15 16
> bpel-dev mailing list