axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Afkham Azeez" <afk...@gmail.com>
Subject Re: [axis2] Changes on the 1_2 branch (VOTE)
Date Sat, 14 Apr 2007 14:41:11 GMT
Do the fixes in the branch need to be necessarily carried out on the trunk
as well. I'm asking this since we'd be merging the code in the branch with
the trunk eventually.

-- Azeez

On 4/13/07, Glen Daniels <glen@thoughtcraft.com> wrote:
>
> Hi Jeremy!
>
> This sounds like a great policy to me.  Can we VOTE on this and then
> make sure we get a serious "Developer Guidelines" page on the website
> (right now that link just gets you a mail guidelines page), including
> this, coding conventions, build policies, etc...?
>
> I'd remove the third bullet though.  I don't think we want to put that
> much responsibility on the reporter - they're not necessarily Axis2
> developers, they might just be poor users with bugs.  The reporter
> should check that the version they're using has been fixed and the
> assignee should have already taken care of any cross-branch merging
> before resolving the issue.  I don't ever want to get into a situation
> where we blame someone who's not on the team for not verifying something.
> :)
>
> That said, +1 from me!
>
> --Glen
>
> Jeremy Hughes wrote:
> > Just a thought ... could JIRA be used in a way that means we can see
> > that fixes put into a branch have also gone into the trunk, rather
> > than assuming it. e.g. for a JIRA that needs to be fixed in 1.2 branch
> > and trunk, set the 'fix for' field of the JIRA to be both "1.2" and
> > "nightly" (which I assume represents trunk). Then ...
> >
> > * It's the RM's responsibility to ensure all the JIRA's being fixed in
> > 1.2 have both "1.2" and "nightly" values in the 'fix for' field.
> > * It's the assignee's responsibility to check in the fix to all the
> > branches in the 'fix for' field.
> > * It's the reporter's responsibility when closing the JIRA to check
> > that the fix has been checked in to all the branches in the 'fix for'
> > field.
> >
> > Any thoughts?
> >
> > Cheers,
> > Jeremy
> >
> > On 07/04/07, Glen Daniels <glen@thoughtcraft.com> wrote:
> >> Hi all:
> >>
> >> Just checking in - is everyone who's making changes on the 1_2 branch
> >> merging them over to the trunk?  We don't want to fix bugs only on the
> >> branch, lest they come back to bite us later down the line....
> >>
> >> If you've made fixes for the release and HAVEN'T yet merged them over,
> >> please consider doing so soon.  Otherwise, please ignore this friendly
> >> reminder.
> >>
> >> Thanks,
> >> --Glen
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Thanks
Afkham Azeez

http://www.wso2.org
GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760

Mime
View raw message