[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Branching and tagging CDT 6.0
|
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schorn, Markus
> Sent: June-22-09 4:21 AM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Branching and tagging CDT 6.0
>
> There is no need to clone the bug. If a bug is fixed in
> 6.0.x, everyone
> will expect it to be fixed in 6.x, also.
>
> ==> Without any exception, every fix in the cdt_6_0 branch needs to be
> done in parallel in HEAD.
That makes sense.
I am a big fan of attaching any code submission as a patch to a bug.
It makes reviewing much easier for others, as well as going back
to a bug much easier later on.
With that in mind, I suggest that those that do include their patch
in bugs, would indicate that the patch applies to both cdt_6_0 and HEAD.
And if a different patch is needed for the two branches, it would
be nice to attach both versions of the patch.
Thanks
Marc
>
> Markus.
>
> > -----Original Message-----
> > From: cdt-dev-bounces@xxxxxxxxxxx
> > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam
> > Sent: Monday, June 22, 2009 3:40 AM
> > To: CDT General developers list.
> > Subject: RE: [cdt-dev] Branching and tagging CDT 6.0
> > Importance: Low
> >
> > > -----Original Message-----
> > > From: cdt-dev-bounces@xxxxxxxxxxx
> > > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Elena Laskavaia
> > > Sent: June-19-09 4:21 PM
> > > To: CDT General developers list.
> > > Subject: Re: [cdt-dev] Branching and tagging CDT 6.0
> > >
> > > Critical and serious bugs, that do not change UI and public
> > API go to
> > > 6.0.1 which is cdt_6_0 branch, same patches should be
> committed to
> > > head.
> >
> > Sounds good.
> > Do you clone bugs when fixing both in HEAD and in 6_0, so
> > that we can set the target correctly for each one?
> >
> > Thanks
> >
> >
> >
> > Could be exceptions
> > > - to discuss on mailing list.
> > >
> > > Everything else goes to HEAD.
> > >
> > >
> > > Marc Khouzam wrote:
> > > > Newbie question:
> > > >
> > > > What goes into cdt_6_0 and what goes into HEAD?
> > > > I've got bugs to commit but I also got a new feature I'm
> > > going to start.
> > > >
> > > > Thanks
> > > >
> > > > Marc
> > > >
> > > >
> > > --------------------------------------------------------------
> > > ----------
> > > > *From:* cdt-dev-bounces@xxxxxxxxxxx
> > > > [mailto:cdt-dev-bounces@xxxxxxxxxxx] *On Behalf Of
> > *Vivian Kong
> > > > *Sent:* June-18-09 10:51 AM
> > > > *To:* cdt-dev@xxxxxxxxxxx
> > > > *Subject:* [cdt-dev] Branching and tagging CDT 6.0
> > > >
> > > > I've tagged the RC5/Final build as *CDT_6_0_0*
> > (I200906161748).
> > > > Branch *cdt_6_0* is now ready for CDT 6.0.1 check-ins.
> > > >
> > > > Regards,
> > > >
> > > > Vivian Kong
> > > > IBM Eclipse CDT
> > > > IBM Canada Toronto Lab
> > > >
> > > >
> > > >
> > > --------------------------------------------------------------
> > > ----------
> > > >
> > > > _______________________________________________
> > > > cdt-dev mailing list
> > > > cdt-dev@xxxxxxxxxxx
> > > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > > _______________________________________________
> > > cdt-dev mailing list
> > > cdt-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
