You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Igor Vaynberg <ig...@gmail.com> on 2007/03/08 00:41:52 UTC
VOTE release 1.3beta
this vote is to release 1.3beta
-igor
Re: VOTE release 1.3beta
Posted by Al Maw <wi...@almaw.com>.
Igor Vaynberg wrote:
> this vote is to release 1.3beta
+1, but only after I've made the Maven 2 stuff nicer, so we can make
this repeatable (WICKET-228).
Al
Re: VOTE release 1.3beta
Posted by Frank Bille <fr...@gmail.com>.
+1 on 1.3-beta1-incubating.
On 3/8/07, Igor Vaynberg <ig...@gmail.com> wrote:
>
> this vote is to release 1.3beta
>
> -igor
>
Re: VOTE release 1.3beta
Posted by Juergen Donnerstag <ju...@gmail.com>.
+1
Juergen
Re: VOTE release 1.3beta
Posted by Jean-Baptiste Quenot <jb...@apache.org>.
* Igor Vaynberg:
> this vote is to release 1.3beta
+1
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
Re: VOTE release 1.3beta
Posted by Martijn Dashorst <ma...@gmail.com>.
+1
Please note that this is merely a 'legal' release to ratify our
release procedure and to identify any remaining legal issues.
Martijn
On 3/8/07, Eelco Hillenius <ee...@gmail.com> wrote:
> +1
>
> Eelco
>
> On 3/7/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > this vote is to release 1.3beta
> >
> > -igor
> >
>
--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org
Re: VOTE release 1.3beta
Posted by Eelco Hillenius <ee...@gmail.com>.
+1
Eelco
On 3/7/07, Igor Vaynberg <ig...@gmail.com> wrote:
> this vote is to release 1.3beta
>
> -igor
>
Re: VOTE release 1.3beta
Posted by Gwyn Evans <gw...@gmail.com>.
+1
/Gwyn
On 07/03/07, Igor Vaynberg <ig...@gmail.com> wrote:
> this vote is to release 1.3beta
>
> -igor
>
Re: VOTE release 1.3beta
Posted by Igor Vaynberg <ig...@gmail.com>.
+1
-igor
On 3/7/07, Igor Vaynberg <ig...@gmail.com> wrote:
>
> this vote is to release 1.3beta
>
> -igor
>
Re: VOTE release 1.3beta
Posted by Eelco Hillenius <ee...@gmail.com>.
Yeah, I'd like like to have it available somewhere, preferably in the
maven repository. Can't we name the version such that it is clear that
it is an unofficial version or something?
Eelco
On 3/10/07, Martijn Dashorst <ma...@gmail.com> wrote:
> Agreed. However I think we should publish the release to the @dev
> crowd. So we will get some traction for our 1.3 effort.
>
> However, before we can go public with the release it should pass the
> ipmc, so whatever happens, it won't happen before the end of the week
> ;-)
>
> Martijn
>
> On 3/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > this is of course only for the "public" release. we should continue forward
> > with the ipmc release to check our legal stuff.
> >
> > -igor
> >
> >
> > On 3/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > >
> > > i think we should hold off on this vote because now there is a possibility
> > > of all 2.0 backports making it into this branch after this release.
> > >
> > > so for now i am changing my vote to -1 until we have decided on the
> > > roadmap for the 1.3 branch.
> > >
> > > -igor
> > >
> > >
> > > On 3/7/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > > >
> > > > this vote is to release 1.3beta
> > > >
> > > > -igor
> > > >
> > >
> > >
> >
>
>
> --
> Learn Wicket at ApacheCon Europe: http://apachecon.com
> Join the wicket community at irc.freenode.net: ##wicket
> Wicket 1.2.5 will keep your server alive. Download Wicket now!
> http://wicketframework.org
>
Re: VOTE release 1.3beta
Posted by Eelco Hillenius <ee...@gmail.com>.
On 3/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> and people who are interested already have it via our maven repository
No, and *this* is my point: they only have snapshots currently. Any
fixture, even if it was just a date, would give people the ability to
take a rest for a few days. Nothing more, as it's not a branch and
eventually they'll have to get the other features in if they want to
take advantage of further bug fixes and stuff.
Eelco
Re: VOTE release 1.3beta
Posted by Igor Vaynberg <ig...@gmail.com>.
and people who are interested already have it via our maven repository
-igor
On 3/10/07, Eelco Hillenius <ee...@gmail.com> wrote:
>
> > >, so i dont see any reason to create any publically accessible
> artifact.
>
> Also, parties like Eclipse and such are putting out no-guarantee
> nightly builds and integration builds etc. This would be an excellent
> point to put out an integration build: something that is typically for
> internal use, but for those living on the edge, they can use it.
>
> Eelco
>
Re: VOTE release 1.3beta
Posted by Eelco Hillenius <ee...@gmail.com>.
> >, so i dont see any reason to create any publically accessible artifact.
Also, parties like Eclipse and such are putting out no-guarantee
nightly builds and integration builds etc. This would be an excellent
point to put out an integration build: something that is typically for
internal use, but for those living on the edge, they can use it.
Eelco
Re: VOTE release 1.3beta
Posted by Eelco Hillenius <ee...@gmail.com>.
We've been here before though. :) It seems impossible to come to a
common understanding on this. For the record, I agree with Johan, but
I think that if we can't agree on whether to call it beta, we should
just call it alpha or integration build or something. As long as we
keep going trying to push a release out.
Eelco
On 3/14/07, Igor Vaynberg <ig...@gmail.com> wrote:
> sure. but it is the magnitude of those changes.
>
> beta should more or less be feature complete. all these changes you are
> backporting are features.
>
> -igor
>
>
> On 3/14/07, Johan Compagner <jc...@gmail.com> wrote:
> >
> > beta == changes can happen..
> > beta != api is stable.
> >
> > johan
> >
> >
> > On 3/11/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > >
> > > i am afraid of people starting to use it. put a lot of time into it,
> > then
> > > upgrade to beta2 and have to redo a bunch of crap. if this happened to
> > me
> > > id
> > > be pissed, i dont like to have the poverbial rug pulled from under me
> > when
> > > im using a beta.
> > >
> > > if we are going to break it then lets at least do it before we have any
> > > sort
> > > of a public release. until then people who dont mind living on the
> > > bleeding
> > > edge can build from source - which those kinds of people do anyways.
> > >
> > > -igor
> > >
> > >
> > > On 3/10/07, Eelco Hillenius <ee...@gmail.com> wrote:
> > > >
> > > > > i dont see how you expect to get traction when people know there are
> > > big
> > > > api
> > > > > breaks coming soon? why try something that will be completely broken
> > > in
> > > > a
> > > > > week?
> > > >
> > > > We're not making this build for new people to try out.
> > > >
> > > > > the people who are interested are the people who build from source
> > > >
> > > > Yes, like us. And like I said, before I want to start working on the
> > > > last few breaks, I'd like to take a breath and have a version without
> > > > the breaks of which i know it works well, so that while I'm upgrading
> > > > and testing in the background, the rest of the team can go on and we
> > > > can make a deployment with it. I'm sure this would be appreciated by
> > > > more people who currently work on 1.3.
> > > >
> > > > >, so i dont see any reason to create any publically accessible
> > > artifact.
> > > >
> > > > What are you afraid of?
> > > >
> > > > Eelco
> > > >
> > >
> >
>
Re: VOTE release 1.3beta
Posted by Igor Vaynberg <ig...@gmail.com>.
sure. but it is the magnitude of those changes.
beta should more or less be feature complete. all these changes you are
backporting are features.
-igor
On 3/14/07, Johan Compagner <jc...@gmail.com> wrote:
>
> beta == changes can happen..
> beta != api is stable.
>
> johan
>
>
> On 3/11/07, Igor Vaynberg <ig...@gmail.com> wrote:
> >
> > i am afraid of people starting to use it. put a lot of time into it,
> then
> > upgrade to beta2 and have to redo a bunch of crap. if this happened to
> me
> > id
> > be pissed, i dont like to have the poverbial rug pulled from under me
> when
> > im using a beta.
> >
> > if we are going to break it then lets at least do it before we have any
> > sort
> > of a public release. until then people who dont mind living on the
> > bleeding
> > edge can build from source - which those kinds of people do anyways.
> >
> > -igor
> >
> >
> > On 3/10/07, Eelco Hillenius <ee...@gmail.com> wrote:
> > >
> > > > i dont see how you expect to get traction when people know there are
> > big
> > > api
> > > > breaks coming soon? why try something that will be completely broken
> > in
> > > a
> > > > week?
> > >
> > > We're not making this build for new people to try out.
> > >
> > > > the people who are interested are the people who build from source
> > >
> > > Yes, like us. And like I said, before I want to start working on the
> > > last few breaks, I'd like to take a breath and have a version without
> > > the breaks of which i know it works well, so that while I'm upgrading
> > > and testing in the background, the rest of the team can go on and we
> > > can make a deployment with it. I'm sure this would be appreciated by
> > > more people who currently work on 1.3.
> > >
> > > >, so i dont see any reason to create any publically accessible
> > artifact.
> > >
> > > What are you afraid of?
> > >
> > > Eelco
> > >
> >
>
Re: VOTE release 1.3beta
Posted by Johan Compagner <jc...@gmail.com>.
beta == changes can happen..
beta != api is stable.
johan
On 3/11/07, Igor Vaynberg <ig...@gmail.com> wrote:
>
> i am afraid of people starting to use it. put a lot of time into it, then
> upgrade to beta2 and have to redo a bunch of crap. if this happened to me
> id
> be pissed, i dont like to have the poverbial rug pulled from under me when
> im using a beta.
>
> if we are going to break it then lets at least do it before we have any
> sort
> of a public release. until then people who dont mind living on the
> bleeding
> edge can build from source - which those kinds of people do anyways.
>
> -igor
>
>
> On 3/10/07, Eelco Hillenius <ee...@gmail.com> wrote:
> >
> > > i dont see how you expect to get traction when people know there are
> big
> > api
> > > breaks coming soon? why try something that will be completely broken
> in
> > a
> > > week?
> >
> > We're not making this build for new people to try out.
> >
> > > the people who are interested are the people who build from source
> >
> > Yes, like us. And like I said, before I want to start working on the
> > last few breaks, I'd like to take a breath and have a version without
> > the breaks of which i know it works well, so that while I'm upgrading
> > and testing in the background, the rest of the team can go on and we
> > can make a deployment with it. I'm sure this would be appreciated by
> > more people who currently work on 1.3.
> >
> > >, so i dont see any reason to create any publically accessible
> artifact.
> >
> > What are you afraid of?
> >
> > Eelco
> >
>
Re: VOTE release 1.3beta
Posted by Gwyn Evans <gw...@gmail.com>.
As I mentioned in another thread, my preference would be 'checkpoint',
maybe with a date, but as long as we don't raise any expectations
about it, then I'm not against making it semi-public if/when we get it
cleared.
/Gwyn
On 11/03/07, Xavier Hanin <xa...@gmail.com> wrote:
> On 3/11/07, Eelco Hillenius <ee...@gmail.com> wrote:
> >
> > > i am afraid of people starting to use it. put a lot of time into it,
> > then
> > > upgrade to beta2 and have to redo a bunch of crap. if this happened to
> > me id
> > > be pissed, i dont like to have the poverbial rug pulled from under me
> > when
> > > im using a beta.
> >
> > So we don't call it beta but alpha or integration build with a date or
> > just a date, we don't put it on sourceforge but just on maven.
>
>
> As a user, I would prefer alpha or integration build than beta, it is much
> closer to the purpose of this release, and make it more obvious.
>
> - Xavier
>
> > if we are going to break it then lets at least do it before we have any
> > sort
> > > of a public release. until then people who dont mind living on the
> > bleeding
> > > edge can build from source - which those kinds of people do anyways.
> >
> > It is not for the people who are on 1.2, but who are on 1.3. I expect
> > most to follow asap - which is THE reason why I would like it in 1.3
> > rather than 1.4 but this intermediate fixture would give people a
> > change to take a breath.
> >
> > Eelco
> >
>
Re: VOTE release 1.3beta
Posted by Xavier Hanin <xa...@gmail.com>.
On 3/11/07, Eelco Hillenius <ee...@gmail.com> wrote:
>
> > i am afraid of people starting to use it. put a lot of time into it,
> then
> > upgrade to beta2 and have to redo a bunch of crap. if this happened to
> me id
> > be pissed, i dont like to have the poverbial rug pulled from under me
> when
> > im using a beta.
>
> So we don't call it beta but alpha or integration build with a date or
> just a date, we don't put it on sourceforge but just on maven.
As a user, I would prefer alpha or integration build than beta, it is much
closer to the purpose of this release, and make it more obvious.
- Xavier
> if we are going to break it then lets at least do it before we have any
> sort
> > of a public release. until then people who dont mind living on the
> bleeding
> > edge can build from source - which those kinds of people do anyways.
>
> It is not for the people who are on 1.2, but who are on 1.3. I expect
> most to follow asap - which is THE reason why I would like it in 1.3
> rather than 1.4 but this intermediate fixture would give people a
> change to take a breath.
>
> Eelco
>
Re: VOTE release 1.3beta
Posted by Igor Vaynberg <ig...@gmail.com>.
if all you want to do is to create a separate version for this in our maven
repo thats fine with me.
-igor
On 3/10/07, Eelco Hillenius <ee...@gmail.com> wrote:
>
> > i am afraid of people starting to use it. put a lot of time into it,
> then
> > upgrade to beta2 and have to redo a bunch of crap. if this happened to
> me id
> > be pissed, i dont like to have the poverbial rug pulled from under me
> when
> > im using a beta.
>
> So we don't call it beta but alpha or integration build with a date or
> just a date, we don't put it on sourceforge but just on maven.
>
> > if we are going to break it then lets at least do it before we have any
> sort
> > of a public release. until then people who dont mind living on the
> bleeding
> > edge can build from source - which those kinds of people do anyways.
>
> It is not for the people who are on 1.2, but who are on 1.3. I expect
> most to follow asap - which is THE reason why I would like it in 1.3
> rather than 1.4 but this intermediate fixture would give people a
> change to take a breath.
>
> Eelco
>
Re: VOTE release 1.3beta
Posted by Eelco Hillenius <ee...@gmail.com>.
> i am afraid of people starting to use it. put a lot of time into it, then
> upgrade to beta2 and have to redo a bunch of crap. if this happened to me id
> be pissed, i dont like to have the poverbial rug pulled from under me when
> im using a beta.
So we don't call it beta but alpha or integration build with a date or
just a date, we don't put it on sourceforge but just on maven.
> if we are going to break it then lets at least do it before we have any sort
> of a public release. until then people who dont mind living on the bleeding
> edge can build from source - which those kinds of people do anyways.
It is not for the people who are on 1.2, but who are on 1.3. I expect
most to follow asap - which is THE reason why I would like it in 1.3
rather than 1.4 but this intermediate fixture would give people a
change to take a breath.
Eelco
Re: VOTE release 1.3beta
Posted by Igor Vaynberg <ig...@gmail.com>.
i am afraid of people starting to use it. put a lot of time into it, then
upgrade to beta2 and have to redo a bunch of crap. if this happened to me id
be pissed, i dont like to have the poverbial rug pulled from under me when
im using a beta.
if we are going to break it then lets at least do it before we have any sort
of a public release. until then people who dont mind living on the bleeding
edge can build from source - which those kinds of people do anyways.
-igor
On 3/10/07, Eelco Hillenius <ee...@gmail.com> wrote:
>
> > i dont see how you expect to get traction when people know there are big
> api
> > breaks coming soon? why try something that will be completely broken in
> a
> > week?
>
> We're not making this build for new people to try out.
>
> > the people who are interested are the people who build from source
>
> Yes, like us. And like I said, before I want to start working on the
> last few breaks, I'd like to take a breath and have a version without
> the breaks of which i know it works well, so that while I'm upgrading
> and testing in the background, the rest of the team can go on and we
> can make a deployment with it. I'm sure this would be appreciated by
> more people who currently work on 1.3.
>
> >, so i dont see any reason to create any publically accessible artifact.
>
> What are you afraid of?
>
> Eelco
>
Re: VOTE release 1.3beta
Posted by Eelco Hillenius <ee...@gmail.com>.
> i dont see how you expect to get traction when people know there are big api
> breaks coming soon? why try something that will be completely broken in a
> week?
We're not making this build for new people to try out.
> the people who are interested are the people who build from source
Yes, like us. And like I said, before I want to start working on the
last few breaks, I'd like to take a breath and have a version without
the breaks of which i know it works well, so that while I'm upgrading
and testing in the background, the rest of the team can go on and we
can make a deployment with it. I'm sure this would be appreciated by
more people who currently work on 1.3.
>, so i dont see any reason to create any publically accessible artifact.
What are you afraid of?
Eelco
Re: VOTE release 1.3beta
Posted by Igor Vaynberg <ig...@gmail.com>.
i dont see how you expect to get traction when people know there are big api
breaks coming soon? why try something that will be completely broken in a
week?
the people who are interested are the people who build from source, so i
dont see any reason to create any publically accessible artifact.
-igor
On 3/10/07, Martijn Dashorst <ma...@gmail.com> wrote:
>
> Agreed. However I think we should publish the release to the @dev
> crowd. So we will get some traction for our 1.3 effort.
>
> However, before we can go public with the release it should pass the
> ipmc, so whatever happens, it won't happen before the end of the week
> ;-)
>
> Martijn
>
> On 3/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > this is of course only for the "public" release. we should continue
> forward
> > with the ipmc release to check our legal stuff.
> >
> > -igor
> >
> >
> > On 3/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > >
> > > i think we should hold off on this vote because now there is a
> possibility
> > > of all 2.0 backports making it into this branch after this release.
> > >
> > > so for now i am changing my vote to -1 until we have decided on the
> > > roadmap for the 1.3 branch.
> > >
> > > -igor
> > >
> > >
> > > On 3/7/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > > >
> > > > this vote is to release 1.3beta
> > > >
> > > > -igor
> > > >
> > >
> > >
> >
>
>
> --
> Learn Wicket at ApacheCon Europe: http://apachecon.com
> Join the wicket community at irc.freenode.net: ##wicket
> Wicket 1.2.5 will keep your server alive. Download Wicket now!
> http://wicketframework.org
>
Re: VOTE release 1.3beta
Posted by Martijn Dashorst <ma...@gmail.com>.
Agreed. However I think we should publish the release to the @dev
crowd. So we will get some traction for our 1.3 effort.
However, before we can go public with the release it should pass the
ipmc, so whatever happens, it won't happen before the end of the week
;-)
Martijn
On 3/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> this is of course only for the "public" release. we should continue forward
> with the ipmc release to check our legal stuff.
>
> -igor
>
>
> On 3/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
> >
> > i think we should hold off on this vote because now there is a possibility
> > of all 2.0 backports making it into this branch after this release.
> >
> > so for now i am changing my vote to -1 until we have decided on the
> > roadmap for the 1.3 branch.
> >
> > -igor
> >
> >
> > On 3/7/07, Igor Vaynberg <ig...@gmail.com> wrote:
> > >
> > > this vote is to release 1.3beta
> > >
> > > -igor
> > >
> >
> >
>
--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org
Re: VOTE release 1.3beta
Posted by Igor Vaynberg <ig...@gmail.com>.
this is of course only for the "public" release. we should continue forward
with the ipmc release to check our legal stuff.
-igor
On 3/10/07, Igor Vaynberg <ig...@gmail.com> wrote:
>
> i think we should hold off on this vote because now there is a possibility
> of all 2.0 backports making it into this branch after this release.
>
> so for now i am changing my vote to -1 until we have decided on the
> roadmap for the 1.3 branch.
>
> -igor
>
>
> On 3/7/07, Igor Vaynberg <ig...@gmail.com> wrote:
> >
> > this vote is to release 1.3beta
> >
> > -igor
> >
>
>
Re: VOTE release 1.3beta
Posted by Igor Vaynberg <ig...@gmail.com>.
i think we should hold off on this vote because now there is a possibility
of all 2.0 backports making it into this branch after this release.
so for now i am changing my vote to -1 until we have decided on the roadmap
for the 1.3 branch.
-igor
On 3/7/07, Igor Vaynberg <ig...@gmail.com> wrote:
>
> this vote is to release 1.3beta
>
> -igor
>
Re: VOTE release 1.3beta
Posted by Johan Compagner <jc...@gmail.com>.
+1
On 3/8/07, Igor Vaynberg <ig...@gmail.com> wrote:
>
> this vote is to release 1.3beta
>
> -igor
>