| Re: [escet-dev] Remove install.asciidoc.org? |
|
Hi Bert,
I updated the development process in issue #24. I opted for the mostly already described, and preferred, 2nd option.
Dennis
Van: escet-dev <escet-dev-bounces@xxxxxxxxxxx> namens Beek, Bert van <D.A.v.Beek@xxxxxx>
Verzonden: donderdag 18 maart 2021 13:46 Aan: escet developer discussions <escet-dev@xxxxxxxxxxx> Onderwerp: Re: [escet-dev] Remove install.asciidoc.org? Hi Dennis,
So, this means that the description should be changed to reflect the first option: creating the branch and merge request in one action, thus avoiding errors such as the one I made in which I ended up with two branches? That would make sense to me. Bert > On 18 Mar 2021, at 11:04, Dennis Hendriks <dh_tue@xxxxxxxxxxx> wrote: > > Hi Bert, > > I think the 2nd option is what is currently described in our development process. I think we make it only more complex by having multiple options in there. I would prefer to only describe the recommended option. > > Dennis > > Van: escet-dev <escet-dev-bounces@xxxxxxxxxxx> namens Beek, Bert van <D.A.v.Beek@xxxxxx> > Verzonden: donderdag 18 maart 2021 10:04 > Aan: escet developer discussions <escet-dev@xxxxxxxxxxx> > Onderwerp: Re: [escet-dev] Remove install.asciidoc.org? > > Hi Dennis, I had indeed just read it, but your explanation about the main two options to deal with merge requests from your previous mail is not in the development process. At least I did not find it there. Perhaps add it? > > Bert > > > On 18 Mar 2021, at 09:58, Dennis Hendriks <dh_tue@xxxxxxxxxxx> wrote: > > > > Hi Bert, > > > > Our development process is explained here: https://www.eclipse.org/escet/escet/#developer-development-process-chapter-index > > > > Dennis > > > > Van: escet-dev <escet-dev-bounces@xxxxxxxxxxx> namens Dennis Hendriks <dh_tue@xxxxxxxxxxx> > > Verzonden: donderdag 18 maart 2021 09:57 > > Aan: escet developer discussions <escet-dev@xxxxxxxxxxx> > > Onderwerp: Re: [escet-dev] Remove install.asciidoc.org? > > > > Hi Bert, > > > > The 2 main options: > > • Create a merge request and branch at once, from the issue. It will be a 'Draft' merge request. Once all the work is done, change the status, removing the 'Draft' status. > > • Create the branch from the issue (and only the branch). Once all the work is done, create a merge request for the branch. > > The 1st option leads to more mails, as every commits leads to a mail. For the 2nd option, you only get mails once the merge request is created, and it is thus in review. > > > > Therefore I prefer the first option. > > > > Dennis _______________________________________________ escet-dev mailing list escet-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/escet-dev |