The story seems quite simple so I thought I'd just ask for a vote sorry
if too stressed.
The interaction jelly tag-library is now ready for release 1.1.
It has been recently boosted with a finer control on auto-completion,
and maven console plugin is using it successfully.
Thanks to give it a try* and provide a vote.
This vote will last till Friday 12:00 GMT.
[ ] +1 yes let's release it
[ ] +0 maybe
[ ] -0 seems not ready
[ ] -1 no, don't!
thank you
paul
* test instruction. Since Jelly-tags-interaction is mostly for
embedding, playing with it can be a challenge. Here's an avenue:
- download it, invoke "maven jar:install-snapshot" then modify the
console plugin's project.xml to depend on 1.1-SNAPSHT, run maven
console where you want
- run the sample script inside the interaction's test directory
To unsubscribe, e-mail: commons-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: commons-dev-help (AT) jakarta (DOT) apache.org

Here is my +1, although I wasn't able to give it a try (but I trust
your judgement :-)

5/9/06, Paul Libbrecht <paul (AT) activemath (DOT) orgwrote:
Thanks to give it a try* and provide a vote.

[X ] +1 yes let's release it

To unsubscribe, e-mail: commons-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: commons-dev-help (AT) jakarta (DOT) apache.org

Tue, 2006-05-09 at 23:07 +0200, Paul Libbrecht wrote:
The story seems quite simple so I thought I'd just ask for a vote sorry
if too stressed.
The interaction jelly tag-library is now ready for release 1.1.
It has been recently boosted with a finer control on auto-completion,
and maven console plugin is using it successfully.
Thanks to give it a try* and provide a vote.

is this a vote on the idea of releasing (in other words, a release plan)
or on actually cutting a release?

if it's an actual release vote then i'd like to be able to check a
release candidate before casting a vote
- robert

To unsubscribe, e-mail: commons-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: commons-dev-help (AT) jakarta (DOT) apache.org

robert burrell donkin wrote:
Tue, 2006-05-09 at 23:07 +0200, Paul Libbrecht wrote:

>The story seems quite simple so I thought I'd just ask for a vote sorry if too stressed.
>The interaction jelly tag-library is now ready for release 1.1.
>It has been recently boosted with a finer control on auto-completion, and maven console plugin is using it successfully. Thanks to give it a try* and provide a vote.
is this a vote on the idea of releasing (in other words, a release plan) or on actually cutting a release?

if it's an actual release vote then i'd like to be able to check a
release candidate before casting a vote

I'm trying to return to this but am getting drowned in time.
I would like to request votes to release jelly-tags-interaction.
I have followed Preparations to release and can judge the following steps:
- I'm nominated as release manager for this (because of last votes at least)
- I am proposing a release plan (below)

Here's the plan:
- all issues with this tag-libs are cleared
- no further changes are needed for the release and almost no risk of
concurrent change exist (hence no branch is needed).
- the release shall, as with most jelly-tag-libraries, only produce jar
files to be consumed from the maven repo at ibiblio and the repo at
apache. No source or binary distribution will be made.
- once the vote passed, I will simply update changes.xml and
project.xml, tag the files, upload the jar to the Apache, submit a jar
upload to iblio's repo.

I have assembled the following release candidates
- a site with RC1 version tag:
http://people.apache.org/~
- a jar which is the sole outcome of this subproject:
http://people.apache.org/~

Please tell me if that's enough to request a vote.

thanks

paul

Dion Gillard wrote:
>I have assembled the following release candidates
>- a site with RC1 version tag:
>http://people.apache.org/~
>- a jar which is the sole outcome of this subproject:
>http://people.apache.org/~
>>
I think we need to include a NTICE file into the jar, right? The
license by itself isn't enough, from memory.
Thanks to remind this. Indeed, this is needed according to:

and is now fixed int he linked jar above.
Without more comments, I'll request a vote tomorrow morning.

paul

