Nick, Team,
First step is to vote in a Release Manager who knows how we do releases. I was hoping Jason would help us with his
experience there.
One more thing is for everyone to agree on a list of JIRA items that should get into the 0.1 release. So please go ahead
and post a list to kick start that discussion.
thanks,
dims
On 07/15/2009 10:20 AM, Nicholas L Gallardo wrote:
I too am anxious to see the 0.1 release go live. I've received a number of
requests and would like to get people playing with the runtime as soon as
possible. Here are some issues that should be addressed before the
release.
* We have had some performance profiling work done on the runtime and found
a few issues that are affecting performance. I will open up JIRAs today
for those issues and would like to see those in 0.1 provided they are
accepted by the community. There are at least four issues that we know of
right now.
* Dims/Kevan, do incubator projects publish release candidates? If so, I'd
like to see at least one RC published before we cut the final release.
* Bryant/Jesse/Mike have opened JIRAs for the remaining work to port over
the IBM integration test bucket. I'd like to see those JIRAs completed
before we ship (hopefully finished by Friday).
* The developer's guide has great content for developing the actual
applications. We need some content on the wiki with specific examples for
how to take the build output, and package it up into a WAR. What's
common-place to us is not to users and a little more hand holding is
necessary. Maybe a specific example of how to build the WAR for deployment
on Geronimo or Tomcat.
-Nick
Nicholas Gallardo
WebSphere - REST& WebServices Development
[email protected]
Phone: 512-286-6258
Building: 903 / 5G-016
Bryant Luk
<bryant....@gmail
.com> To
[email protected]
07/15/2009 08:18 cc
AM
Subject
Re: Wink 0.1 release
Please respond to
wink-...@incubato
r.apache.org
I think we should look at the issues in JIRA first and address as many
as we can that are related to the server/client/common component (i.e.
identify ones that are going to be 0.1 or are going to be later). I
hope that we are finished porting the main integration test cases by
the end of this week.
In particular:
https://issues.apache.org/jira/browse/WINK-34
https://issues.apache.org/jira/browse/WINK-76
In addition, any remaining spec related issues. I think most of these
are taken care of but will need to look at the list. I don't know all
the rules behind claiming TCK compliance, but I think we should also
take another pass at the TCK since there were significant (and IMO
correct) changes made.
Also, I think Nick had a few issues he wanted to get in.
I am also anxious for a release but I think we have to take care of
some of these first.
On Wed, Jul 15, 2009 at 7:59 AM, Michael Elman<[email protected]> wrote:
I also think that Wink is ready for 0.1
Should we start formal voting?
On Wed, Jul 15, 2009 at 9:17 AM, Snitkovsky, Martin<
[email protected]> wrote:
I agree that adoption wise it is *highly* important to release 0.1 as
soon
as we can.
We already got few requests from inside HP to consume Wink.
The first questions was "when you are going to publish first stable
release/build?".
Does someone have rough estimation on how long it can take to go from
incubator snapshot to 0.1 release?
--martin
-----Original Message-----
From: Baram, Eliezer
Sent: Tuesday, July 14, 2009 2:22 PM
To: [email protected]
Subject: Wink 0.1 release
Hi
Now, when Wink is JAX-RS compliant, have a build environment and all the
resources are licensed under Apache license, it's time we discuss
releasing
Wink 0.1. Having a released version of Wink is an important step of
adoption
Wink by users and enlarging the community and I think we should have one
as
early as possible.
What are the things that you think that must be handled before we can
release Wink 0.1?
I have two:
1) Removing Symphony references from the entire SDK.
2) Validate that the documentation is still accurate after the
changes
we enter the SDK in the last period.
Thoughts?
--Eli
--
- Bryant Luk
