Yep, I'll do the clean up.
branches/WICKET_1_2_1 will go to /releases/wicket-1.2.1
Martijn
On 8/26/06, Frank Bille <[EMAIL PROTECTED]> wrote:
> Good. But I would like to propose this structure instead:
>
>
> [just kidding] ;)
>
>
>
> Martijn, do you also clean up the repository? I mean move
> br
Good. But I would like to propose this structure instead:[just kidding] ;)Martijn, do you also clean up the repository? I mean move branches/WICKET_1_2_1 to tags or delete it etc.?Frank
On 8/25/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All,We've discussed this over and over, and we keep runni
/releases is where martijn will be tweaking various things for the releases - such as readme.txt, pom.xml, etconce he built the releases no one should touch that branch - it becomes read only and saves the exact state of the repo for the release that is in the .zip file
-IgorOn 8/25/06, Johan Compa
all fine by me but just curious for one thing:Who is doing that commit to releses/wicket-1.2.2 (after which it is readonly)?Because i think you can have a working copy of the changes you want in that release branch/tag
and commit that to a tag saying that you want to commit the working copy. I don'
Martijn Dashorst wrote:
> All,
>
> We've discussed this over and over, and we keep running in circels,
> having the same conversation and arguments over and over.
>
> This is how we're going to do it, it is a combination of the things
> that have passed.
>
> branches/wicket-1.x<- wicket
