Re: [Wicket-user] wicket-stuff tags/branches

Gili Wed, 14 Dec 2005 09:40:03 -0800

Martijn,

I think it would be useful for at least *some* of the wicket-stuff codeto be synched with wicket branches. Wicket's "head" branch is ratherunstable at the moment (due to niceurl support) so I'd like to useWICKET_1_1. The problem is that if wicket-stuff depends upon wicket's"head" branch I can't do this.

All this is to say that I am +1 for synching the hibernate 3.0 moduleagainst wicket (Igor did this last night).


Gili

Juergen Donnerstag wrote:

Some are really experimental only with little documentation and more
meant to share ideas rather than being "products"

Juergen


On 12/14/05, Igor Vaynberg <[EMAIL PROTECTED]> wrote:

a lot of those projects have been stable for a while, so why havent they
been released?


-Igor


On 12/14/05, Martijn Dashorst < [EMAIL PROTECTED]> wrote:

As long as there is no marked release, then yes. It is up to the


maintainers of each project to provide one. As far as I know, the only
project that has made a release using Wicket 1.1 is the Contrib Dojo
project. As such that is the only project that has a label attached, and I
don't think it is Wicket 1.1.

I really don't know why we should even bother tagging the wicket stuff


projects with a WICKET_1_1 tag. Each project has its own release cycle, and
as such its own tagging mechanism. There is absolutely no reason to tag a
non released project with WICKET_1_1. That code may not even compile with
wicket 1.1!

Martijn




On 12/14/05, Igor Vaynberg <[EMAIL PROTECTED] > wrote:

so the mentality is use cvs wicket-stuff at your own risk?

-Igor




On 12/14/05, Martijn Dashorst < [EMAIL PROTECTED]> wrote:

The Wicket stuff modules weren't released at all, so there was NO NEED


to do so. These are separate projects, with their own release cycle. Each of
those projects could depend on a different version of wicket, depending on
the speed of the maintainer.

So, there is no need to fix anything.

Martijn



On 12/13/05, Igor Vaynberg < [EMAIL PROTECTED]> wrote:

after discussing on irc we found out that the actual problem was


that we did not tag the wicket-stuff modules with WICKET_1_1 when we
released. i think that should be done for future releases.

-Igor




On 12/13/05, Gili <[EMAIL PROTECTED]> wrote:

Hi,

   wicket-stuff has:

WICKET_1_1
WICKET_1_1_BRANCH
HEAD
head

   which is rather confusing and inconsistent with the


tags/branches in the "wicket" repository. Who is CVS admin for wicket-stuff?
Can this be cleaned up?

Gili
--
http://www.desktopbeautifier.com/



--
Living a wicket life...

Martijn Dashorst -


http://www.jroller.com/page/dashorst

Wicket 1.1 is out:


http://wicket.sourceforge.net/wicket-1.1



--
Living a wicket life...

Martijn Dashorst - http://www.jroller.com/page/dashorst

Wicket 1.1 is out:


http://wicket.sourceforge.net/wicket-1.1




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user


--
http://www.desktopbeautifier.com/


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] wicket-stuff tags/branches

Reply via email to