You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by Sanjiva Weerawarana <sa...@watson.ibm.com> on 2000/07/08 06:16:06 UTC
when shall we do a build and dist?
The current release of Apache SOAP is apparently not usable
out-of-the-box because Sam and I screwed up (me much more than
Sam 'cause I was spsed to test things) and didn't remove some
extra stuff from the deploy.jsp file. I'd like to have a version
of Apache SOAP that's stable and working out of the box so
that other things such as the NASSL Toolkit can base off of that.
(The only reason we didn't was because the current dist is not clean.)
So, shall we do a distribution soon (like in a week)? We haven't
done many changes yet - some cleanup on the router jsp and added
some new serializers etc.. I can do some more work on the router
and also convert it to a servlet before the release.
Is there anything else that's vital right now? The code should
be pretty stable and solid IMO. I suggest we call this new
release v2.0 of Apache SOAP and consider that pretty much the
baseline version for Apache SOAP.
Along these same lines, we need some kind of release manager
person to do the production builds, etc. etc.. I believe Sam
plays that role for Jakarta. Is someone willing to take on
that role?
Sanjiva.
Re: when shall we do a build and dist? commit for Harmeet
Posted by Harmeet Bedi <hb...@hotmail.com>.
thanks all,
I will play with the build files from CVS, is there some documentation or
some
guidelines that would help. If not I can write something that makes sense to
me and send it around.
I may need
- Commit access to CVS. May need to modify build files.
- Write access to FTP. And where to put usual and release builds.
- How often should builds be done. Are they daily, weekly, or whenever some
wants.
- Instructions/pointers from anyone who has done this before. This is
my first brush with Open Source volunteer work and I would appreciate all
the help I can get.
Harmeet
----- Original Message -----
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
To: <so...@xml.apache.org>
Sent: Monday, July 10, 2000 6:49 AM
Subject: Re: when shall we do a build and dist?
> Looks like we have a volunteer! As far as I know, the qualifications are
> that you understand the software (which you do if you use it) and that
> you be willing to put in the time and effort.
>
> You will need to be a committer to do builds and put them up. I'll send
> a vote note in a sec.
>
> Thanks for volunteering!
>
> Sanjiva.
Re: when shall we do a build and dist? commit for Harmeet
Posted by Harmeet Bedi <hb...@hotmail.com>.
thanks all,
I will play with the build files from CVS, is there some documentation or
some
guidelines that would help. If not I can write something that makes sense to
me and send it around.
I may need
- Commit access to CVS. May need to modify build files.
- Write access to FTP. And where to put usual and release builds.
- How often should builds be done. Are they daily, weekly, or whenever some
wants.
- Instructions/pointers from anyone who has done this before. This is
my first brush with Open Source volunteer work and I would appreciate all
the help I can get.
Harmeet
----- Original Message -----
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
To: <so...@xml.apache.org>
Sent: Monday, July 10, 2000 6:49 AM
Subject: Re: when shall we do a build and dist?
> Looks like we have a volunteer! As far as I know, the qualifications are
> that you understand the software (which you do if you use it) and that
> you be willing to put in the time and effort.
>
> You will need to be a committer to do builds and put them up. I'll send
> a vote note in a sec.
>
> Thanks for volunteering!
>
> Sanjiva.
Re: when shall we do a build and dist?
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Looks like we have a volunteer! As far as I know, the qualifications are
that you understand the software (which you do if you use it) and that
you be willing to put in the time and effort.
You will need to be a committer to do builds and put them up. I'll send
a vote note in a sec.
Thanks for volunteering!
Sanjiva.
----- Original Message -----
From: "Harmeet Bedi" <ha...@intraspect.com>
To: <so...@xml.apache.org>
Sent: Saturday, July 08, 2000 2:45 PM
Subject: Re: when shall we do a build and dist?
> I could do the release and some QA work
>
> About me:
> Software developer by profession, active user of Tomcat and SOAP. Admirer of
> Apache group. :-)
>
> Not sure what qualifications are needed for the task of release manger, but
> thought I'd pitch in and offer.
>
> Harmeet
> ----- Original Message -----
> From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
> To: "Apache SOAP" <so...@xml.apache.org>
> Sent: Friday, July 07, 2000 9:16 PM
> Subject: when shall we do a build and dist?
>
>
> > The current release of Apache SOAP is apparently not usable
> > out-of-the-box because Sam and I screwed up (me much more than
> > Sam 'cause I was spsed to test things) and didn't remove some
> > extra stuff from the deploy.jsp file. I'd like to have a version
> > of Apache SOAP that's stable and working out of the box so
> > that other things such as the NASSL Toolkit can base off of that.
> > (The only reason we didn't was because the current dist is not clean.)
> >
> > So, shall we do a distribution soon (like in a week)? We haven't
> > done many changes yet - some cleanup on the router jsp and added
> > some new serializers etc.. I can do some more work on the router
> > and also convert it to a servlet before the release.
> >
> > Is there anything else that's vital right now? The code should
> > be pretty stable and solid IMO. I suggest we call this new
> > release v2.0 of Apache SOAP and consider that pretty much the
> > baseline version for Apache SOAP.
> >
> > Along these same lines, we need some kind of release manager
> > person to do the production builds, etc. etc.. I believe Sam
> > plays that role for Jakarta. Is someone willing to take on
> > that role?
> >
> > Sanjiva.
> >
>
Re: when shall we do a build and dist?
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Looks like we have a volunteer! As far as I know, the qualifications are
that you understand the software (which you do if you use it) and that
you be willing to put in the time and effort.
You will need to be a committer to do builds and put them up. I'll send
a vote note in a sec.
Thanks for volunteering!
Sanjiva.
----- Original Message -----
From: "Harmeet Bedi" <ha...@intraspect.com>
To: <so...@xml.apache.org>
Sent: Saturday, July 08, 2000 2:45 PM
Subject: Re: when shall we do a build and dist?
> I could do the release and some QA work
>
> About me:
> Software developer by profession, active user of Tomcat and SOAP. Admirer of
> Apache group. :-)
>
> Not sure what qualifications are needed for the task of release manger, but
> thought I'd pitch in and offer.
>
> Harmeet
> ----- Original Message -----
> From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
> To: "Apache SOAP" <so...@xml.apache.org>
> Sent: Friday, July 07, 2000 9:16 PM
> Subject: when shall we do a build and dist?
>
>
> > The current release of Apache SOAP is apparently not usable
> > out-of-the-box because Sam and I screwed up (me much more than
> > Sam 'cause I was spsed to test things) and didn't remove some
> > extra stuff from the deploy.jsp file. I'd like to have a version
> > of Apache SOAP that's stable and working out of the box so
> > that other things such as the NASSL Toolkit can base off of that.
> > (The only reason we didn't was because the current dist is not clean.)
> >
> > So, shall we do a distribution soon (like in a week)? We haven't
> > done many changes yet - some cleanup on the router jsp and added
> > some new serializers etc.. I can do some more work on the router
> > and also convert it to a servlet before the release.
> >
> > Is there anything else that's vital right now? The code should
> > be pretty stable and solid IMO. I suggest we call this new
> > release v2.0 of Apache SOAP and consider that pretty much the
> > baseline version for Apache SOAP.
> >
> > Along these same lines, we need some kind of release manager
> > person to do the production builds, etc. etc.. I believe Sam
> > plays that role for Jakarta. Is someone willing to take on
> > that role?
> >
> > Sanjiva.
> >
>
Re: when shall we do a build and dist?
Posted by Harmeet Bedi <ha...@intraspect.com>.
I could do the release and some QA work
About me:
Software developer by profession, active user of Tomcat and SOAP. Admirer of
Apache group. :-)
Not sure what qualifications are needed for the task of release manger, but
thought I'd pitch in and offer.
Harmeet
----- Original Message -----
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
To: "Apache SOAP" <so...@xml.apache.org>
Sent: Friday, July 07, 2000 9:16 PM
Subject: when shall we do a build and dist?
> The current release of Apache SOAP is apparently not usable
> out-of-the-box because Sam and I screwed up (me much more than
> Sam 'cause I was spsed to test things) and didn't remove some
> extra stuff from the deploy.jsp file. I'd like to have a version
> of Apache SOAP that's stable and working out of the box so
> that other things such as the NASSL Toolkit can base off of that.
> (The only reason we didn't was because the current dist is not clean.)
>
> So, shall we do a distribution soon (like in a week)? We haven't
> done many changes yet - some cleanup on the router jsp and added
> some new serializers etc.. I can do some more work on the router
> and also convert it to a servlet before the release.
>
> Is there anything else that's vital right now? The code should
> be pretty stable and solid IMO. I suggest we call this new
> release v2.0 of Apache SOAP and consider that pretty much the
> baseline version for Apache SOAP.
>
> Along these same lines, we need some kind of release manager
> person to do the production builds, etc. etc.. I believe Sam
> plays that role for Jakarta. Is someone willing to take on
> that role?
>
> Sanjiva.
>
Re: when shall we do a build and dist?
Posted by Harmeet Bedi <ha...@intraspect.com>.
I could do the release and some QA work
About me:
Software developer by profession, active user of Tomcat and SOAP. Admirer of
Apache group. :-)
Not sure what qualifications are needed for the task of release manger, but
thought I'd pitch in and offer.
Harmeet
----- Original Message -----
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
To: "Apache SOAP" <so...@xml.apache.org>
Sent: Friday, July 07, 2000 9:16 PM
Subject: when shall we do a build and dist?
> The current release of Apache SOAP is apparently not usable
> out-of-the-box because Sam and I screwed up (me much more than
> Sam 'cause I was spsed to test things) and didn't remove some
> extra stuff from the deploy.jsp file. I'd like to have a version
> of Apache SOAP that's stable and working out of the box so
> that other things such as the NASSL Toolkit can base off of that.
> (The only reason we didn't was because the current dist is not clean.)
>
> So, shall we do a distribution soon (like in a week)? We haven't
> done many changes yet - some cleanup on the router jsp and added
> some new serializers etc.. I can do some more work on the router
> and also convert it to a servlet before the release.
>
> Is there anything else that's vital right now? The code should
> be pretty stable and solid IMO. I suggest we call this new
> release v2.0 of Apache SOAP and consider that pretty much the
> baseline version for Apache SOAP.
>
> Along these same lines, we need some kind of release manager
> person to do the production builds, etc. etc.. I believe Sam
> plays that role for Jakarta. Is someone willing to take on
> that role?
>
> Sanjiva.
>
Re: when shall we do a build and dist?
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
This is definitely a severe problem; can you please post the diffs so
that they can be put in immediately?
On a related note, since we're at an early stage, I'd like to nominate
you as a committer. You mentioned that you've got some other changes
that may be committed too.
Other committers, please +1 or -1 Kevin's commit status.
Thanks,
Sanjiva.
----- Original Message -----
From: "Kevin J. Mitchell" <ke...@xmls.com>
To: <so...@xml.apache.org>
Sent: Monday, July 10, 2000 9:03 AM
Subject: RE: when shall we do a build and dist?
> There is a problem with HTTP comm on UNIX platforms. There is a discussion
> of the problem (and the solution I came up with) on the soap-user list. It
> seems like a pretty vital thing to fix (to me at least) for a stable
> starting point. I have a fix for it, and would like to get it into the
> Apache base. If folks agree with the severity of the problem, how should I
> go about doing this (i.e. how to get CVS commit access or supply diff to
> this list)?
>
> PS - I have several other modifications, all made to the IBM base, that may
> have value to others. As an example, see the "Processing Requests with
> custom mapping types" thread on this list.
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
> Sent: Saturday, July 08, 2000 12:16 AM
> To: Apache SOAP
> Subject: when shall we do a build and dist?
>
>
> The current release of Apache SOAP is apparently not usable
> out-of-the-box because Sam and I screwed up (me much more than
> Sam 'cause I was spsed to test things) and didn't remove some
> extra stuff from the deploy.jsp file. I'd like to have a version
> of Apache SOAP that's stable and working out of the box so
> that other things such as the NASSL Toolkit can base off of that.
> (The only reason we didn't was because the current dist is not clean.)
>
> So, shall we do a distribution soon (like in a week)? We haven't
> done many changes yet - some cleanup on the router jsp and added
> some new serializers etc.. I can do some more work on the router
> and also convert it to a servlet before the release.
>
> Is there anything else that's vital right now? The code should
> be pretty stable and solid IMO. I suggest we call this new
> release v2.0 of Apache SOAP and consider that pretty much the
> baseline version for Apache SOAP.
>
> Along these same lines, we need some kind of release manager
> person to do the production builds, etc. etc.. I believe Sam
> plays that role for Jakarta. Is someone willing to take on
> that role?
>
> Sanjiva.
>
>
Re: when shall we do a build and dist?
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
This is definitely a severe problem; can you please post the diffs so
that they can be put in immediately?
On a related note, since we're at an early stage, I'd like to nominate
you as a committer. You mentioned that you've got some other changes
that may be committed too.
Other committers, please +1 or -1 Kevin's commit status.
Thanks,
Sanjiva.
----- Original Message -----
From: "Kevin J. Mitchell" <ke...@xmls.com>
To: <so...@xml.apache.org>
Sent: Monday, July 10, 2000 9:03 AM
Subject: RE: when shall we do a build and dist?
> There is a problem with HTTP comm on UNIX platforms. There is a discussion
> of the problem (and the solution I came up with) on the soap-user list. It
> seems like a pretty vital thing to fix (to me at least) for a stable
> starting point. I have a fix for it, and would like to get it into the
> Apache base. If folks agree with the severity of the problem, how should I
> go about doing this (i.e. how to get CVS commit access or supply diff to
> this list)?
>
> PS - I have several other modifications, all made to the IBM base, that may
> have value to others. As an example, see the "Processing Requests with
> custom mapping types" thread on this list.
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
> Sent: Saturday, July 08, 2000 12:16 AM
> To: Apache SOAP
> Subject: when shall we do a build and dist?
>
>
> The current release of Apache SOAP is apparently not usable
> out-of-the-box because Sam and I screwed up (me much more than
> Sam 'cause I was spsed to test things) and didn't remove some
> extra stuff from the deploy.jsp file. I'd like to have a version
> of Apache SOAP that's stable and working out of the box so
> that other things such as the NASSL Toolkit can base off of that.
> (The only reason we didn't was because the current dist is not clean.)
>
> So, shall we do a distribution soon (like in a week)? We haven't
> done many changes yet - some cleanup on the router jsp and added
> some new serializers etc.. I can do some more work on the router
> and also convert it to a servlet before the release.
>
> Is there anything else that's vital right now? The code should
> be pretty stable and solid IMO. I suggest we call this new
> release v2.0 of Apache SOAP and consider that pretty much the
> baseline version for Apache SOAP.
>
> Along these same lines, we need some kind of release manager
> person to do the production builds, etc. etc.. I believe Sam
> plays that role for Jakarta. Is someone willing to take on
> that role?
>
> Sanjiva.
>
>
RE: when shall we do a build and dist?
Posted by "Kevin J. Mitchell" <ke...@xmls.com>.
There is a problem with HTTP comm on UNIX platforms. There is a discussion
of the problem (and the solution I came up with) on the soap-user list. It
seems like a pretty vital thing to fix (to me at least) for a stable
starting point. I have a fix for it, and would like to get it into the
Apache base. If folks agree with the severity of the problem, how should I
go about doing this (i.e. how to get CVS commit access or supply diff to
this list)?
PS - I have several other modifications, all made to the IBM base, that may
have value to others. As an example, see the "Processing Requests with
custom mapping types" thread on this list.
-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
Sent: Saturday, July 08, 2000 12:16 AM
To: Apache SOAP
Subject: when shall we do a build and dist?
The current release of Apache SOAP is apparently not usable
out-of-the-box because Sam and I screwed up (me much more than
Sam 'cause I was spsed to test things) and didn't remove some
extra stuff from the deploy.jsp file. I'd like to have a version
of Apache SOAP that's stable and working out of the box so
that other things such as the NASSL Toolkit can base off of that.
(The only reason we didn't was because the current dist is not clean.)
So, shall we do a distribution soon (like in a week)? We haven't
done many changes yet - some cleanup on the router jsp and added
some new serializers etc.. I can do some more work on the router
and also convert it to a servlet before the release.
Is there anything else that's vital right now? The code should
be pretty stable and solid IMO. I suggest we call this new
release v2.0 of Apache SOAP and consider that pretty much the
baseline version for Apache SOAP.
Along these same lines, we need some kind of release manager
person to do the production builds, etc. etc.. I believe Sam
plays that role for Jakarta. Is someone willing to take on
that role?
Sanjiva.
RE: when shall we do a build and dist?
Posted by "Kevin J. Mitchell" <ke...@xmls.com>.
There is a problem with HTTP comm on UNIX platforms. There is a discussion
of the problem (and the solution I came up with) on the soap-user list. It
seems like a pretty vital thing to fix (to me at least) for a stable
starting point. I have a fix for it, and would like to get it into the
Apache base. If folks agree with the severity of the problem, how should I
go about doing this (i.e. how to get CVS commit access or supply diff to
this list)?
PS - I have several other modifications, all made to the IBM base, that may
have value to others. As an example, see the "Processing Requests with
custom mapping types" thread on this list.
-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
Sent: Saturday, July 08, 2000 12:16 AM
To: Apache SOAP
Subject: when shall we do a build and dist?
The current release of Apache SOAP is apparently not usable
out-of-the-box because Sam and I screwed up (me much more than
Sam 'cause I was spsed to test things) and didn't remove some
extra stuff from the deploy.jsp file. I'd like to have a version
of Apache SOAP that's stable and working out of the box so
that other things such as the NASSL Toolkit can base off of that.
(The only reason we didn't was because the current dist is not clean.)
So, shall we do a distribution soon (like in a week)? We haven't
done many changes yet - some cleanup on the router jsp and added
some new serializers etc.. I can do some more work on the router
and also convert it to a servlet before the release.
Is there anything else that's vital right now? The code should
be pretty stable and solid IMO. I suggest we call this new
release v2.0 of Apache SOAP and consider that pretty much the
baseline version for Apache SOAP.
Along these same lines, we need some kind of release manager
person to do the production builds, etc. etc.. I believe Sam
plays that role for Jakarta. Is someone willing to take on
that role?
Sanjiva.