I hereby request to vote about the release of the jelly subproject
"interaction tag library".
The details of the release plan are below.
I would like to please request a vote for 36 hours, ie. till Wednesday
14:00 GMT.
+1 [ ] yes, let's do it
0 [ ] let it happen but I can't really check
-1 [ ] don't do it because

thank you in advance.

paul

Paul Libbrecht wrote:
Here's the plan:
- all issues with this tag-libs are cleared
- no further changes are needed for the release and almost no risk
of concurrent change exist (hence no branch is needed).
- the release shall, as with most jelly-tag-libraries, only produce
jar files to be consumed from the maven repo at ibiblio and the repo
at apache. No source or binary distribution will be made.
- once the vote passed, I will simply update changes.xml and
project.xml, tag the files, upload the jar to the Apache, submit a jar
upload to iblio's repo.

I have assembled the following release candidates
- a site with RC1 version tag:
http://people.apache.org/~
- a jar which is the sole outcome of this subproject:
http://people.apache.org/~

6/19/06, Paul Libbrecht <paul (AT) activemath (DOT) orgwrote:
I hereby request to vote about the release of the jelly subproject
"interaction tag library".
The details of the release plan are below.
I would like to please request a vote for 36 hours, ie. till Wednesday
14:00 GMT.
+1 [ ] yes, let's do it
0 [X] let it happen but I can't really check
-1 [ ] don't do it because

<snip/>

Regardless of what Jelly has been doing in the past, IM its a good
idea to have source distributions for any release, given which one
would be able to (atleast after meeting certain pre-requisites)
effectively reproduce the release binaries. Why don't Jelly taglibs
have accompanying source distros?

Note we had a similar situation in Jakarta Taglibs which AFAICT has
since been remedied. Also, a gentle reminder to please tag SVN (as
previous Jelly releases have done).

Since I've not participated in the discussion so far, and wasn't
around to bring this up earlier for the last three days when the plan
(below) was posted, I will vote 0. I will also encourage you to leave
votes open for atleast 72 hours (instead of 36).

Thank you for your time towards this release.
-Rahul

thank you in advance.

paul

Paul Libbrecht wrote:
Here's the plan:
- all issues with this tag-libs are cleared
- no further changes are needed for the release and almost no risk
of concurrent change exist (hence no branch is needed).
- the release shall, as with most jelly-tag-libraries, only produce
jar files to be consumed from the maven repo at ibiblio and the repo
at apache. No source or binary distribution will be made.
- once the vote passed, I will simply update changes.xml and
project.xml, tag the files, upload the jar to the Apache, submit a jar
upload to iblio's repo.

I have assembled the following release candidates
- a site with RC1 version tag:
http://people.apache.org/~
- a jar which is the sole outcome of this subproject:
http://people.apache.org/~
>
>
>
>
>

To unsubscribe, e-mail: commons-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: commons-dev-help (AT) jakarta (DOT) apache.org

+1

If anybody wants to try it with the new maven console plugin (which will
be released if this vote passes):

http://people.apache.org/~
http://people.apache.org/~

Cheers,
-Lukas

Paul Libbrecht wrote:
I hereby request to vote about the release of the jelly subproject
"interaction tag library".
The details of the release plan are below.
I would like to please request a vote for 36 hours, ie. till Wednesday
14:00 GMT.
+1 [ ] yes, let's do it
0 [ ] let it happen but I can't really check
-1 [ ] don't do it because

thank you in advance.

paul

Paul Libbrecht wrote:

>Here's the plan:
>- all issues with this tag-libs are cleared
>- no further changes are needed for the release and almost no risk
>of concurrent change exist (hence no branch is needed).
>- the release shall, as with most jelly-tag-libraries, only produce
>jar files to be consumed from the maven repo at ibiblio and the repo
>at apache. No source or binary distribution will be made.
>- once the vote passed, I will simply update changes.xml and
>project.xml, tag the files, upload the jar to the Apache, submit a jar
>upload to iblio's repo.
>>
>I have assembled the following release candidates
>- a site with RC1 version tag:
>http://people.apache.org/~
>- a jar which is the sole outcome of this subproject:
>http://people.apache.org/~
>>

