You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Jacek Laskowski <ja...@laskowski.net.pl> on 2007/09/12 22:39:43 UTC
Branching trunk to branches/3.0
Hi,
Okey, so it seems everybody's interested in 3.0 release. I have never
done any releases before so I'm asking you for help whenever I'm about
to make a mistake or whatever you think should be done another way.
With this said, I'm going to branch the trunk to the 3.0 branch first.
svn copy -m "OpenEJB 3.0 branch" \
https://svn.apache.org/repos/asf/openejb/trunk/openejb3 \
https://svn.apache.org/repos/asf/openejb/branches/3.0
Unless I hear any objection, I'll cut it tomorrow, 09/13 at around
9:00 PM CET (GMT+1). I'll be hanging out on #openejb (irc) while doing
it.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Branching trunk to branches/3.0
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/14/07, Kevan Miller <ke...@gmail.com> wrote:
>
> FYI, the license/notice files in openejb3 are not correct. Generated
> jars don't include license/notice files. We cannot release in their
> current form.
>
> I'll start taking a look at this, but will probably wait until the
> morning... If anybody else is interested, it's really a lot of fun...
Just run RAT [1]
jlaskowski@dev /cygdrive/c/oss/openejb-3.0-beta-1
$ mvn org.codehaus.mojo:rat-maven-plugin:1.0-alpha-3:check
...
[INFO] [rat:check]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Too many unapproved licenses: 42
[INFO] ------------------------------------------------------------------------
...
Nice. I'll be looking into it tonight.
[1] http://code.google.com/p/arat/
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Branching trunk to branches/3.0
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/13/07, Kevan Miller <ke...@gmail.com> wrote:
> I'll start taking a look at this, but will probably wait until the
> morning... If anybody else is interested, it's really a lot of fun...
I'll be around on irc later tonight (CET) so I'll step forward to help
a little where you see me fit well.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Branching trunk to branches/3.0
Posted by Kevan Miller <ke...@gmail.com>.
FYI, the license/notice files in openejb3 are not correct. Generated
jars don't include license/notice files. We cannot release in their
current form.
I'll start taking a look at this, but will probably wait until the
morning... If anybody else is interested, it's really a lot of fun...
--kevan
Re: Branching trunk to branches/3.0
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/14/07, David Blevins <da...@visi.com> wrote:
>
> On Sep 13, 2007, at 3:34 PM, Jacek Laskowski wrote:
>
> > On 9/13/07, David Blevins <da...@visi.com> wrote:
> >
> >> The version would be 3.0-beta-1.
> >
> > Version changed to 3.0-RC1.
>
> Beta is the term most people liked.
Done. Just for the record. Here are the command I did. On to fixing
the missing LICENSE/NOTICE files in jar files.
jlaskowski@dev /cygdrive/c/oss/openejb3.0
$ find . -name pom.xml | xargs perl -pi -e
"s;<version>3.0-RC1</version>;<version>3.0-beta-1</version>;g"
jlaskowski@dev /cygdrive/c/oss/openejb3.0
$ find . -name *.bak | xargs rm
jlaskowski@dev /cygdrive/c/oss/openejb3.0
$ svn status
M assembly/openejb-itests-webapp/pom.xml
M assembly/openejb-tomcat/pom.xml
M assembly/openejb-standalone/pom.xml
M assembly/pom.xml
M container/openejb-javaagent/pom.xml
M container/openejb-jee/pom.xml
M container/openejb-loader/pom.xml
M container/openejb-core/pom.xml
M container/pom.xml
M server/openejb-http/pom.xml
M server/openejb-axis/pom.xml
M server/openejb-ejbd/pom.xml
M server/openejb-corba/pom.xml
M server/openejb-server/pom.xml
M server/openejb-webadmin/pom.xml
M server/openejb-hsql/pom.xml
M server/openejb-admin/pom.xml
M server/openejb-activemq/pom.xml
M server/pom.xml
M server/openejb-telnet/pom.xml
M server/openejb-derbynet/pom.xml
M server/openejb-xfire/pom.xml
M server/openejb-client/pom.xml
M pom.xml
M itests/openejb-itests-beans/pom.xml
M itests/openejb-itests-client/pom.xml
M itests/openejb-itests-app/pom.xml
M itests/pom.xml
M itests/openejb-itests-interceptor-beans/pom.xml
M examples/ejb-injection/pom.xml
M examples/calculator-stateless-pojo/pom.xml
M examples/expanded-env-entries/pom.xml
M examples/helloworld-stateful-pojo/pom.xml
M examples/resource-injection/pom.xml
M examples/telephone-stateful/pom.xml
M examples/counter-stateful-pojo/pom.xml
M examples/pom.xml
jlaskowski@dev /cygdrive/c/oss/openejb3.0
$ svn ci -m 'Updated to version 3.0-beta-1' .
jlaskowski@dev /cygdrive/c/oss/openejb3.0
$ svn mv https://svn.apache.org/repos/asf/openejb/branches/3.0
https://svn.apache.org/repos/asf/openejb/branches/3.0-beta-1
jlaskowski@dev /cygdrive/c/oss
$ rm -rf openejb3.0
jlaskowski@dev /cygdrive/c/oss
$ svn co https://svn.apache.org/repos/asf/openejb/branches/3.0-beta-1
openejb-3.0-beta-1
...
U openejb-3.0-beta-1
Checked out revision 575688.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Branching trunk to branches/3.0
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 13, 2007, at 7:16 PM, David Blevins wrote:
>
> On Sep 13, 2007, at 3:34 PM, Jacek Laskowski wrote:
>
>> On 9/13/07, David Blevins <da...@visi.com> wrote:
>>
>>> The version would be 3.0-beta-1.
>>
>> Version changed to 3.0-RC1.
>
> Beta is the term most people liked. I looked up Release Candidate
> just now to reality check with my gut understanding of it -- maybe
> it's better -- but it doesn't seem to fit. Wikipedia's definition
> of beta seems to fit well:
>
> A beta version is the first version released outside the
> organization or community that develops the software, for the
> purpose of evaluation or real-world black/grey-box testing. [1]
I prefer beta, also.
>
>
>> I'm not sure whether or not the branch
>> name should reflect the version. I think it should. Once it passes a
>> final release vote the branch will be copied over to a tag, doesn't
>> it?
>
> Right on both counts. We should even tack on "openejb" onto the
> tag name just in case we release other things like eclipse plugins
> or something.
hmm. well, i'd start considering maintaining a separate directory
structures at a higher level to avoid that kind of conflict...
openejb/container-server/trunk/
openejb/container-server/tags
openejb/eclipse-plugin/trunk
etc.
Assuming that we want to keep container and server together. So think
up a better name... ;-)
--kevan
Re: Branching trunk to branches/3.0
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/13/07, David Blevins <da...@visi.com> wrote:
> Beta is the term most people liked.
I'm sold [*]. I'll change it later today.
[*] sold == convinced, right?
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Branching trunk to branches/3.0
Posted by David Blevins <da...@visi.com>.
On Sep 13, 2007, at 3:34 PM, Jacek Laskowski wrote:
> On 9/13/07, David Blevins <da...@visi.com> wrote:
>
>> The version would be 3.0-beta-1.
>
> Version changed to 3.0-RC1.
Beta is the term most people liked. I looked up Release Candidate
just now to reality check with my gut understanding of it -- maybe
it's better -- but it doesn't seem to fit. Wikipedia's definition of
beta seems to fit well:
A beta version is the first version released outside the
organization or community that develops the software, for the
purpose of evaluation or real-world black/grey-box testing. [1]
> I'm not sure whether or not the branch
> name should reflect the version. I think it should. Once it passes a
> final release vote the branch will be copied over to a tag, doesn't
> it?
Right on both counts. We should even tack on "openejb" onto the tag
name just in case we release other things like eclipse plugins or
something.
-David
[1] http://en.wikipedia.org/wiki/Release_candidate
Re: Branching trunk to branches/3.0
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/13/07, David Blevins <da...@visi.com> wrote:
> The version would be 3.0-beta-1.
Version changed to 3.0-RC1. I'm not sure whether or not the branch
name should reflect the version. I think it should. Once it passes a
final release vote the branch will be copied over to a tag, doesn't
it?
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Branching trunk to branches/3.0
Posted by David Blevins <da...@visi.com>.
On Sep 13, 2007, at 1:17 PM, Jacek Laskowski wrote:
> On 9/12/07, Jacek Laskowski <ja...@laskowski.net.pl> wrote:
>
>> With this said, I'm going to branch the trunk to the 3.0 branch
>> first.
>>
>> svn copy -m "OpenEJB 3.0 branch" \
>> https://svn.apache.org/repos/asf/openejb/trunk/openejb3 \
>> https://svn.apache.org/repos/asf/openejb/branches/3.0
>
> Done. The next step is to update poms with 3.0 version and let it
> be reviewed.
The version would be 3.0-beta-1.
-David
Re: Branching trunk to branches/3.0
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/12/07, Jacek Laskowski <ja...@laskowski.net.pl> wrote:
> With this said, I'm going to branch the trunk to the 3.0 branch first.
>
> svn copy -m "OpenEJB 3.0 branch" \
> https://svn.apache.org/repos/asf/openejb/trunk/openejb3 \
> https://svn.apache.org/repos/asf/openejb/branches/3.0
Done. The next step is to update poms with 3.0 version and let it be reviewed.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl