I suggest releasing from the head with a version of 1.1.5.  Releasing
the head as 1.1.4 to me is more confusing for the following reasons:
  o It is currently  called 1.1..5-SNAPSHOT
  o Issues are linked to 1.1.5-SNAPSHOT
  o Mailing list post refer to 1.1.5-SNAPSHOT
  o 1.1.4 has already gone through, although partially, a release process.
  o 1.1.4.1 has already gone through, although partially, a release process.
  o User searching the mailing list for 1.1.5 issues will have to determine
    if the post is for the first or second 1.1.5

I do not have a problem with a missing 1.1.4 release, Tomcat does this all the 
time.


The following statement is a concerning statement:
  "1.1.5 that is 100% compatible to the current core 1.1.5"
What does it mean?  Are their related Jira issues?

Paul Spencer


Manfred Geiler wrote:
The new tomahawk release number is a trade-off.
We must decide between
- releasing tomahawk 1.1.4 which is not compatible to core 1.1.4 and
therefore might confuse users
- skipping tomahawk 1.1.4, stay in sync with core and have a tomahawk
1.1.5 that is 100% compatible to the current core 1.1.5

WDYT?

--Manfred


On 2/23/07, Scheper, Erik-Berndt <[EMAIL PROTECTED]> wrote:

I agree.

The old 1.1.4 RC is getting really aged now.
However, it seems strange to just throw it away and follow-up 1.1.3 by 1.1.5

Regards,
Erik-Berndt


________________________________

Van: Cagatay Civici [mailto:[EMAIL PROTECTED]
Verzonden: vr 23-2-2007 9:27
Aan: MyFaces Development
Onderwerp: Re: Tomahawk 1.1.5 release plans?


Hi,

+1 for throwing away 1.1.4, creating a new branch using current trunk and releasing 1.1.4.

Cagatay


On 2/23/07, Manfred Geiler < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote:

Ok folks, I will try to start the release process for tomahawk next week.

        Well, regarding the branch there are various possibilities:
- use the already existing 1.1.4 branch from Nov. 2006 and release 1.1.4 - throw away existing 1.1.4 branch, create new branch and release 1.1.4
        - (optionally) throw away existing 1.1.4 branch, create new 1.1.5
        branch, skip version number 1.1.4 and release 1.1.5

        If we use one of the two "create new branch" strategies, which
        revision is stable enough. Current head?

        Thanks,
        Manfred



        On 2/22/07, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
        > +1 on this idea.
        >
> Tomahawk has settled down since the Dojo move and has been running > relatively stable. Best to ensure the next release is branched sometime > before any more big changes. (Tomahawk 1.1.4 RC is very good too) :)
        >
        > Paul Spencer wrote:
> > We just completed a MyFaces 1.1.5 release, which resolved blockers > > related to Tomahawk. Can we get a Tomahawk release done before we start
        > > changing things for Fusion?
        > >
        > >
        > > Paul Spencer
        > >
        > >
        > >
        >
        >
        >




Disclaimer:
This message contains information that may be privileged or confidential and is the property of Sogeti Nederland B.V. or its Group members. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.





Reply via email to