We decided to forgo an explicit future 3.0 branch and just make main
the place for future development. Commit the rabbit hole work to main
and it becomes a part of the current 2.5 development work. It will be
released as a 3.0 branch.
----- Original Message -----
From: "marc fleury" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 07, 2001 9:07 PM
Subject: RE: [JBoss-dev] JAWS_2_4 DTD
> ok good, so I need to deal with the branch stuff only if I want to back
port
> something. Ok.
>
> what happened to the 3.0 branch? I am finishing the jive stuff online
> (moving the forums) and would like to commit the rabbit hole work I
> have... will that go in 2.5?
>
> it is really "new" work... new Main, new configuration, the full j2ee
> shebang flirting with web services... will that go 2.5 if I don't cvs
> something?
>
> I am still a *little bit* confused :))
>
> he he, I feel like a monkey,
>
> TIA and all that
>
> marcf
>
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
> |M Stark
> |Sent: Saturday, July 07, 2001 11:49 PM
> |To: [EMAIL PROTECTED]
> |Subject: Re: [JBoss-dev] JAWS_2_4 DTD
> |
> |
> |Right, you committed to main. This is the 2.5 effort although its not a
> |branch.
> |
> |----- Original Message -----
> |From: "marc fleury" <[EMAIL PROTECTED]>
> |To: <[EMAIL PROTECTED]>
> |Sent: Saturday, July 07, 2001 6:34 PM
> |Subject: RE: [JBoss-dev] JAWS_2_4 DTD
> |
> |
> |> ok,
> |> I am super confused...
> |>
> |> so the changes I made to the interceptor won't show in 2.4 right? only
in
> |> the 2.5 branch.
> |>
> |> marcf
> |>
> |> |-----Original Message-----
> |> |From: [EMAIL PROTECTED]
> |> |[mailto:[EMAIL PROTECTED]]On Behalf Of
Scott
> |> |M Stark
> |> |Sent: Saturday, July 07, 2001 7:33 PM
> |> |To: [EMAIL PROTECTED]
> |> |Subject: Re: [JBoss-dev] JAWS_2_4 DTD
> |> |
> |> |
> |> |Yes, every incremental change made on a branch needs to be tagged to
> |> |make it easy to identify the changes going into a release.
> |> |
> |> |----- Original Message -----
> |> |From: "Aaron Mulder" <[EMAIL PROTECTED]>
> |> |To: <[EMAIL PROTECTED]>
> |> |Sent: Saturday, July 07, 2001 4:18 PM
> |> |Subject: Re: [JBoss-dev] JAWS_2_4 DTD
> |> |
> |> |
> |> |> 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
> |> |>
> |> |
> |> |
> |> |
> |> |_______________________________________________
> |> |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
>
>
>
> _______________________________________________
> 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
