On Sat, 7 Jul 2001, Scott M Stark wrote:
> When you make a change to a branch you need to tag it with the
> next beta binary release tag: Rel_<major>.<even_minor>.<patch>.<build>
Are you saying that a release does not just label and use the
"head of the branch" but is built based on a label created at the time of
the previous release or something? Wouldn't it just be easier to tag the
current code in the branch when you're ready to make the release?
I made a change to the 2.4 metadata to handle the array types
(which never showed up on the mailing list due to the CVS weirdness but is
actually in the repository). I did not actually tag it though, so if I
need to tag it in order for it to be included in the next build, let me
know.
Aaron
> A change typically does not use the latest label if that is what your
> referring to as the "current 2_4 label".
>
>
> >
> > the datasource element was added to the entity element in version 1.1.2.2
> > on Bracnh_2_4. But it hasn't been updated on the main branch or added to
> > the 2_4 label. Shouldn't this change go onto both main and the current 2_4
> > label?
> >
> > There is also a code change associated with this -
> > src/main/org/jboss/ejb/plugins/jaws/metadata/JawsEntityMetaData.java also
> > on the 2_4 branch but not in the label but these changes are on main
> (added
> > in version 1.11).
> >
> > Mike S-R
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
