Also I don't think we've even checked in single fix into the branch
yet.  So we're only talking one or two fixes that weren't already in
the trunk.

sean

On 9/28/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> The plan was to do a release candidate over the weekend after using
> the rest of this week to fix last minute "must fix" bugs.  We could
> move that up a bit.  What if we build the RC on Friday?  That gives us
> through tomorrow to fix everything that needs to go in.
>
> Once we build the RC we can merge the fixes down.  The users of the
> nightly build will only be without these fixes for a few days.
>
> sean
>
> On 9/28/05, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > Honestly, I just think we should push this one out.
> >
> > there have been 64 issues fixed since 1.1.0, that should be enough.
> >
> > regards,
> >
> > Martin
> >
> > On 9/28/05, Bill Dudney <[EMAIL PROTECTED]> wrote:
> > > problem is that merging is a pain in the neck. we can do it its just
> > > a pain
> > >
> > > So we need to push out the release sooner rather than later.
> > >
> > > I've not seen any discussion on the bug list to get fixed.
> > >
> > > TTFN,
> > >
> > > -bd-
> > > On Sep 28, 2005, at 2:11 AM, Mathias Brökelmann wrote:
> > >
> > > > IMO it´s better if we fix a bug in both trunk and the branch. Trunk is
> > > > used by more users (either by svn or through the nightlies). This will
> > > > give us more feedback if a bugfix introduces a new bug.
> > > >
> > > > 2005/9/28, Sean Schofield <[EMAIL PROTECTED]>:
> > > >
> > > >> Bugs that have been introduced on the branch (ex. MYFACES-634) should
> > > >> obviously be fixed on the branch.
> > > >>
> > > >> Additional Rule of thumb: If the bug is going to be fixed in the
> > > >> branch fix it *only* in the branch.  Do not fix in the trunk.  We
> > > >> will
> > > >> merge into the trunk in a few weeks when we are done.
> > > >>
> > > >> sean
> > > >>
> > > >> On 9/27/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> > > >>
> > > >>> I changed all of the issues fixed in nightly to be version 1.1.1 (by
> > > >>> renaming the existing nightly version in JIRA and creating a new
> > > >>> one.)
> > > >>>
> > > >>> So we can now search on a list of things that are fixed in that
> > > >>> version and eventually generate release notes.
> > > >>>
> > > >>> Thanks Bill for the branch (its tedious - I know.)
> > > >>>
> > > >>> sean
> > > >>>
> > > >>> On 9/27/05, Bill Dudney <[EMAIL PROTECTED]> wrote:
> > > >>>
> > > >>>> branch created
> > > >>>>
> > > >>>> If you want a bug to be fixed in the 1_1_1 release you must apply
> > > >>>> your changes to the release/branches/1_1_1 branch in SVN.
> > > >>>>
> > > >>>> Please limit the changes to the ones identified in the other thread
> > > >>>> titled '[proposal] Branch Content'.
> > > >>>>
> > > >>>> Thanks!
> > > >>>>
> > > >>>> -bd-
> > > >>>>
> > > >>>> On Sep 27, 2005, at 10:21 AM, Sean Schofield wrote:
> > > >>>>
> > > >>>>
> > > >>>>> Go for it.
> > > >>>>>
> > > >>>>> sean
> > > >>>>>
> > > >>>>> On 9/27/05, Bill Dudney <[EMAIL PROTECTED]> wrote:
> > > >>>>>
> > > >>>>>
> > > >>>>>> Hi Sean,
> > > >>>>>>
> > > >>>>>> I need about 30 more minutes to finish up something. I'll
> > > >>>>>> start the
> > > >>>>>> branch around 1:00 EST. Is that OK with everyone?
> > > >>>>>>
> > > >>>>>> TTFN,
> > > >>>>>>
> > > >>>>>> -bd-
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > Mathias
> > > >
> > >
> > >
> >
> >
> > --
> >
> > http://www.irian.at
> > Your JSF powerhouse -
> > JSF Trainings in English and German
> >
>

Reply via email to