5 a.m.
Hi everyone
I am planning on cutting a branch of https://anonsvn.jboss.org/repos/jbosstool/trunk for a
JBDS SOA Tooling Beta1. Is there anything anyone urgently needs to commit before I
branch?
Regards
Doug
Douglas Palmer
dpalmer(a)redhat.com
JBoss, by Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Mark Hegarty (Ireland), Matt Parson
(USA), Charlie Peters (USA)
5:17 a.m.
could we for simplicity sake not use the same branch we will use for jboss tools b3
tomorrow ?
It's going to be confusing if using a different one.
/max
On Apr 26, 2012, at 12:00 , Doug Palmer wrote:
Hi everyone
I am planning on cutting a branch of https://anonsvn.jboss.org/repos/jbosstool/trunk for
a JBDS SOA Tooling Beta1. Is there anything anyone urgently needs to commit before I
branch?
Regards
Doug
Douglas Palmer
dpalmer(a)redhat.com
JBoss, by Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Mark Hegarty (Ireland), Matt Parson
(USA), Charlie Peters (USA)
12:10 p.m.
New subject: [Soa-tools-list] Branching for SOA tools Beta1
After much discussion today the decision was (I believe) made to branch
SOA stuff independently from the Core stuff so that there won't be any
parent pom collisions & qualifiers will be updated correctly.
Thus, expect to see new branches here [1] and here [2] for the SOA
Tooling Beta1 branch:
[1] https://svn.jboss.org/repos/jbosstools/branches/
[2] https://svn.jboss.org/repos/devstudio/branches/
For components who rely on the upstream JBT parent pom (jbpm3, bpel,
esb, modeshape, etc.), please ensure that the version you're using in
your root pom.xml is the correct one from this new branch (eg.,
"3.3.0.Beta1-SOA-SNAPSHOT", and that your job correctly defines the
right upstream bits (eg., _stable_branch jobs or 3.3.indigo sites
instead of trunk).
Doug, when do you plan to perform the two branching operations, fix the
_stable_branch jobs, commit the changes to root poms (as needed, if
component leads fail to do so) and announce the associated code freeze?
Cheers,
Nick
On 04/26/2012 06:17 AM, Max Rydahl Andersen wrote:
could we for simplicity sake not use the same branch we will use for
jboss tools b3 tomorrow ?
It's going to be confusing if using a different one.
/max
On Apr 26, 2012, at 12:00 , Doug Palmer wrote:
> Hi everyone
>
> I am planning on cutting a branch of https://anonsvn.jboss.org/repos/jbosstool/trunk
for a JBDS SOA Tooling Beta1. Is there anything anyone urgently needs to commit before I
branch?
>
> Regards
> Doug
>
> Douglas Palmer
> dpalmer(a)redhat.com
>
> JBoss, by Red Hat
> Registered in England and Wales under Company Registration No. 03798903
> Directors: Michael Cunningham (USA), Mark Hegarty (Ireland), Matt Parson
> (USA), Charlie Peters (USA)
>
>
_______________________________________________
Soa-tools-list mailing list
Soa-tools-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/soa-tools-list
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
10:32 a.m.
New subject: Branching for SOA tools Beta2
Hi everyone
I am planning on building Beta2 of the soa tools tomorrow; I will cut the branch at about
9AM GMT. Please don't break anything between now and then ;)
Regards
Doug
Douglas Palmer
dpalmer(a)redhat.com
JBoss, by Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Mark Hegarty (Ireland), Matt Parson
(USA), Charlie Peters (USA)
4571
days inactive
4592
days old
jbosstools-dev@lists.jboss.org
3 comments
3 participants
participants (3)
-
Doug Palmer -
Max Rydahl Andersen -
Nick Boldt