You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcs-dev@jakarta.apache.org by Thomas Vandahl <tv...@apache.org> on 2007/05/26 12:04:19 UTC
[VOTE] Release JCS 1.3
Hi folks,
After much discussion on the JCS developer list, the first official
release of JCS (version 1.3) after leaving the Turbine project is ready
to vote on.
You can find the created artifacts here:
site: http://people.apache.org/~tv/jcs/
jars: http://people.apache.org/~tv/jcs/jar/
dist: http://people.apache.org/~tv/jcs/dist/
Now, shall we release JCS as it is published there?
[ ] +1 Yes, JCS 1.3 should be released
[ ] 0 I do not care
[ ] -1 No (give reasons)
Voting is subject to the rules described in
http://jakarta.apache.org/site/management.html
The deadline is Sat, June 1 2007, 12:00 CET
Note that the Jakarta PMC has the final word on whether the release is
published
or not.
Bye, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Hanson Char <ha...@gmail.com>.
[x] +1 Yes, JCS 1.3 should be released
[ ] 0 I do not care
[ ] -1 No (give reasons)
Hanson Char
On 5/26/07, Thomas Vandahl <tv...@apache.org> wrote:
>
> Hi folks,
>
> After much discussion on the JCS developer list, the first official
> release of JCS (version 1.3) after leaving the Turbine project is ready
> to vote on.
>
> You can find the created artifacts here:
> site: http://people.apache.org/~tv/jcs/
> jars: http://people.apache.org/~tv/jcs/jar/
> dist: http://people.apache.org/~tv/jcs/dist/
>
> Now, shall we release JCS as it is published there?
>
> [ ] +1 Yes, JCS 1.3 should be released
> [ ] 0 I do not care
> [ ] -1 No (give reasons)
>
> Voting is subject to the rules described in
> http://jakarta.apache.org/site/management.html
>
> The deadline is Sat, June 1 2007, 12:00 CET
>
> Note that the Jakarta PMC has the final word on whether the release is
> published
> or not.
>
> Bye, Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
>
>
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Vandahl wrote:
> Now, shall we release JCS as it is published there?
>
> [X] +1 Yes, JCS 1.3 should be released
> [ ] 0 I do not care
> [ ] -1 No (give reasons)
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Corrected Result: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Vandahl wrote:
> Voting has closed. Here are the results:
>
> +1 votes:
> Hanson Char <ha...@gmail.com>
> Thomas Vandahl <tv...@apache.org>
> * Henning Schmiedehausen <hp...@intermeta.de>
> * Aaron Smuts <as...@yahoo.com>
> * Scott Eade <se...@backstagetech.com.au>
* Rony G. Flatscher <Ro...@wu-wien.ac.at>
>
> 0 votes:
* sebbaz@gmail.com
>
> -1 votes:
None.
(* denotes binding votes)
The vote has passed. We will make the artifacts available as soon as
possible.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Corrected Result: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Vandahl wrote:
> Voting has closed. Here are the results:
>
> +1 votes:
> Hanson Char <ha...@gmail.com>
> Thomas Vandahl <tv...@apache.org>
> * Henning Schmiedehausen <hp...@intermeta.de>
> * Aaron Smuts <as...@yahoo.com>
> * Scott Eade <se...@backstagetech.com.au>
* Rony G. Flatscher <Ro...@wu-wien.ac.at>
>
> 0 votes:
* sebbaz@gmail.com
>
> -1 votes:
None.
(* denotes binding votes)
The vote has passed. We will make the artifacts available as soon as
possible.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
This is my personal model for this stuff. YMMV
---- trunk -------+---- main development -----------
|
release branch branches/JCS_1_3
|
+ --- tag tags/JCS_1_3_RC1
|
+ --- tag tags/JCS_1_3_RC2
|
+ --- tag tags/JCS_1_3
|
+ --- tag tags/JCS_1_3_1
you release *from* a release branch *on* a release tag.
Best regards
Henning
On Wed, 2007-06-06 at 18:41 +0100, sebb wrote:
> On 06/06/07, Roland Weber <os...@dubioso.net> wrote:
> > Hi Thomas,
> >
> > >> If you changed the release files manually, you
> > >> should commit those changes to SVN and give Sebastian some time to
> > >> change his vote.
> > >
> > > We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
> > > SVN. This is at least what I understood the release-then-vote-policy
> > > means.
> >
> > The point of a SVN branch is to have an archived version of the
> > exact files that go into the release. If you have to change a
> > release after creating the branch, you should update the branch
> > and re-build the release from scratch. This is the best way to
> > make sure that releases can be reproduced.
>
> s/branch/tag/g surely?
>
> S///
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux, |gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 07/06/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> On Wed, 2007-06-06 at 19:13 +0100, sebb wrote:
> > On 06/06/07, Roland Weber <os...@dubioso.net> wrote:
> > > sebb wrote:
> > > > s/branch/tag/g surely?
> > >
> > > Eh... CVS tag = SVN branch? Whatever, the things that are
> >
> > No, CVS tag = SVN tag
>
> No. SVN tag == SVN branch == shallow directory copy.
Depends on your meaning of "shallow" - changing a file in the original
does not change the file in the copy.
> There is just a convention in SVN to distinguish branches and tags. Both
> are the same thing, just in different places ( /branches and /tags).
Yes, I think that's what I said.
> A CVS tag is something totally different. A CVS tag is a named set of
> different file revisions and basically a kludge if you do not have a
> repository-wide atomic revision number. Which subversion has.
What I meant was that the /tags directory is conventionally used in
SVN where one would use tags in CVS.
Rather than using the revision number for building/representing a
release, a tag is created, and then never updated. The tag tree thus
contains a specific revision of the the database, and is a way of
giving the revision a name.
As far as I can see, SVN tags are a convenience - one could just
document which revision constitutes the release, and use that to to do
the build or retrieve the files.
S///
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
On Wed, 2007-06-06 at 19:13 +0100, sebb wrote:
> On 06/06/07, Roland Weber <os...@dubioso.net> wrote:
> > sebb wrote:
> > > s/branch/tag/g surely?
> >
> > Eh... CVS tag = SVN branch? Whatever, the things that are
>
> No, CVS tag = SVN tag
No. SVN tag == SVN branch == shallow directory copy.
There is just a convention in SVN to distinguish branches and tags. Both
are the same thing, just in different places ( /branches and /tags).
A CVS tag is something totally different. A CVS tag is a named set of
different file revisions and basically a kludge if you do not have a
repository-wide atomic revision number. Which subversion has.
Best regards
Henning
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux, |gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Roland Weber <os...@dubioso.net>.
Hi Sebastian,
> So a release can be developed in a branch or the trunk; before the
> release is finally built the current files should be copied to a
> subdirectory of tags.
>
> The tags subdirectory should not be updated once created.
The branch was the correct term. You copy trunk into a branch
in case you need to update something. Once the release is done
you cut off the branch and stick a tag to it :-)
cheers,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 06/06/07, Roland Weber <os...@dubioso.net> wrote:
> sebb wrote:
> > s/branch/tag/g surely?
>
> Eh... CVS tag = SVN branch? Whatever, the things that are
No, CVS tag = SVN tag
> not trunk and from which you can get a named historic version
> (=revision?) of what used to be in trunk :-)
In SVN, there is no distinction between tags and branches (or indeed trunk).
They are all just directory names.
But the convention is to use
trunk
for mainline code;
branch/branch-name
for any parallel developments (which may one day get merged into trunk); and
tags/tagname
to identify a snapshot which does not change.
SVN does not prevent anyone from updating any of the directories,
whereas as I recall, CVS tags were not as easy to update once created.
So a release can be developed in a branch or the trunk; before the
release is finally built the current files should be copied to a
subdirectory of tags.
The tags subdirectory should not be updated once created.
> It's called "level" in CMVC, and I just don't want to spend
> my time on learning a separate vocabulary for every source
> repository system out there :-(
>
> cheers,
> Roland
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Roland Weber <os...@dubioso.net>.
sebb wrote:
> s/branch/tag/g surely?
Eh... CVS tag = SVN branch? Whatever, the things that are
not trunk and from which you can get a named historic version
(=revision?) of what used to be in trunk :-)
It's called "level" in CMVC, and I just don't want to spend
my time on learning a separate vocabulary for every source
repository system out there :-(
cheers,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 06/06/07, Roland Weber <os...@dubioso.net> wrote:
> Hi Thomas,
>
> >> If you changed the release files manually, you
> >> should commit those changes to SVN and give Sebastian some time to
> >> change his vote.
> >
> > We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
> > SVN. This is at least what I understood the release-then-vote-policy
> > means.
>
> The point of a SVN branch is to have an archived version of the
> exact files that go into the release. If you have to change a
> release after creating the branch, you should update the branch
> and re-build the release from scratch. This is the best way to
> make sure that releases can be reproduced.
s/branch/tag/g surely?
S///
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Roland Weber <os...@dubioso.net>.
Hi Thomas,
>> If you changed the release files manually, you
>> should commit those changes to SVN and give Sebastian some time to
>> change his vote.
>
> We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
> SVN. This is at least what I understood the release-then-vote-policy
> means.
The point of a SVN branch is to have an archived version of the
exact files that go into the release. If you have to change a
release after creating the branch, you should update the branch
and re-build the release from scratch. This is the best way to
make sure that releases can be reproduced.
cheers,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Rahul Akolkar <ra...@gmail.com>.
On 6/3/07, Martin van den Bemt <ml...@mvdb.net> wrote:
> Agreed. though that page probably needs a bit of a reality check.. The problem is when someone does
> a -1 with reasoning, people tend to stop voting until that vote is switched to a +1 and if that vote
> is switched to a +1 and there are enough votes, people that stopped voting will keep silent.
>
> Hope I make sense :)
>
<snip/>
Concretely, Thomas / Will -- In this particular scenario, I wouldn't
release if I were the RM until I was able to work this out with sebb.
YMMV.
-Rahul
> Mvgr,
> Martin
>
> Will Glass-Husain wrote:
> > Martin,
> >
> > Actually, that's not true. Releases cannot be vetoed by a -1. See
> > http://www.apache.org/foundation/voting.html
> >
> > If there's a majority approval and at least 3 +1 PMC votes, than it's up to
> > the release manager to decide whether or not to release. He can decide to
> > table the vote based on feedback, if so desired. (We had this issue in the
> > release of Velocity 1.5).
> >
> > WILL
> >
> >
> >
> > On 6/3/07, Martin van den Bemt <ml...@mvdb.net> wrote:
> >> Rony is a PMC member.. However the -1 of Sebb (which is binding and
> > blocking) is still there (unless
> >> I missed his +1)..
> >> Added Rony to the jakarta-pmc authorization file (thanx for spotting
> > this)..
> >>
> >> Mvgr,
> >> Martin
> >>
> >> Thomas Vandahl wrote:
> >> > Hi Roland,
> >> >
> >> > Roland Weber wrote:
> >> >> Hi Thomas,
> >> >>
> >> >>> I could not find any information about whether Rony Flatscher is a
> >> >>> member of the PMC
> >> >> In the committers-only SVN module is a file board/committee-info.txt
> >> >> which lists the PMCs of all Apache projects. It's (supposed to be ;-)
> >> >> the authoritative source. Rony Flatscher is listed there as PMC
> >> member.
> >> >
> >> > I came across some commit message regarding asf-authorization which
> >> > contained a list of members of the jakarta-pmc group and he was not
> >> > listed there. So I was unsure.
> >> >
> >> >> I'm not sure myself how Sebastian's -1 will be weighed here. I would
> >> >> have expected that the NOTICE and LICENSE files get fixed and he
> >> >> changes his vote. As by his last mail on the topic, the content in
> >> >> SVN did not get fixed. If you changed the release files manually, you
> >> >> should commit those changes to SVN and give Sebastian some time to
> >> >> change his vote.
> >> >
> >> > We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
> >> > SVN. This is at least what I understood the release-then-vote-policy
> >> > means. I have committed the latest changes and moved the tag, however.
> >> >
> >> > If Rony is a PMC member we have a result of 3 +1 votes, which should be
> >> > sufficient. However its up to the PMC to decide this.
> >> >
> >> > Bye, Thomas.
> >> >
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Martin van den Bemt <ml...@mvdb.net>.
Agreed. though that page probably needs a bit of a reality check.. The problem is when someone does
a -1 with reasoning, people tend to stop voting until that vote is switched to a +1 and if that vote
is switched to a +1 and there are enough votes, people that stopped voting will keep silent.
Hope I make sense :)
Mvgr,
Martin
Will Glass-Husain wrote:
> Martin,
>
> Actually, that's not true. Releases cannot be vetoed by a -1. See
> http://www.apache.org/foundation/voting.html
>
> If there's a majority approval and at least 3 +1 PMC votes, than it's up to
> the release manager to decide whether or not to release. He can decide to
> table the vote based on feedback, if so desired. (We had this issue in the
> release of Velocity 1.5).
>
> WILL
>
>
>
> On 6/3/07, Martin van den Bemt <ml...@mvdb.net> wrote:
>> Rony is a PMC member.. However the -1 of Sebb (which is binding and
> blocking) is still there (unless
>> I missed his +1)..
>> Added Rony to the jakarta-pmc authorization file (thanx for spotting
> this)..
>>
>> Mvgr,
>> Martin
>>
>> Thomas Vandahl wrote:
>> > Hi Roland,
>> >
>> > Roland Weber wrote:
>> >> Hi Thomas,
>> >>
>> >>> I could not find any information about whether Rony Flatscher is a
>> >>> member of the PMC
>> >> In the committers-only SVN module is a file board/committee-info.txt
>> >> which lists the PMCs of all Apache projects. It's (supposed to be ;-)
>> >> the authoritative source. Rony Flatscher is listed there as PMC
>> member.
>> >
>> > I came across some commit message regarding asf-authorization which
>> > contained a list of members of the jakarta-pmc group and he was not
>> > listed there. So I was unsure.
>> >
>> >> I'm not sure myself how Sebastian's -1 will be weighed here. I would
>> >> have expected that the NOTICE and LICENSE files get fixed and he
>> >> changes his vote. As by his last mail on the topic, the content in
>> >> SVN did not get fixed. If you changed the release files manually, you
>> >> should commit those changes to SVN and give Sebastian some time to
>> >> change his vote.
>> >
>> > We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
>> > SVN. This is at least what I understood the release-then-vote-policy
>> > means. I have committed the latest changes and moved the tag, however.
>> >
>> > If Rony is a PMC member we have a result of 3 +1 votes, which should be
>> > sufficient. However its up to the PMC to decide this.
>> >
>> > Bye, Thomas.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail: general-help@jakarta.apache.org
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: general-help@jakarta.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Will Glass-Husain <wg...@gmail.com>.
Martin,
Actually, that's not true. Releases cannot be vetoed by a -1. See
http://www.apache.org/foundation/voting.html
If there's a majority approval and at least 3 +1 PMC votes, than it's up to
the release manager to decide whether or not to release. He can decide to
table the vote based on feedback, if so desired. (We had this issue in the
release of Velocity 1.5).
WILL
On 6/3/07, Martin van den Bemt <ml...@mvdb.net> wrote:
> Rony is a PMC member.. However the -1 of Sebb (which is binding and
blocking) is still there (unless
> I missed his +1)..
> Added Rony to the jakarta-pmc authorization file (thanx for spotting
this)..
>
> Mvgr,
> Martin
>
> Thomas Vandahl wrote:
> > Hi Roland,
> >
> > Roland Weber wrote:
> >> Hi Thomas,
> >>
> >>> I could not find any information about whether Rony Flatscher is a
> >>> member of the PMC
> >> In the committers-only SVN module is a file board/committee-info.txt
> >> which lists the PMCs of all Apache projects. It's (supposed to be ;-)
> >> the authoritative source. Rony Flatscher is listed there as PMC member.
> >
> > I came across some commit message regarding asf-authorization which
> > contained a list of members of the jakarta-pmc group and he was not
> > listed there. So I was unsure.
> >
> >> I'm not sure myself how Sebastian's -1 will be weighed here. I would
> >> have expected that the NOTICE and LICENSE files get fixed and he
> >> changes his vote. As by his last mail on the topic, the content in
> >> SVN did not get fixed. If you changed the release files manually, you
> >> should commit those changes to SVN and give Sebastian some time to
> >> change his vote.
> >
> > We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
> > SVN. This is at least what I understood the release-then-vote-policy
> > means. I have committed the latest changes and moved the tag, however.
> >
> > If Rony is a PMC member we have a result of 3 +1 votes, which should be
> > sufficient. However its up to the PMC to decide this.
> >
> > Bye, Thomas.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: general-help@jakarta.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
Re: Result: [VOTE] Release JCS 1.3
Posted by Martin van den Bemt <ml...@mvdb.net>.
Rony is a PMC member.. However the -1 of Sebb (which is binding and blocking) is still there (unless
I missed his +1)..
Added Rony to the jakarta-pmc authorization file (thanx for spotting this)..
Mvgr,
Martin
Thomas Vandahl wrote:
> Hi Roland,
>
> Roland Weber wrote:
>> Hi Thomas,
>>
>>> I could not find any information about whether Rony Flatscher is a
>>> member of the PMC
>> In the committers-only SVN module is a file board/committee-info.txt
>> which lists the PMCs of all Apache projects. It's (supposed to be ;-)
>> the authoritative source. Rony Flatscher is listed there as PMC member.
>
> I came across some commit message regarding asf-authorization which
> contained a list of members of the jakarta-pmc group and he was not
> listed there. So I was unsure.
>
>> I'm not sure myself how Sebastian's -1 will be weighed here. I would
>> have expected that the NOTICE and LICENSE files get fixed and he
>> changes his vote. As by his last mail on the topic, the content in
>> SVN did not get fixed. If you changed the release files manually, you
>> should commit those changes to SVN and give Sebastian some time to
>> change his vote.
>
> We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
> SVN. This is at least what I understood the release-then-vote-policy
> means. I have committed the latest changes and moved the tag, however.
>
> If Rony is a PMC member we have a result of 3 +1 votes, which should be
> sufficient. However its up to the PMC to decide this.
>
> Bye, Thomas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Hi Roland,
Roland Weber wrote:
> Hi Thomas,
>
>> I could not find any information about whether Rony Flatscher is a
>> member of the PMC
>
> In the committers-only SVN module is a file board/committee-info.txt
> which lists the PMCs of all Apache projects. It's (supposed to be ;-)
> the authoritative source. Rony Flatscher is listed there as PMC member.
I came across some commit message regarding asf-authorization which
contained a list of members of the jakarta-pmc group and he was not
listed there. So I was unsure.
> I'm not sure myself how Sebastian's -1 will be weighed here. I would
> have expected that the NOTICE and LICENSE files get fixed and he
> changes his vote. As by his last mail on the topic, the content in
> SVN did not get fixed. If you changed the release files manually, you
> should commit those changes to SVN and give Sebastian some time to
> change his vote.
We were voting on the artifacts on people.apache.org/~tv/jcs/, not on
SVN. This is at least what I understood the release-then-vote-policy
means. I have committed the latest changes and moved the tag, however.
If Rony is a PMC member we have a result of 3 +1 votes, which should be
sufficient. However its up to the PMC to decide this.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: Result: [VOTE] Release JCS 1.3
Posted by Roland Weber <os...@dubioso.net>.
Hi Thomas,
> I could not find any information about whether Rony Flatscher is a
> member of the PMC
In the committers-only SVN module is a file board/committee-info.txt
which lists the PMCs of all Apache projects. It's (supposed to be ;-)
the authoritative source. Rony Flatscher is listed there as PMC member.
I'm not sure myself how Sebastian's -1 will be weighed here. I would
have expected that the NOTICE and LICENSE files get fixed and he
changes his vote. As by his last mail on the topic, the content in
SVN did not get fixed. If you changed the release files manually, you
should commit those changes to SVN and give Sebastian some time to
change his vote.
Btw, he asked on legal-discuss about the correct usage of these
files, but I see little point in delaying the release until that
question has been answered.
cheers,
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Result: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Vandahl wrote:
> Now, shall we release JCS as it is published there?
>
> [ ] +1 Yes, JCS 1.3 should be released
> [ ] 0 I do not care
> [ ] -1 No (give reasons)
Voting has closed. Here are the results:
+1 votes:
Hanson Char <ha...@gmail.com>
Thomas Vandahl <tv...@apache.org>
* Henning Schmiedehausen <hp...@intermeta.de>
* Aaron Smuts <as...@yahoo.com>
* Scott Eade <se...@backstagetech.com.au>
Rony G. Flatscher <Ro...@wu-wien.ac.at>
0 votes:
none
-1 votes:
* sebbaz@gmail.com
(* denotes binding votes of PMC members)
I could not find any information about whether Rony Flatscher is a
member of the PMC, so would someone with the necessary insight please
decide if this vote passed or not.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
sebb wrote:
> But you _are_ still a committer...
Yes, but then, everybody else in Jakarta is also potentially a committer
for JCS and we would not want to list them all.
By, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 26/05/07, Scott Eade <se...@backstagetech.com.au> wrote:
> sebb wrote:
> > On 26/05/07, Thomas Vandahl <tv...@apache.org> wrote:
> >> sebb wrote:
> >> > Project Team: both tv and jvanzyl are committers
> >> Actually my contributions are very small, so I'm fine with the
> >> contributor status.
> >
> > But you _are_ still a committer...
> Surely it is up to Thomas to decide how he wants to be listed?
> > Also what about jvanzyl?
> So as a committer Jason is welcome to make this change. I don't see
> this as the responsibility of the release manager.
>
OK, fine.
The page does not entirely agree with the SVN history; it was not
clear if that was deliberate or accidental.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Scott Eade <se...@backstagetech.com.au>.
sebb wrote:
> On 26/05/07, Thomas Vandahl <tv...@apache.org> wrote:
>> sebb wrote:
>> > Project Team: both tv and jvanzyl are committers
>> Actually my contributions are very small, so I'm fine with the
>> contributor status.
>
> But you _are_ still a committer...
Surely it is up to Thomas to decide how he wants to be listed?
> Also what about jvanzyl?
So as a committer Jason is welcome to make this change. I don't see
this as the responsibility of the release manager.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 26/05/07, Thomas Vandahl <tv...@apache.org> wrote:
> sebb wrote:
> > Sorry, but: -1
> >
> > There should be NOTICE files in all the archives (jar, zip etc).
> > The NOTICE file (found in SVN) needs to refer to Xerox - see
> > jcs-1.3\src\aspect\Trace.aj
> >
> > No KEYS file to check the signatures - and could not find it in SVN.
> >
> > Sourcefiles:
> > There should probably be AL2.0 headers in the .aj files (apart from
> > Trace.aj)
>
> One should not do those things in a hurry. Sorry for this. I will
> rebuild the stuff and upload it again.
>
> >
> > -0 Other problems:
> >
> > Website:
> > The Changes report refers to CVS - this should really be SVN
> Changed.
>
> > The JCoverage report should really open in a new window, as is done
> > for Javadocs etc.
> This is standard Maven stuff. How would you change that?
Sorry, no idea.
> > The Checkstyle report is in German, ideally it should be in English.
> Fixed.
>
> > Project Team: both tv and jvanzyl are committers
> Actually my contributions are very small, so I'm fine with the
> contributor status.
But you _are_ still a committer...
Also what about jvanzyl?
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
sebb wrote:
> Sorry, but: -1
>
> There should be NOTICE files in all the archives (jar, zip etc).
> The NOTICE file (found in SVN) needs to refer to Xerox - see
> jcs-1.3\src\aspect\Trace.aj
>
> No KEYS file to check the signatures - and could not find it in SVN.
>
> Sourcefiles:
> There should probably be AL2.0 headers in the .aj files (apart from
> Trace.aj)
One should not do those things in a hurry. Sorry for this. I will
rebuild the stuff and upload it again.
>
> -0 Other problems:
>
> Website:
> The Changes report refers to CVS - this should really be SVN
Changed.
> The JCoverage report should really open in a new window, as is done
> for Javadocs etc.
This is standard Maven stuff. How would you change that?
> The Checkstyle report is in German, ideally it should be in English.
Fixed.
> Project Team: both tv and jvanzyl are committers
Actually my contributions are very small, so I'm fine with the
contributor status.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 05/06/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> Could you create an example on how you would consider the structure and
> content as "acceptable" so that we can understand what you want to have?
>
> Thanks
> Henning
I thought I already had done so:
On 27/05/07, sebb <se...@gmail.com> wrote:
> On 27/05/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> > The license under which the code gets licensed to our end users is in
> > LICENSE.txt.
> >
> > Copyright notices and optional third-party licenses under which the code
> > got licensed to us is in NOTICE.
>
> Are you sure?
>
> That does not seem to agree with the sample NOTICE file:
>
> http://www.apache.org/licenses/example-NOTICE.txt
>
> Nor does it seem to agree with the way that httpd use the NOTICE and
> LICENSE files:
>
> http://svn.apache.org/viewvc/httpd/httpd/trunk/
>
> As I understand it, the NOTICE file is for attributions.
> The LICENSE file is for licenses.
> These may either be included inline, or in separate files referenced
> from the main LICENSE file.
>
S///
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Could you create an example on how you would consider the structure and
content as "acceptable" so that we can understand what you want to have?
Thanks
Henning
sebb schrieb:
> On 04/06/07, Thomas Vandahl <tv...@apache.org> wrote:
>> sebb wrote:
>> > Sorry for the delay in responding.
>> >
>> > The NOTICE file is much clearer, and the Xerox license is identified,
>> > so I am withdrawing my -1.
>> >
>> > When the rules have been clarified, the next release can implement any
>> > changes if necessary.
>> >
>> > Sebastian
>>
>> Thanks, I will clarify the result now, based on your +1 I suppose?
>
> Sorry, I should have been clearer.
>
> I have withdrawn the -1.
> That does not mean I am now totally in favour.
>
> I'm not convinced that the files are quite right yet, so I am now
> abstaining.
>
>> Bye, Thomas.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: general-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 04/06/07, Thomas Vandahl <tv...@apache.org> wrote:
> sebb wrote:
> > Sorry for the delay in responding.
> >
> > The NOTICE file is much clearer, and the Xerox license is identified,
> > so I am withdrawing my -1.
> >
> > When the rules have been clarified, the next release can implement any
> > changes if necessary.
> >
> > Sebastian
>
> Thanks, I will clarify the result now, based on your +1 I suppose?
Sorry, I should have been clearer.
I have withdrawn the -1.
That does not mean I am now totally in favour.
I'm not convinced that the files are quite right yet, so I am now abstaining.
> Bye, Thomas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
sebb wrote:
> Sorry for the delay in responding.
>
> The NOTICE file is much clearer, and the Xerox license is identified,
> so I am withdrawing my -1.
>
> When the rules have been clarified, the next release can implement any
> changes if necessary.
>
> Sebastian
Thanks, I will clarify the result now, based on your +1 I suppose?
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 04/06/07, Thomas Vandahl <tv...@apache.org> wrote:
> Hi Sebastian,
Hi
> sebb wrote:
> > However:
> >
> > http://apache.org/dev/apply-license.html
> >
> > says much the same, and seems to be policy.
>
> As you can see from the SVN tag JCS_1_3 and the artifacts at my site,
> your concerns have been addressed and the license files have been fixed.
>
> I would like to ask you to be so kind as to re-vote on the subject,
> based on the new status.
>
Sorry for the delay in responding.
The NOTICE file is much clearer, and the Xerox license is identified,
so I am withdrawing my -1.
When the rules have been clarified, the next release can implement any
changes if necessary.
Sebastian
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Martin van den Bemt wrote:
> If you vote again your vote is binding too :)
Next time. Thanks again for voting me in.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Martin van den Bemt <ml...@mvdb.net>.
If you vote again your vote is binding too :)
Mvgr,
Martin
Thomas Vandahl wrote:
> Hi Sebastian,
>
> sebb wrote:
>> However:
>>
>> http://apache.org/dev/apply-license.html
>>
>> says much the same, and seems to be policy.
>
> As you can see from the SVN tag JCS_1_3 and the artifacts at my site,
> your concerns have been addressed and the license files have been fixed.
>
> I would like to ask you to be so kind as to re-vote on the subject,
> based on the new status.
>
> Regards, Thomas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Hi Sebastian,
sebb wrote:
> However:
>
> http://apache.org/dev/apply-license.html
>
> says much the same, and seems to be policy.
As you can see from the SVN tag JCS_1_3 and the artifacts at my site,
your concerns have been addressed and the license files have been fixed.
I would like to ask you to be so kind as to re-vote on the subject,
based on the new status.
Regards, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 30/05/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> Yep, I know this.
>
> Status
>
> Version: 0.52
>
> Effective Date. N/A (proposed)
>
> ==> non binding.
However:
http://apache.org/dev/apply-license.html
says much the same, and seems to be policy.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Yep, I know this.
Status
Version: 0.52
Effective Date. N/A (proposed)
==> non binding.
If it were in effect, then yes, the paragraph
--- cut ---
* Reciprocity
Required by some Components: Some included third-party works are
licensed under terms that require distribution of derivative works
to be made available under the same license as the original work.
See the Apache product's LICENSE file to find the applicable
third-party licenses.
--- cut ---
would make it clear.
But it is no official Apache policy. And in lieu of policy, none of us
can say that the way Thomas compiled LICENSE and NOTICE is wrong.
Because there is no official policy.
*Sigh*, it seems that I finally have to subscribe to legal-discuss. :-(
Best regards
Henning
On Wed, 2007-05-30 at 12:35 -0700, Henri Yandell wrote:
> On 5/30/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> > On Wed, 2007-05-30 at 19:00 +0100, sebb wrote:
> > > The NOTICE file is not supposed to contain any licenses.
> >
> > What makes you think so? I am still a bit stumped that you so strongly
> > insist on this. Is there any reference (besides the cited httpd project)
> > to that?
>
> For a long time I thought LICENSE was for the license only and
> everything else went in NOTICE. Discussions with Cliff, and I'm pretty
> sure watching other discussions on legal-discuss, made it clear that
> license-things go in LICENSE, and copyright/ip things go in NOTICE.
>
> Look at the two places in http://people.apache.org/~cliffs/3party.html
> where it mentions LICENSE, both imply that the LICENSE file is the
> only place to find licensing terms.
>
> Hen
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux, |gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henri Yandell <fl...@gmail.com>.
On 5/30/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> On Wed, 2007-05-30 at 19:00 +0100, sebb wrote:
> > The NOTICE file is not supposed to contain any licenses.
>
> What makes you think so? I am still a bit stumped that you so strongly
> insist on this. Is there any reference (besides the cited httpd project)
> to that?
For a long time I thought LICENSE was for the license only and
everything else went in NOTICE. Discussions with Cliff, and I'm pretty
sure watching other discussions on legal-discuss, made it clear that
license-things go in LICENSE, and copyright/ip things go in NOTICE.
Look at the two places in http://people.apache.org/~cliffs/3party.html
where it mentions LICENSE, both imply that the LICENSE file is the
only place to find licensing terms.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
On Wed, 2007-05-30 at 19:00 +0100, sebb wrote:
> The NOTICE file is not supposed to contain any licenses.
What makes you think so? I am still a bit stumped that you so strongly
insist on this. Is there any reference (besides the cited httpd project)
to that?
Best regards
Henning
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux, |gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 30/05/07, Thomas Vandahl <tv...@apache.org> wrote:
> sebb wrote:
> > The NOTICE file is not supposed to contain any licenses.
> I beg to differ, but I will not go into this again.
>
> > I suggest you remove the Xerox license header from it, and add it to
> > the LICENSE file, with the appropriate introduction.
> The LICENSE.txt file is supposed to contain the ASL 2.0 and nothing
> else.
I don't think that is correct.
The reference to copying the AL 2.0 file to the LICENSE file in
http://apache.org/dev/apply-license.html#new
relates to creating the initial LICENSE file - it does not say that
the LICENSE file cannot contain anything else.
> I created another file LICENSE.xerox and refer to it from the
> NOTICE file.
It needs either to be referenced in or actually in the LICENSE file.
> > Sorry to keep going on about this, but there's only one other file to edit.
> Actually, it's more than that.
Not necessarily.
It's your choice as to whether to append the Xerox license to the
LICENSE file or put it in a separate file and edit LICENSE to refer to
it.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by "Rony G. Flatscher" <Ro...@wu-wien.ac.at>.
+1
---rony
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Can you BTW also remove the empty <aspectSourceDirectory/> from the
Maven 1 POM. This is what stops maven 1.1 beta 3 from building the
distribution.
Good work, folks. +1
Best regards
Henning
Scott Eade schrieb:
> Thomas Vandahl wrote:
>> Thomas Vandahl wrote:
>>
>>> Actually, it's more than that. But so be it. I will update the files on
>>> my site and kindly ask for a re-vote.
>>>
>>
>> Done. I chose the separate LICENSE file. The maven2-POM is also part of
>> the distribution.
>>
> The maven2 pom is what I was holding out for and I believe the license
> issue has been dealt with correctly. So...
>
> +1 for the release from me.
>
> Scott
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Can you BTW also remove the empty <aspectSourceDirectory/> from the
Maven 1 POM. This is what stops maven 1.1 beta 3 from building the
distribution.
Good work, folks. +1
Best regards
Henning
Scott Eade schrieb:
> Thomas Vandahl wrote:
>> Thomas Vandahl wrote:
>>
>>> Actually, it's more than that. But so be it. I will update the files on
>>> my site and kindly ask for a re-vote.
>>>
>>
>> Done. I chose the separate LICENSE file. The maven2-POM is also part of
>> the distribution.
>>
> The maven2 pom is what I was holding out for and I believe the license
> issue has been dealt with correctly. So...
>
> +1 for the release from me.
>
> Scott
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Scott Eade <se...@backstagetech.com.au>.
Thomas Vandahl wrote:
> Thomas Vandahl wrote:
>
>> Actually, it's more than that. But so be it. I will update the files on
>> my site and kindly ask for a re-vote.
>>
>
> Done. I chose the separate LICENSE file. The maven2-POM is also part of
> the distribution.
>
The maven2 pom is what I was holding out for and I believe the license
issue has been dealt with correctly. So...
+1 for the release from me.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Scott Eade <se...@backstagetech.com.au>.
Thomas Vandahl wrote:
> Thomas Vandahl wrote:
>
>> Actually, it's more than that. But so be it. I will update the files on
>> my site and kindly ask for a re-vote.
>>
>
> Done. I chose the separate LICENSE file. The maven2-POM is also part of
> the distribution.
>
The maven2 pom is what I was holding out for and I believe the license
issue has been dealt with correctly. So...
+1 for the release from me.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Vandahl wrote:
> Actually, it's more than that. But so be it. I will update the files on
> my site and kindly ask for a re-vote.
Done. I chose the separate LICENSE file. The maven2-POM is also part of
the distribution.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
sebb wrote:
> The NOTICE file is not supposed to contain any licenses.
I beg to differ, but I will not go into this again.
> I suggest you remove the Xerox license header from it, and add it to
> the LICENSE file, with the appropriate introduction.
The LICENSE.txt file is supposed to contain the ASL 2.0 and nothing
else. I created another file LICENSE.xerox and refer to it from the
NOTICE file.
> Sorry to keep going on about this, but there's only one other file to edit.
Actually, it's more than that. But so be it. I will update the files on
my site and kindly ask for a re-vote.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 30/05/07, Thomas Vandahl <tv...@apache.org> wrote:
> sebb wrote:
> > I find the current NOTICE rather misleading - it looks as though the
> > whole of JCS is licensed under a Xerox licence.
> >
> > I think it's therefore important to fix this.
>
> From re-reading the NOTICE file, I agree with you. My proposal to solve
> this is the following:
>
> ---8<---
> Apache Jakarta JCS
> Copyright 2001-2007 The Apache Software Foundation.
> Portions Copyright (c) Xerox Corporation 1998-2001.
>
> This product includes software developed at
> The Apache Software Foundation (http://www.apache.org/).
>
> This product includes software developed at Xerox Corporation which has
> been published under the following license:
> ---
> Copyright (c) Xerox Corporation 1998-2001. All rights reserved.
>
> Use and copying of this software and preparation of derivative works
> based upon this software are permitted. Any distribution of this
> software or derivative works must comply with all applicable United
> States export control laws.
>
> This software is made available AS IS, and Xerox Corporation makes no
> warranty about the software, its performance or its conformity to any
> specification.
> ---
>
> ---8<---
>
> Could we agree on this version?
>
The NOTICE file is not supposed to contain any licenses.
I suggest you remove the Xerox license header from it, and add it to
the LICENSE file, with the appropriate introduction.
Sorry to keep going on about this, but there's only one other file to edit.
> Bye, Thomas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
sebb wrote:
> I find the current NOTICE rather misleading - it looks as though the
> whole of JCS is licensed under a Xerox licence.
>
> I think it's therefore important to fix this.
>From re-reading the NOTICE file, I agree with you. My proposal to solve
this is the following:
---8<---
Apache Jakarta JCS
Copyright 2001-2007 The Apache Software Foundation.
Portions Copyright (c) Xerox Corporation 1998-2001.
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
This product includes software developed at Xerox Corporation which has
been published under the following license:
---
Copyright (c) Xerox Corporation 1998-2001. All rights reserved.
Use and copying of this software and preparation of derivative works
based upon this software are permitted. Any distribution of this
software or derivative works must comply with all applicable United
States export control laws.
This software is made available AS IS, and Xerox Corporation makes no
warranty about the software, its performance or its conformity to any
specification.
---
---8<---
Could we agree on this version?
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 29/05/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> Hi,
>
> uhm, this is as ambiguous as before. Do you consider third-party license
> a notice (the foo library is distributed under the foo license as shown
> here) or a license in its own right and you would put in into LICENSE.
>
> According to http://apache.org/dev/apply-license.html#new, the LICENSE
> file is a copy of http://www.apache.org/licenses/LICENSE-2.0.txt
>
> And is that *really* important?
I find the current NOTICE rather misleading - it looks as though the
whole of JCS is licensed under a Xerox licence.
I think it's therefore important to fix this.
> Best regards
> Henning
>
>
> Martin van den Bemt schrieb:
> > Full license text should go in LICENSE and attributions and notices in NOTICE..
> >
> > Mvgr,
> > Martin
> >
> > Henning Schmiedehausen wrote:
> >> Well, I understand it differently and Thomas (probably looking at other
> >> projects) did this too:
> >>
> >> - LICENSE.txt contains the terms under which the software is licensed.
> >> This is Apache License 2.0
> >>
> >> - NOTICE contains attributions to included code and the licenses that
> >> it is included under. Some projects choose to reference "foo.LICENSE"
> >> files for "foo". Some choose to put the appropriate licensess into
> >> the NOTICE file. Yet others put these (third party) licenses into the
> >> LICENSE file.
> >>
> >> All of the above are ok IMHO. I personally have a preference for the
> >> first variant. httpd uses the second. I think FOP uses the third.
> >>
> >> Best regards
> >> Henning
> >>
> >> On Mon, 2007-05-28 at 15:24 -0700, Henri Yandell wrote:
> >>> On 5/27/07, sebb <se...@gmail.com> wrote:
> >>>> On 27/05/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> >>>>> The license under which the code gets licensed to our end users is in
> >>>>> LICENSE.txt.
> >>>>>
> >>>>> Copyright notices and optional third-party licenses under which the code
> >>>>> got licensed to us is in NOTICE.
> >>>> Are you sure?
> >>>>
> >>>> That does not seem to agree with the sample NOTICE file:
> >>>>
> >>>> http://www.apache.org/licenses/example-NOTICE.txt
> >>>>
> >>>> Nor does it seem to agree with the way that httpd use the NOTICE and
> >>>> LICENSE files:
> >>>>
> >>>> http://svn.apache.org/viewvc/httpd/httpd/trunk/
> >>>>
> >>>> As I understand it, the NOTICE file is for attributions.
> >>>> The LICENSE file is for licenses.
> >>>> These may either be included inline, or in separate files referenced
> >>>> from the main LICENSE file.
> >>> That's how I understand it too.
> >>>
> >>> Hen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: general-help@jakarta.apache.org
> >
>
> --
> Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
> 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
> Open Source Consulting, Development, Design | Velocity - Turbine
>
> "Save the cheerleader. Save the world."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Hi,
uhm, this is as ambiguous as before. Do you consider third-party license
a notice (the foo library is distributed under the foo license as shown
here) or a license in its own right and you would put in into LICENSE.
According to http://apache.org/dev/apply-license.html#new, the LICENSE
file is a copy of http://www.apache.org/licenses/LICENSE-2.0.txt
And is that *really* important?
Best regards
Henning
Martin van den Bemt schrieb:
> Full license text should go in LICENSE and attributions and notices in NOTICE..
>
> Mvgr,
> Martin
>
> Henning Schmiedehausen wrote:
>> Well, I understand it differently and Thomas (probably looking at other
>> projects) did this too:
>>
>> - LICENSE.txt contains the terms under which the software is licensed.
>> This is Apache License 2.0
>>
>> - NOTICE contains attributions to included code and the licenses that
>> it is included under. Some projects choose to reference "foo.LICENSE"
>> files for "foo". Some choose to put the appropriate licensess into
>> the NOTICE file. Yet others put these (third party) licenses into the
>> LICENSE file.
>>
>> All of the above are ok IMHO. I personally have a preference for the
>> first variant. httpd uses the second. I think FOP uses the third.
>>
>> Best regards
>> Henning
>>
>> On Mon, 2007-05-28 at 15:24 -0700, Henri Yandell wrote:
>>> On 5/27/07, sebb <se...@gmail.com> wrote:
>>>> On 27/05/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
>>>>> The license under which the code gets licensed to our end users is in
>>>>> LICENSE.txt.
>>>>>
>>>>> Copyright notices and optional third-party licenses under which the code
>>>>> got licensed to us is in NOTICE.
>>>> Are you sure?
>>>>
>>>> That does not seem to agree with the sample NOTICE file:
>>>>
>>>> http://www.apache.org/licenses/example-NOTICE.txt
>>>>
>>>> Nor does it seem to agree with the way that httpd use the NOTICE and
>>>> LICENSE files:
>>>>
>>>> http://svn.apache.org/viewvc/httpd/httpd/trunk/
>>>>
>>>> As I understand it, the NOTICE file is for attributions.
>>>> The LICENSE file is for licenses.
>>>> These may either be included inline, or in separate files referenced
>>>> from the main LICENSE file.
>>> That's how I understand it too.
>>>
>>> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Martin van den Bemt <ml...@mvdb.net>.
Full license text should go in LICENSE and attributions and notices in NOTICE..
Mvgr,
Martin
Henning Schmiedehausen wrote:
> Well, I understand it differently and Thomas (probably looking at other
> projects) did this too:
>
> - LICENSE.txt contains the terms under which the software is licensed.
> This is Apache License 2.0
>
> - NOTICE contains attributions to included code and the licenses that
> it is included under. Some projects choose to reference "foo.LICENSE"
> files for "foo". Some choose to put the appropriate licensess into
> the NOTICE file. Yet others put these (third party) licenses into the
> LICENSE file.
>
> All of the above are ok IMHO. I personally have a preference for the
> first variant. httpd uses the second. I think FOP uses the third.
>
> Best regards
> Henning
>
> On Mon, 2007-05-28 at 15:24 -0700, Henri Yandell wrote:
>> On 5/27/07, sebb <se...@gmail.com> wrote:
>>> On 27/05/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
>>>> The license under which the code gets licensed to our end users is in
>>>> LICENSE.txt.
>>>>
>>>> Copyright notices and optional third-party licenses under which the code
>>>> got licensed to us is in NOTICE.
>>> Are you sure?
>>>
>>> That does not seem to agree with the sample NOTICE file:
>>>
>>> http://www.apache.org/licenses/example-NOTICE.txt
>>>
>>> Nor does it seem to agree with the way that httpd use the NOTICE and
>>> LICENSE files:
>>>
>>> http://svn.apache.org/viewvc/httpd/httpd/trunk/
>>>
>>> As I understand it, the NOTICE file is for attributions.
>>> The LICENSE file is for licenses.
>>> These may either be included inline, or in separate files referenced
>>> from the main LICENSE file.
>> That's how I understand it too.
>>
>> Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Well, I understand it differently and Thomas (probably looking at other
projects) did this too:
- LICENSE.txt contains the terms under which the software is licensed.
This is Apache License 2.0
- NOTICE contains attributions to included code and the licenses that
it is included under. Some projects choose to reference "foo.LICENSE"
files for "foo". Some choose to put the appropriate licensess into
the NOTICE file. Yet others put these (third party) licenses into the
LICENSE file.
All of the above are ok IMHO. I personally have a preference for the
first variant. httpd uses the second. I think FOP uses the third.
Best regards
Henning
On Mon, 2007-05-28 at 15:24 -0700, Henri Yandell wrote:
> On 5/27/07, sebb <se...@gmail.com> wrote:
> > On 27/05/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> > > The license under which the code gets licensed to our end users is in
> > > LICENSE.txt.
> > >
> > > Copyright notices and optional third-party licenses under which the code
> > > got licensed to us is in NOTICE.
> >
> > Are you sure?
> >
> > That does not seem to agree with the sample NOTICE file:
> >
> > http://www.apache.org/licenses/example-NOTICE.txt
> >
> > Nor does it seem to agree with the way that httpd use the NOTICE and
> > LICENSE files:
> >
> > http://svn.apache.org/viewvc/httpd/httpd/trunk/
> >
> > As I understand it, the NOTICE file is for attributions.
> > The LICENSE file is for licenses.
> > These may either be included inline, or in separate files referenced
> > from the main LICENSE file.
>
> That's how I understand it too.
>
> Hen
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux, |gls
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person |eau
Open Source Consulting, Development, Design | Velocity - Turbine guy |rwc
|m k
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350 |a s
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen |n
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henri Yandell <fl...@gmail.com>.
On 5/27/07, sebb <se...@gmail.com> wrote:
> On 27/05/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> > The license under which the code gets licensed to our end users is in
> > LICENSE.txt.
> >
> > Copyright notices and optional third-party licenses under which the code
> > got licensed to us is in NOTICE.
>
> Are you sure?
>
> That does not seem to agree with the sample NOTICE file:
>
> http://www.apache.org/licenses/example-NOTICE.txt
>
> Nor does it seem to agree with the way that httpd use the NOTICE and
> LICENSE files:
>
> http://svn.apache.org/viewvc/httpd/httpd/trunk/
>
> As I understand it, the NOTICE file is for attributions.
> The LICENSE file is for licenses.
> These may either be included inline, or in separate files referenced
> from the main LICENSE file.
That's how I understand it too.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 27/05/07, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> The license under which the code gets licensed to our end users is in
> LICENSE.txt.
>
> Copyright notices and optional third-party licenses under which the code
> got licensed to us is in NOTICE.
Are you sure?
That does not seem to agree with the sample NOTICE file:
http://www.apache.org/licenses/example-NOTICE.txt
Nor does it seem to agree with the way that httpd use the NOTICE and
LICENSE files:
http://svn.apache.org/viewvc/httpd/httpd/trunk/
As I understand it, the NOTICE file is for attributions.
The LICENSE file is for licenses.
These may either be included inline, or in separate files referenced
from the main LICENSE file.
S///
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
The license under which the code gets licensed to our end users is in
LICENSE.txt.
Copyright notices and optional third-party licenses under which the code
got licensed to us is in NOTICE.
Thomas did the right thing.
Best regards
Henning
sebb schrieb:
> On 27/05/07, Thomas Vandahl <tv...@apache.org> wrote:
>> sebb wrote:
>> > I don't think so. The NOTICE is not supposed to contain the license.
>>
>> It doesn't. It contains what I understand as "license header" of that
>> one Xerox file and the associated copyright notice.
>>
>
> Sorry to keep going on about this, but I think it is important.
>
> At the moment the Xerox license header makes it look as though the
> software is being released under a Xerox license.
>
> That is confusing.
>
> If you don't want to add the Xerox header to LICENSE.txt, it can be
> put in a separate file which is referenced from NOTICE.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 27/05/07, Thomas Vandahl <tv...@apache.org> wrote:
> sebb wrote:
> > I don't think so. The NOTICE is not supposed to contain the license.
>
> It doesn't. It contains what I understand as "license header" of that
> one Xerox file and the associated copyright notice.
>
Sorry to keep going on about this, but I think it is important.
At the moment the Xerox license header makes it look as though the
software is being released under a Xerox license.
That is confusing.
If you don't want to add the Xerox header to LICENSE.txt, it can be
put in a separate file which is referenced from NOTICE.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
sebb wrote:
> I don't think so. The NOTICE is not supposed to contain the license.
It doesn't. It contains what I understand as "license header" of that
one Xerox file and the associated copyright notice.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
On 26/05/07, Thomas Vandahl <tv...@apache.org> wrote:
> sebb wrote:
> > Sorry, but: -1
> >
> > There should be NOTICE files in all the archives (jar, zip etc).
> > The NOTICE file (found in SVN) needs to refer to Xerox - see
> > jcs-1.3\src\aspect\Trace.aj
> >
> > No KEYS file to check the signatures - and could not find it in SVN.
> >
> > Sourcefiles:
> > There should probably be AL2.0 headers in the .aj files (apart from
> > Trace.aj)
> >
> > -0 Other problems:
> >
> > Website:
> > The Changes report refers to CVS - this should really be SVN
> > The JCoverage report should really open in a new window, as is done
> > for Javadocs etc.
> > The Checkstyle report is in German, ideally it should be in English.
>
> All complaints have been fixed. The new versions are online. I beg for
> pardon again. I uploaded a copy of the KEYS file to both, the jar and
> the dist directory for your convenience.
>
> I'm not sure how to handle the Xerox copyright stuff. I included the
> whole text inside the NOTICE file for now. Don't know if that is
> appropriate.
I don't think so. The NOTICE is not supposed to contain the license.
See:
http://svn.apache.org/viewvc/httpd/httpd/trunk/
for an example.
> Would you please be so kind as to review again and vote again.
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
sebb wrote:
> Sorry, but: -1
>
> There should be NOTICE files in all the archives (jar, zip etc).
> The NOTICE file (found in SVN) needs to refer to Xerox - see
> jcs-1.3\src\aspect\Trace.aj
>
> No KEYS file to check the signatures - and could not find it in SVN.
>
> Sourcefiles:
> There should probably be AL2.0 headers in the .aj files (apart from
> Trace.aj)
>
> -0 Other problems:
>
> Website:
> The Changes report refers to CVS - this should really be SVN
> The JCoverage report should really open in a new window, as is done
> for Javadocs etc.
> The Checkstyle report is in German, ideally it should be in English.
All complaints have been fixed. The new versions are online. I beg for
pardon again. I uploaded a copy of the KEYS file to both, the jar and
the dist directory for your convenience.
I'm not sure how to handle the Xerox copyright stuff. I included the
whole text inside the NOTICE file for now. Don't know if that is
appropriate.
Would you please be so kind as to review again and vote again.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by sebb <se...@gmail.com>.
Sorry, but: -1
There should be NOTICE files in all the archives (jar, zip etc).
The NOTICE file (found in SVN) needs to refer to Xerox - see
jcs-1.3\src\aspect\Trace.aj
No KEYS file to check the signatures - and could not find it in SVN.
Sourcefiles:
There should probably be AL2.0 headers in the .aj files (apart from Trace.aj)
-0 Other problems:
Website:
The Changes report refers to CVS - this should really be SVN
The JCoverage report should really open in a new window, as is done
for Javadocs etc.
The Checkstyle report is in German, ideally it should be in English.
Project Team: both tv and jvanzyl are committers
Sebb AT AO
On 26/05/07, Thomas Vandahl <tv...@apache.org> wrote:
> Hi folks,
>
> After much discussion on the JCS developer list, the first official
> release of JCS (version 1.3) after leaving the Turbine project is ready
> to vote on.
>
> You can find the created artifacts here:
> site: http://people.apache.org/~tv/jcs/
> jars: http://people.apache.org/~tv/jcs/jar/
> dist: http://people.apache.org/~tv/jcs/dist/
>
> Now, shall we release JCS as it is published there?
>
> [ ] +1 Yes, JCS 1.3 should be released
> [ ] 0 I do not care
> [ ] -1 No (give reasons)
>
> Voting is subject to the rules described in
> http://jakarta.apache.org/site/management.html
>
> The deadline is Sat, June 1 2007, 12:00 CET
>
> Note that the Jakarta PMC has the final word on whether the release is
> published
> or not.
>
> Bye, Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Scott Eade <se...@backstagetech.com.au>.
Thomas Vandahl wrote:
> Scott Eade wrote:
>
>> Sorry to be a pain Thomas, but I'm afraid the pom that is included jar
>> directory is no good. Can you please use the version that I committed
>> last week - the important bits that are missing are the scope and
>> optional elements within the dependency elements (an no need for the
>> war.bundle.jar properties where present).
>>
>
> I'm not sure what you mean. I did a maven1 build and scopes are a maven2
> thing AFAIK. Please clarify.
>
Sorry for the misunderstanding - the pom you have produced is probably
fine for people using jcs with maven 1. I am thinking about the pom
that will be deployed to the maven 2 repository to make it easy for
people to use jcs in their projects that are built with maven 2. In my
experience (by no means complete) the poms don't appear to provide much
benefit for projects built with maven 1, but for maven 2 they are
essential for transitive dependencies (where scope and optional are
important).
Since we have it, I would like to see the maven 2 pom included in the
release.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Scott Eade wrote:
> Sorry to be a pain Thomas, but I'm afraid the pom that is included jar
> directory is no good. Can you please use the version that I committed
> last week - the important bits that are missing are the scope and
> optional elements within the dependency elements (an no need for the
> war.bundle.jar properties where present).
I'm not sure what you mean. I did a maven1 build and scopes are a maven2
thing AFAIK. Please clarify.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Scott Eade <se...@backstagetech.com.au>.
Sorry to be a pain Thomas, but I'm afraid the pom that is included jar
directory is no good. Can you please use the version that I committed
last week - the important bits that are missing are the scope and
optional elements within the dependency elements (an no need for the
war.bundle.jar properties where present).
Scott
Thomas Vandahl wrote:
> Hi folks,
>
> After much discussion on the JCS developer list, the first official
> release of JCS (version 1.3) after leaving the Turbine project is ready
> to vote on.
>
> You can find the created artifacts here:
> site: http://people.apache.org/~tv/jcs/
> jars: http://people.apache.org/~tv/jcs/jar/
> dist: http://people.apache.org/~tv/jcs/dist/
>
> Now, shall we release JCS as it is published there?
>
> [ ] +1 Yes, JCS 1.3 should be released
> [ ] 0 I do not care
> [ ] -1 No (give reasons)
>
> Voting is subject to the rules described in
> http://jakarta.apache.org/site/management.html
>
> The deadline is Sat, June 1 2007, 12:00 CET
>
> Note that the Jakarta PMC has the final word on whether the release is
> published
> or not.
>
> Bye, Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
All I have is the minor nit that a default target is missing and an
empty aspectSourceDirectory which prevents using maven 1.1 for building.
+1 for the release! Thanks to all who participated!
Best regards
Henning
Thomas Vandahl schrieb:
> Hi folks,
>
> After much discussion on the JCS developer list, the first official
> release of JCS (version 1.3) after leaving the Turbine project is ready
> to vote on.
>
> You can find the created artifacts here:
> site: http://people.apache.org/~tv/jcs/
> jars: http://people.apache.org/~tv/jcs/jar/
> dist: http://people.apache.org/~tv/jcs/dist/
>
> Now, shall we release JCS as it is published there?
>
> [ ] +1 Yes, JCS 1.3 should be released
> [ ] 0 I do not care
> [ ] -1 No (give reasons)
>
> Voting is subject to the rules described in
> http://jakarta.apache.org/site/management.html
>
> The deadline is Sat, June 1 2007, 12:00 CET
>
> Note that the Jakarta PMC has the final word on whether the release is
> published
> or not.
>
> Bye, Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
All I have is the minor nit that a default target is missing and an
empty aspectSourceDirectory which prevents using maven 1.1 for building.
+1 for the release! Thanks to all who participated!
Best regards
Henning
Thomas Vandahl schrieb:
> Hi folks,
>
> After much discussion on the JCS developer list, the first official
> release of JCS (version 1.3) after leaving the Turbine project is ready
> to vote on.
>
> You can find the created artifacts here:
> site: http://people.apache.org/~tv/jcs/
> jars: http://people.apache.org/~tv/jcs/jar/
> dist: http://people.apache.org/~tv/jcs/dist/
>
> Now, shall we release JCS as it is published there?
>
> [ ] +1 Yes, JCS 1.3 should be released
> [ ] 0 I do not care
> [ ] -1 No (give reasons)
>
> Voting is subject to the rules described in
> http://jakarta.apache.org/site/management.html
>
> The deadline is Sat, June 1 2007, 12:00 CET
>
> Note that the Jakarta PMC has the final word on whether the release is
> published
> or not.
>
> Bye, Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Result: [VOTE] Release JCS 1.3
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Vandahl wrote:
> Now, shall we release JCS as it is published there?
>
> [ ] +1 Yes, JCS 1.3 should be released
> [ ] 0 I do not care
> [ ] -1 No (give reasons)
Voting has closed. Here are the results:
+1 votes:
Hanson Char <ha...@gmail.com>
Thomas Vandahl <tv...@apache.org>
* Henning Schmiedehausen <hp...@intermeta.de>
* Aaron Smuts <as...@yahoo.com>
* Scott Eade <se...@backstagetech.com.au>
Rony G. Flatscher <Ro...@wu-wien.ac.at>
0 votes:
none
-1 votes:
* sebbaz@gmail.com
(* denotes binding votes of PMC members)
I could not find any information about whether Rony Flatscher is a
member of the PMC, so would someone with the necessary insight please
decide if this vote passed or not.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [VOTE] Release JCS 1.3
Posted by Aaron Smuts <as...@yahoo.com>.
[X] +1 Yes, JCS 1.3 should be released
[ ] 0 I do not care
[ ] -1 No (give reasons)
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org