To unsubscribe, e-mail: commons-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: commons-dev-help (AT) jakarta (DOT) apache.org

Rahul Akolkar wrote:
Regardless of what Jelly has been doing in the past, IM its a good
idea to have source distributions for any release, given which one
would be able to (atleast after meeting certain pre-requisites)
effectively reproduce the release binaries. Why don't Jelly taglibs
have accompanying source distros?
As a general wish, I only agree.
In this case both limit in time and the fact that this tag-library is
exactly made of one class tend me to not do so.
Note we had a similar situation in Jakarta Taglibs which AFAICT has
since been remedied. Also, a gentle reminder to please tag SVN (as
previous Jelly releases have done).
course tagging was planned. Do you mean I should tag RC1 as well ?
Since I've not participated in the discussion so far, and wasn't
around to bring this up earlier for the last three days when the plan
(below) was posted, I will vote 0. I will also encourage you to leave
votes open for atleast 72 hours (instead of 36).
The fact that I sent this wish already long ago, with less clarity
indeed, pushes me here. And also, the fact that maven plugin release is
waiting.

paul

Thank you for your time towards this release.
-Rahul
>
>
>thank you in advance.
>>
>paul
>>
>Paul Libbrecht wrote:
>Here's the plan:
>- all issues with this tag-libs are cleared
>- no further changes are needed for the release and almost no risk
>of concurrent change exist (hence no branch is needed).
>- the release shall, as with most jelly-tag-libraries, only produce
>jar files to be consumed from the maven repo at ibiblio and the repo
>at apache. No source or binary distribution will be made.
>- once the vote passed, I will simply update changes.xml and
>project.xml, tag the files, upload the jar to the Apache, submit a jar
>upload to iblio's repo.
>>
>I have assembled the following release candidates
>- a site with RC1 version tag:
>http://people.apache.org/~
>- a jar which is the sole outcome of this subproject:
>
>http://people.apache.org/~
>>
>>
>>
>>
>>
>>
>

+1

While I disapprove of a jar only release, I think I'd prefer to get the
release out given the lack of Jelly committers.
Stephen

Paul Libbrecht wrote:
I hereby request to vote about the release of the jelly subproject
"interaction tag library".
The details of the release plan are below.
I would like to please request a vote for 36 hours, ie. till Wednesday
14:00 GMT.
+1 [ ] yes, let's do it
0 [ ] let it happen but I can't really check
-1 [ ] don't do it because

thank you in advance.

paul

Paul Libbrecht wrote:

>Here's the plan:
>- all issues with this tag-libs are cleared
>- no further changes are needed for the release and almost no risk
>of concurrent change exist (hence no branch is needed).
>- the release shall, as with most jelly-tag-libraries, only produce
>jar files to be consumed from the maven repo at ibiblio and the repo
>at apache. No source or binary distribution will be made.
>- once the vote passed, I will simply update changes.xml and
>project.xml, tag the files, upload the jar to the Apache, submit a jar
>upload to iblio's repo.
>>
>I have assembled the following release candidates
>- a site with RC1 version tag:
>http://people.apache.org/~
>- a jar which is the sole outcome of this subproject:
>http://people.apache.org/~
>>

To unsubscribe, e-mail: commons-dev-unsubscribe (AT) jakarta (DOT) apache.org
For additional commands, e-mail: commons-dev-help (AT) jakarta (DOT) apache.org

Maybe I'll work on this tonight local time (in about 14 hours).
The problem is that "maven dist" calls the maven dist of jelly which is
quite wrong, I think and I did not want to touch this yet.
If it sounds appropriate and someone can check my candidate sources I
could try this tonight before tagging it would only affect,
probably, the maven.xml in jelly/jelly-tags.

