I apologize for this remark. I should've taken a couple of breaths and
set gmail beer goggles up. Blame it on 4 weeks of baby invoked sleep
deprivation (and no, I didn't get a good nights sleep last night, 4am
when the little screamer finally slept—or I passed out... not sure
which one).
Martijn
m
-- sent from a wireless device
-Original Message-
From: Igor Vaynberg
Sent: Tuesday, August 04, 2009 10:01 AM
To: users@wicket.apache.org
Subject: Re: SVN URL for Wicket 1.4.0 sources?
nothing was lost
-igor
On Tue, Aug 4, 2009 at 6:51 AM, nino martinez
wael wrote:
> I too am a b
nothing was lost
-igor
On Tue, Aug 4, 2009 at 6:51 AM, nino martinez
wael wrote:
> I too am a bit worried.. A temporary fix could be to include the svn
> revision number for the release. Until this gets fixed.
>
> At work, we have a special profile for hudson which does the mvn
> release:prepare
thanks, my bad. got lost in all the building and rebuilding :)
-igor
On Tue, Aug 4, 2009 at 1:14 AM, Martijn
Dashorst wrote:
> fixed
>
> On Tue, Aug 4, 2009 at 9:57 AM, Thomas Singer wrote:
>> We include the Wicket sources using an SVN external. I now wanted to update
>> from the latest Wicket 1.
Oh and yes Wicket Devs you are doing a great job, without you there
would be no wicket.. And with no wicket no happy Nino:) But just
because something has done one way always it doesn't mean it's the
best way.
I believe creating a release should be as simple as a click :)
Regards Nino
2009/8/4 n
I too am a bit worried.. A temporary fix could be to include the svn
revision number for the release. Until this gets fixed.
At work, we have a special profile for hudson which does the mvn
release:prepare release:perform, which does the release and tag +
deploy in one go. The idea are if hudson c
On Tue, Aug 4, 2009 at 7:54 AM, Martijn
Dashorst wrote:
> We have documented, and established release procedures, which I
> followed, and then I must jump to your bidding?
Again, the point is that we shouldn't have to read the release
procedures to find the release tags. Maven/Subversion folks ju
http://svn.apache.org/repos/asf/wicket/releases/
--
Jeremy Thomerson
http://www.wickettraining.com
On Tue, Aug 4, 2009 at 3:20 AM, James
Carman wrote:
> That's not exactly fixing it, Martijn. The version in the pom still
> says "SNAPSHOT." What did you do, copy trunk?
>
> Who cut this releas
We have documented, and established release procedures, which I
followed, and then I must jump to your bidding?
Why is it so difficult to understand that our releases/* directory is
where we keep our release builds? And that they constitute our
official place for checking out release code?
svn co
Wow, that's a great way for a member of the development team to treat
a member of their user community. I'm not the only one with these
concerns. Why don't you bad-mouth Reinhard too?
On Tue, Aug 4, 2009 at 7:35 AM, Martijn
Dashorst wrote:
> Jeez, get a life...
>
> Martijn
>
> On Tue, Aug 4, 200
Jeez, get a life...
Martijn
On Tue, Aug 4, 2009 at 1:29 PM, James
Carman wrote:
> We shouldn't have to do this kind of research to know what's going on.
> That's the whole point.
>
> On Tue, Aug 4, 2009 at 7:25 AM, Martijn
> Dashorst wrote:
>> WTF?
>>
>> Read the commit messages and then tell me
We shouldn't have to do this kind of research to know what's going on.
That's the whole point.
On Tue, Aug 4, 2009 at 7:25 AM, Martijn
Dashorst wrote:
> WTF?
>
> Read the commit messages and then tell me that the 1.4.0 release is
> not an exact copy of sandbox/ivaynberg/wicket-1.4.0 ?
>
> Martijn
WTF?
Read the commit messages and then tell me that the 1.4.0 release is
not an exact copy of sandbox/ivaynberg/wicket-1.4.0 ?
Martijn
On Tue, Aug 4, 2009 at 12:33 PM, James
Carman wrote:
> Well, think about it this way. In the original message in this
> thread, Thomas Singer went looking for t
The same thing happened to me recently. I wanted to check out the
release tag and could not find it. I was already sort of surprised when
Igor mentioned he'd release from his private sandbox.
And now we have a 1.4.0 tag with a 1.4-SNAPSHOT in it and trunk which
still has 1.4-SNAPSHOT. That can
Well, think about it this way. In the original message in this
thread, Thomas Singer went looking for the 1.4.0 release stuff at the
URL:
http://svn.apache.org/repos/asf/wicket/tags/wicket-1.4.0
and it wasn't there. Why did he go there? Hmm. Maybe because
that's how everyone else does it?
tags/foo is as mutable as releases/foo
If a release needs to be cut, we can just do:
svn co https://svn.apache.org/repos/asf/wicket/releases/wicket-1.4.0
./release.sh
there are no changes to the release after it has been created. A
social convention, just as tagging it.
And this is the last thi
You might want to check the best practices document from the Incubator:
http://incubator.apache.org/guides/releasemanagement.html#best-practices-svn
On Tue, Aug 4, 2009 at 5:05 AM, Martijn
Dashorst wrote:
> Same for releases/wicket-1.4.0 after the release has been created.
>
> Martijn
>
> On Tue
On Tue, Aug 4, 2009 at 5:05 AM, Martijn
Dashorst wrote:
> We create a branch of off trunk for future maintenance of wicket 1.4,
> not from a release branch.
>
> wicket/branches/wicket-1.3.x -> created from wicket/trunk when we
> moved 1.3 to maintenance mode
> wicket/branches/wicket-1.4.x -> will
On Tue, Aug 4, 2009 at 5:00 AM, Martijn
Dashorst wrote:
> I can commit to a tag just as good as to the release branch. There is no
> spoon.
You're not answering the question, either. You haven't shown me how
you would easily re-create the released software as it was when it was
released with you
Same for releases/wicket-1.4.0 after the release has been created.
Martijn
On Tue, Aug 4, 2009 at 11:02 AM, James
Carman wrote:
> You aren't *supposed* to commit to tags, though.
>
> On Tue, Aug 4, 2009 at 5:00 AM, Martijn
> Dashorst wrote:
>> I can commit to a tag just as good as to the release
We create a branch of off trunk for future maintenance of wicket 1.4,
not from a release branch.
wicket/branches/wicket-1.3.x -> created from wicket/trunk when we
moved 1.3 to maintenance mode
wicket/branches/wicket-1.4.x -> will be created from wicket/trunk when
we move 1.4 to mainenance mode
w
Take a look at:
http://svnbook.red-bean.com/en/1.5/svn.branchmerge.tags.html#svn.branchmerge.tags.mksimple
"But wait a moment: isn't this tag creation procedure the same
procedure we used to create a branch? Yes, in fact, it is. In
Subversion, there's no difference between a tag and a branch. Bot
You aren't *supposed* to commit to tags, though.
On Tue, Aug 4, 2009 at 5:00 AM, Martijn
Dashorst wrote:
> I can commit to a tag just as good as to the release branch. There is no
> spoon.
>
> Martijn
>
> On Tue, Aug 4, 2009 at 10:56 AM, James
> Carman wrote:
>> Ok, so show me how you would re-cr
I can commit to a tag just as good as to the release branch. There is no spoon.
Martijn
On Tue, Aug 4, 2009 at 10:56 AM, James
Carman wrote:
> Ok, so show me how you would re-create the 1.4.0 release as it was
> when it was released. What SVN URL would you use to do that? If
> someone has check
I don't disagree that you guys are doing it this way. I'm saying it's
the wrong way to do it.
On Tue, Aug 4, 2009 at 4:45 AM, Martijn
Dashorst wrote:
> See also: http://cwiki.apache.org/confluence/display/WICKET/Releasing
>
> On Tue, Aug 4, 2009 at 10:41 AM, Martijn
> Dashorst wrote:
>> This has
Ok, so show me how you would re-create the 1.4.0 release as it was
when it was released. What SVN URL would you use to do that? If
someone has checked in changes into your "release branch", you're
going to need to find what version (SVN version) was used along with
that URL to re-create the 1.4.0
See also: http://cwiki.apache.org/confluence/display/WICKET/Releasing
On Tue, Aug 4, 2009 at 10:41 AM, Martijn
Dashorst wrote:
> This has been the process since I've been release manager. Create tag
> when we cut the release, create release branch where we build the
> release from the tag, release
This has been the process since I've been release manager. Create tag
when we cut the release, create release branch where we build the
release from the tag, release it. If there's a issue, repeat. This way
release artifacts don't pollute the main development stream, which is
rather normal SVN usag
Thank you.
Tom
Martijn Dashorst wrote:
> fixed
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
On Tue, Aug 4, 2009 at 4:25 AM, Martijn
Dashorst wrote:
> I beg to differ: the way it is currently setup is the way we have done
> it since inception of wicket.
No, I beg to differ. You haven't been doing it that way. Take a look at:
http://svn.apache.org/repos/asf/wicket/tags/wicket-1.3.6/pom.
see http://svn.apache.org/repos/asf/wicket/releases/wicket-1.4.0
Martijn
On Tue, Aug 4, 2009 at 10:25 AM, Martijn
Dashorst wrote:
> I beg to differ: the way it is currently setup is the way we have done
> it since inception of wicket.
>
> tag -> the moment where we cut the release
> release -> th
I beg to differ: the way it is currently setup is the way we have done
it since inception of wicket.
tag -> the moment where we cut the release
release -> the branch where the commits go to actually build the release
Martijn
On Tue, Aug 4, 2009 at 10:20 AM, James
Carman wrote:
> That's not exact
That's not exactly fixing it, Martijn. The version in the pom still
says "SNAPSHOT." What did you do, copy trunk?
Who cut this release? There should be a tag available to re-create
every release. I don't see tags for the last couple of rcs either.
This is quite a big no-no in Apache Land.
On
fixed
On Tue, Aug 4, 2009 at 9:57 AM, Thomas Singer wrote:
> We include the Wicket sources using an SVN external. I now wanted to update
> from the latest Wicket 1.3.* release
> (http://svn.apache.org/repos/asf/wicket/tags/wicket-1.3.6) to 1.4.0, but
> could not find a corresponding tag or branch.
34 matches
Mail list logo
