+1 to use 1.2 as trunk because I believe it'll speed up the development.
Also +1 to Manfred's suggestion.
Regards,
Cagatay
Hi *,
I wonder if we should switch the trunk to be the 1.2 branch now, cause
our next release will surely be fully 1.2 compatible (Tomcat 6 is out
now, so the sooner we're done, the better)... We'll have a lot better
testing of 1.2 if we do it like this - wdyt?
regards,
Martin
--
+1
On 4/18/07, Martin Marinschek [EMAIL PROTECTED] wrote:
Hi *,
I wonder if we should switch the trunk to be the 1.2 branch now, cause
our next release will surely be fully 1.2 compatible (Tomcat 6 is out
now, so the sooner we're done, the better)... We'll have a lot better
testing of 1.2 if
Development
Onderwerp: Use 1.2 as current now
Hi *,
I wonder if we should switch the trunk to be the 1.2 branch now, cause
our next release will surely be fully 1.2 compatible (Tomcat 6 is out
now, so the sooner we're done, the better)... We'll have a lot better
testing of 1.2 if we do it like
Jetty is also ready ;)
On 4/18/07, Martin Marinschek [EMAIL PROTECTED] wrote:
Hi *,
I wonder if we should switch the trunk to be the 1.2 branch now, cause
our next release will surely be fully 1.2 compatible (Tomcat 6 is out
now, so the sooner we're done, the better)... We'll have a lot better
Ok, I'll start a vote - this is important enough that we should do a vote.
regards,
Martin
On 4/18/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Jetty is also ready ;)
On 4/18/07, Martin Marinschek [EMAIL PROTECTED] wrote:
Hi *,
I wonder if we should switch the trunk to be the 1.2
Hi *,
this is a formal vote on using the 1.2 branch as current now.
Steps in doing this:
- branch the current head as 1.1.5_1
- merge down the 1.2 branch to current head (that will be a lot of
work, I'll tackle it)
my +1 for doing this right now.
regards,
Martin
--
http://www.irian.at
JDK 1.4 compatibility?
Regards,
Erik-Berndt
-Oorspronkelijk bericht-
Van: Martin Marinschek [mailto:[EMAIL PROTECTED]
Verzonden: woensdag 18 april 2007 10:07
Aan: MyFaces Development
Onderwerp: Use 1.2 as current now
Hi *,
I wonder if we should switch the trunk to be the 1.2 branch now
What is in head that needs to be merged with the 1.2 branch? Why not
move head to 1.1.5_1 and move 1.2 to head?
I'm rather worried that the spec compliance will go down drastically
if there are extensive merges.
thanks
david jencks
On Apr 18, 2007, at 1:35 AM, Martin Marinschek wrote:
+1
This will help to finish the 1.2 development. I am not sure about a
complete merge of the head and the 1.2 branch (it is a lot of work!).
Maybe I will put the 1.2 branch as trunk and apply fixes (maybe
existing fixes in for 1.1) in the trunk as the issues arise?) However,
if you want to
On 18/04/07, Bruno Aranda [EMAIL PROTECTED] wrote:
+1
This will help to finish the 1.2 development. I am not sure about a
complete merge of the head and the 1.2 branch (it is a lot of work!).
Maybe I will put the 1.2 branch as trunk and apply fixes (maybe
Read I would put instead of I will
:-)
+1
On 4/18/07, Bruno Aranda [EMAIL PROTECTED] wrote:
On 18/04/07, Bruno Aranda [EMAIL PROTECTED] wrote:
+1
This will help to finish the 1.2 development. I am not sure about a
complete merge of the head and the 1.2 branch (it is a lot of work!).
Maybe I will put the 1.2 branch as trunk
+1 but without a merge of the 1.1 trunk into 1.2. We have to select
each individual issue. That is quite time consuming and shouldn't be
done with this step.
What about this:
move current trunk to a 1.1 branch and
move current 1.2 branch to trunk.
That is quite a small step without any side
Yes.
+1 for a switch
But let's discuss the how first.
Just had a look at the tomcat repo and I like the structure they use.
Main issue is that they do not name their trunk folder trunk but
rather give it a name corresponding to the actual major/minor version
(eg tc5.5.x). I like this idea.
And
+1 for making the 1.2 tag the main show.
I'm pretty confident that merging is no longer an option. The code bases
have been separate for more than six months and they are very different.
Plenty commits from several of us have touched 30 or 40 files at a time.
Dennis Byrne
On 4/18/07, Martin
Ok - first for merging:
I'll try to do it, but will refrain from doing so if it gets too hard.
We'll see if it works or if it doesn't.
second for branches/tags/trunk renaming:
I think that Manfred's suggestion has merits. We can go with this.
regards,
Martin
On 4/18/07, Dennis Byrne [EMAIL
+1 non-binding
Gary
-- Original message --
From: Martin Marinschek [EMAIL PROTECTED]
Hi *,
this is a formal vote on using the 1.2 branch as current now.
Steps in doing this:
- branch the current head as 1.1.5_1
- merge down the 1.2 branch to current
+1 for Manfreds suggestion.
2007/4/18, Manfred Geiler [EMAIL PROTECTED]:
Yes.
+1 for a switch
But let's discuss the how first.
Just had a look at the tomcat repo and I like the structure they use.
Main issue is that they do not name their trunk folder trunk but
rather give it a name
Manfred's idea sounds good to me. I especially appreciate that it
will cause minimal disruption.
Best wishes,
Paul
On Apr 18, 2007, at 7:21 AM, Manfred Geiler wrote:
Yes.
+1 for a switch
But let's discuss the how first.
Just had a look at the tomcat repo and I like the structure they
FAQ, news, and info
-Original Message-
From: Martin Marinschek [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 18, 2007 4:07 AM
To: MyFaces Development
Subject: Use 1.2 as current now
Hi *,
I wonder if we should switch the trunk to be the 1.2 branch now, cause
our next release
1.2 as current now
Hi *,
I wonder if we should switch the trunk to be the 1.2 branch now, cause
our next release will surely be fully 1.2 compatible (Tomcat 6 is out
now, so the sooner we're done, the better)... We'll have a lot better
testing of 1.2 if we do it like this - wdyt?
regards
: Use 1.2 as current now
Hi *,
I wonder if we should switch the trunk to be the 1.2 branch now, cause
our next release will surely be fully 1.2 compatible (Tomcat 6 is out
now, so the sooner we're done, the better)... We'll have a lot better
testing of 1.2 if we do it like this - wdyt?
regards
Will there be a clear process in place for those who are not using 1.2
yet to check and out and fix 1.1 issues? There's 80+ issues still
open.
My initial reaction was -1, but I'm tending more toward +1 now, so
long as 1.1 development can continue fairly easily. I'm hoping to be
able to switch
Manfred addressed my concerns that I just posted on the other thread.
+1
On 4/18/07, Paul McMahan [EMAIL PROTECTED] wrote:
Manfred's idea sounds good to me. I especially appreciate that it
will cause minimal disruption.
Best wishes,
Paul
On Apr 18, 2007, at 7:21 AM, Manfred Geiler wrote:
+1 for making 1.2 current.
+1 for Manfred's structure.
Once things have settled down (after Martin's attempted/successful merge),
I'm going to do another source code audit to ensure the licensing is all
compliant.
On 4/18/07, Paul McMahan [EMAIL PROTECTED] wrote:
Manfred's idea sounds good to
://www.JSFCentral.com - JavaServer Faces
FAQ, news, and info
* Sign up for the JSF Central newsletter!
http://oi.vresp.com/?fid=ac048d0e17 *
From: Zubin Wadia [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 18, 2007 10:27 AM
To: MyFaces Development; [EMAIL PROTECTED]
Subject: Re: Use 1.2 as current now
26 matches
Mail list logo