paul

Dion Gillard wrote:
Paul can we post the source/binary distribution release after getting
the jar out?

6/20/06, Paul Libbrecht <paul (AT) activemath (DOT) orgwrote:
>Rahul Akolkar wrote:
>Regardless of what Jelly has been doing in the past, IM its a good
>idea to have source distributions for any release, given which one
>would be able to (atleast after meeting certain pre-requisites)
>effectively reproduce the release binaries. Why don't Jelly taglibs
>have accompanying source distros?
>As a general wish, I only agree.
>In this case both limit in time and the fact that this tag-library is
>exactly made of one class tend me to not do so.
>Note we had a similar situation in Jakarta Taglibs which AFAICT has
>since been remedied. Also, a gentle reminder to please tag SVN (as
>previous Jelly releases have done).
>course tagging was planned. Do you mean I should tag RC1 as well ?
>Since I've not participated in the discussion so far, and wasn't
>around to bring this up earlier for the last three days when the plan
>(below) was posted, I will vote 0. I will also encourage you to leave
>votes open for atleast 72 hours (instead of 36).
>The fact that I sent this wish already long ago, with less clarity
>indeed, pushes me here. And also, the fact that maven plugin release is
>waiting.
>>
>paul
>>
>Thank you for your time towards this release.
>-Rahul
>>
>>
>>thank you in advance.
>>>
>>paul
>>>
>>Paul Libbrecht wrote:
>>Here's the plan:
>>- all issues with this tag-libs are cleared
>>- no further changes are needed for the release and almost no
>risk
>>of concurrent change exist (hence no branch is needed).
>>- the release shall, as with most jelly-tag-libraries, only produce
>>jar files to be consumed from the maven repo at ibiblio and the
>repo
>>at apache. No source or binary distribution will be made.
>>- once the vote passed, I will simply update changes.xml and
>>project.xml, tag the files, upload the jar to the Apache, submit
>a jar
>>upload to iblio's repo.
>>>
>>I have assembled the following release candidates
>>- a site with RC1 version tag:
>>http://people.apache.org/~
>>- a jar which is the sole outcome of this subproject:
>>>
>>
>http://people.apache.org/~
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>

The vote result is as follows:
+1 Paul
+0 Rahul
+1 Dion
+1 Stephen
Result: +1

I tried to follow the procedure in order to see the impact of a binary
and source releases and have to say that I feat it'll move lots of
stuffs around. In particular, how would the mirrorred download look like
with several flavours of dists (both binary and sources) ? I have given
it up for now. I find it ok to have a single binary and source
distribution of the whole jelly project (yes, I know, it should be
released more often!).
We may consider the maven sources plugin at some point

I am now setting things up for a proper signing and hashing then will
achieve the jar-oriented tasks of the release guide. And send an
announcement here and on commons-users.

paul

Paul Libbrecht wrote:
I hereby request to vote about the release of the jelly subproject
"interaction tag library".
The details of the release plan are below.
I would like to please request a vote for 36 hours, ie. till Wednesday
14:00 GMT.
+1 [ ] yes, let's do it
0 [ ] let it happen but I can't really check
-1 [ ] don't do it because

thank you in advance.

paul

Paul Libbrecht wrote:
>Here's the plan:
>- all issues with this tag-libs are cleared
>- no further changes are needed for the release and almost no risk
>of concurrent change exist (hence no branch is needed).
>- the release shall, as with most jelly-tag-libraries, only produce
>jar files to be consumed from the maven repo at ibiblio and the repo
>at apache. No source or binary distribution will be made.
>- once the vote passed, I will simply update changes.xml and
>project.xml, tag the files, upload the jar to the Apache, submit a
>jar upload to iblio's repo.
>>
>I have assembled the following release candidates
>- a site with RC1 version tag:
>http://people.apache.org/~
>- a jar which is the sole outcome of this subproject:
>http://people.apache.org/~
>>
>