[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [birt-dev] Bugzilla bug marked as FIXED butthere isnocorresponding check-ins to HEAD
|
Thanks Wenfeng for opening up the discussion.
One suggestion is that if a committer is having
trouble
checking into CVS, perhaps he/she can submit the patch
and attach to the bugzilla entry and send a note to
birt-dev to have another committer in another region
to commit the change for him/her and record who the
patch was contributed by in CVS. Then things can
proceed accordingly.
Regards,
Yip Ng
--- Wenfeng Li <wli@xxxxxxxxxxx> wrote:
>
> Since large scale internet outage is a relatively
> rare case
> (hopefully), it is hard to justify a new state value
> to the Eclipse CVS
> admin. Without this outage, typically the fix is
> checked into Eclipse
> CVS before bugzilla is updated.
>
> I think a comment in bugzilla is a good interim
> solution.
>
> Wenfeng
>
> -----Original Message-----
> From: birt-dev-bounces@xxxxxxxxxxx
> [mailto:birt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Sunitha Kambhampati
> Sent: Thursday, January 11, 2007 3:58 PM
> To: birt-dev@xxxxxxxxxxx
> Subject: Re: [birt-dev] Bugzilla bug marked as FIXED
> butthere
> isnocorresponding check-ins to HEAD
>
>
> Thanks Wenfeng for the response and for opening up
> the discussion.
>
> I tend to think that it is best for the bugzilla
> state to always reflect
>
> the status of the eclipse CVS repository.
> The committer should make sure that the changes go
> up to the CVS first
> before marking the bug as fixed.
>
> At Apache projects, bugs can have a status of 'in
> progress' set to
> indicate that the bug is being worked on. I looked
> at
>
https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#resolution
> and
> dont see any such state. One question is -- Is it
> even possible to add a
>
> state in bugzilla to have 'In Progress' status. If
> yes, then maybe we
> can use this to indicate that progress is being made
> on the bug.
>
> If this is not possible, maybe just a comment by the
> committer in the
> bugzilla saying 'fix looks good and will commit when
> CVS repository can
> be accessed' or something like that so that the
> contributor knows what
> is happening to his/her patch.
>
> Thoughts/comments?
>
> regards,
> Sunitha.
>
> Wenfeng Li wrote:
>
> >Any suggestions?
> >
> >Technically, the bug status setting to fixed is
> correct as long as the
> >bug is fixed in the target milestone build when
> that build is released.
>
> >But I can see the need of telling if the fix is
> already in CVS and if
> >it is already incorporated into the daily build.
> >
> >Wenfeng
> >
> >-----Original Message-----
> >From: birt-dev-bounces@xxxxxxxxxxx
> >[mailto:birt-dev-bounces@xxxxxxxxxxx]
> >On Behalf Of Yip Ng
> >Sent: Thursday, January 11, 2007 2:45 PM
> >To: birt-dev@xxxxxxxxxxx
> >Subject: RE: [birt-dev] Bugzilla bug marked as
> FIXED but there
> >isnocorresponding check-ins to HEAD
> >
> >
> >Hi Wenfeng:
> >
> >Thanks for the info. Given that we don't know when
> >the network issue will be resolved, is it possible
> to
> >remark the bug in some other open status other than
> >FIXED to reflect the actual current Bugzilla status
> >since the code patch are not sync up to the Eclipse
> >CVS?
> >
> >
> >Regards,
> >Yip Ng
> >
> >--- Wenfeng Li <wli@xxxxxxxxxxx> wrote:
> >
> >
> >
> >>HI, Yip
> >>
> >>Due to the internet issue between North America
> and
> >>China, our
> >>committers at Shanghai can not check in to the
> >>Eclipse CVS server. This
> >>bug fix is checked into to a local backup CVS
> >>server, once the network
> >>issue is addressed, it will be checked into
> Eclipse
> >>CVS.
> >>
> >>Wenfeng
> >>
> >>-----Original Message-----
> >>From: birt-dev-bounces@xxxxxxxxxxx
> >>[mailto:birt-dev-bounces@xxxxxxxxxxx]
> >>On Behalf Of Yip Ng
> >>Sent: Thursday, January 11, 2007 10:40 AM
> >>To: birt-dev@xxxxxxxxxxx
> >>Subject: [birt-dev] Bugzilla bug marked as FIXED
> but
> >>there is
> >>nocorresponding check-ins to HEAD
> >>
> >>
> >>Hi birt-dev,
> >>
> >>I have a question on marking a BIRT bug as FIXED
> for
> >>its resolution. I have reported a bug (bugzilla
> >>168018), it was marked as FIXED but I do not see
> any corresponding
> >>check-ins to CVS HEAD, so I wasn't able to verify
> >>the fix or provide
> >>comments. I would expect the changes to have been
> >>committed to HEAD
> >>before marking the resolution as FIXED, so I am
> abit
> >>confused about the
> >>procedures here. Can someone clarify this?
> >>How does this work in general?
> >>
>
>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=168018
> >>
> >>Regards,
> >>Yip Ng
> >>
> >>
> >>
> >>
> >>
> >>
> >>
>
>_______________________________________________________________________
> _
> >
> >
> >>____________
> >>Yahoo! Music Unlimited
> >>Access over 1 million songs.
> >>http://music.yahoo.com/unlimited
> >>_______________________________________________
> >>birt-dev mailing list
> >>birt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/birt-dev
> >>_______________________________________________
> >>birt-dev mailing list
> >>birt-dev@xxxxxxxxxxx
> >>https://dev.eclipse.org/mailman/listinfo/birt-dev
> >>
> >>
> >>
> >
> >
> >
> >
>
>_______________________________________________________________________
> _
> >____________
> >Never Miss an Email
> >Stay connected with Yahoo! Mail on your mobile.
> Get started!
> >http://mobile.yahoo.com/services?promote=mail
> >_______________________________________________
> >birt-dev mailing list
> >birt-dev@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/birt-dev
> >_______________________________________________
> >birt-dev mailing list
> >birt-dev@xxxxxxxxxxx
> >https://dev.eclipse.org/mailman/listinfo/birt-dev
> >
>
=== message truncated ===
____________________________________________________________________________________
Don't get soaked. Take a quick peak at the forecast
with the Yahoo! Search weather shortcut.
http://tools.search.yahoo.com/shortcuts/#loc_weather