[prev in list] [next in list] [prev in thread] [next in thread]
List: flightgear-devel
Subject: Re: [Flightgear-devel] What is the FlightGear release plan ?
From: Bertrand Coconnier <bcoconni () gmail ! com>
Date: 2020-10-31 17:45:27
Message-ID: CAHpp8MG-Aho4qg1Gq=wBStScOHXBU0viyuvEj=OfPxaqi7fJ1A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Le sam. 31 oct. 2020 à 17:45, James Turner <james@flightgear.org> a écrit :
>
>
> On 31 Oct 2020, at 16:36, Bertrand Coconnier <bcoconni@gmail.com> wrote:
>
> BTW whatever the option taken, I will have to produce the patches to
> extract the relevant bug fixes from the monolithic commits of the upgrades
> of JSBSim release version in 'next'. Unless you (the FlightGear devs)
> manage to do that on your own, I guess I will have to be involved in the
> LTS maintenance in all scenarios.
>
>
> I'd recommend to keep each fix as a separate commit in the JSBsim repo:
> then we can at least include ‘corresponds to JSBsim commit
> shadshfdhsjfhdjf' in the commit to Flightgear.
>
I will not make much difference to me: bug fixes will be extracted from
JSBSim 'master' branch in any case, not from FlightGear 'next' branch.
> Having to extract individual fixes from a large JSBsim commit sounds ..
> not fun at all.
>
> This is a god example of why it's always better to make more, fine-grained
> commits, than a large ones.
>
I am getting a bit confused here. You said that "We obviously don't want to
track the main dev branch" (I guess you are talking about JSBSim main
branch) so I understood that you don't want to have every single JSBSim
commit copied to FlightGear 'next' ? I guess bug fixes can be introduced
individually but regarding major, potentially breaking, changes that's
another story: such changes need several commits to mature and I would
prefer to push them to FlightGear as big monolithic commits.
Regards,
Bertrand.
[Attachment #5 (text/html)]
<div dir="ltr"><div dir="ltr">Le sam. 31 oct. 2020 Ã 17:45, James Turner <<a \
href="mailto:james@flightgear.org">james@flightgear.org</a>> a écrit \
:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px \
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div \
style="overflow-wrap: break-word;"><br><div><br><blockquote type="cite"><div>On 31 \
Oct 2020, at 16:36, Bertrand Coconnier <<a href="mailto:bcoconni@gmail.com" \
target="_blank">bcoconni@gmail.com</a>> wrote:</div><br><div><span \
style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal \
;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transf \
orm:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">BTW \
whatever the option taken, I will have to produce the patches to extract the relevant \
bug fixes from the monolithic commits of the upgrades of JSBSim release version in \
'next'. Unless you (the FlightGear devs) manage to do that on your own, I \
guess I will have to be involved in the LTS maintenance in all \
scenarios.</span></div></blockquote></div><br><div>I'd recommend to keep each fix as \
a separate commit in the JSBsim repo: then we can at least include ‘corresponds to \
JSBsim commit shadshfdhsjfhdjf' in the commit to \
Flightgear.</div></div></blockquote><div><br></div><div>I will not make much \
difference to me: bug fixes will be extracted from JSBSim 'master' branch in \
any case, not from FlightGear 'next' branch.</div><div> </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: \
break-word;"><div>Having to extract individual fixes from a large JSBsim commit \
sounds .. not fun at all.<br></div><div><br></div><div>This is a god example of why \
it's always better to make more, fine-grained commits, than a large \
ones.</div></div></blockquote><div><br></div><div>I am getting a bit confused here. \
You said that "We obviously don't want to track the main dev branch" (I \
guess you are talking about JSBSim main branch) so I understood that you don't \
want to have every single JSBSim commit copied to FlightGear 'next' ? I guess \
bug fixes can be introduced individually but regarding major, potentially breaking, \
changes that's another story: such changes need several commits to mature and I \
would prefer to push them to FlightGear as big monolithic \
commits.</div><div><br></div><div>Regards,</div><div><br></div><div>Bertrand.</div></div></div>
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic