closed tickets

[G. M.-S.]

Is there an easy way to get a branch with all closed tickets merged?

Does it make sense to work with such a branch instead of the last beta branch?  I.e., for tickets positively reviewed or needing review.

Guillermo

[Dima Pasechnik]

On Thu, Jun 30, 2022 at 5:00 PM G. M.-S. <list...@gmail.com> wrote:
>
>
> Is there an easy way to get a branch with all closed tickets merged?
>
> Does it make sense to work with such a branch instead of the last beta branch? I.e., for tickets positively reviewed or needing review.

Volker is against this.
(while such a branch exists, it's likely to get rewritten a lot before
it becomes a beta)

>
> Guillermo
>
>
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CANnG18_3xVngMffm2Op5Qvx%2B-YBdQ8o6mXZMmuSL-D21gGyg2w%40mail.gmail.com.

[G. M.-S.]

Thanks Dima.

I asked because if the beta branch has problems you need to merge some tickets in order to make some progress with other tickets.

Last example:  #34025.

Guillermo

[Dima Pasechnik]

On Thu, Jun 30, 2022 at 5:11 PM G. M.-S. <list...@gmail.com> wrote:
>
>
> Thanks Dima.
>
> I asked because if the beta branch has problems you need to merge some tickets in order to make some progress with other tickets.
> Last example: #34025.

it would be harmless to merge the branch of #34025, i.e.
u/gh-DavidAyotte/fix_blocker_in_hecke_series
into the branch you work on.
(don't forget to specify #34025 as a dependency in the ticket description then)

Dima

>
> Guillermo
>
> On Thu, 30 Jun 2022 at 18:02, Dima Pasechnik <dim...@gmail.com> wrote:
>>
>> On Thu, Jun 30, 2022 at 5:00 PM G. M.-S. <list...@gmail.com> wrote:
>> >
>> > Is there an easy way to get a branch with all closed tickets merged?
>> >
>> > Does it make sense to work with such a branch instead of the last beta branch? I.e., for tickets positively reviewed or needing review.
>>
>> Volker is against this.
>> (while such a branch exists, it's likely to get rewritten a lot before
>> it becomes a beta)
>
>

> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CANnG1897TG_PUORSnH3V1QnpKwsEv4GVqAwK5Rn3E9wAMLgqqQ%40mail.gmail.com.

[Kwankyu Lee]

On Friday, July 1, 2022 at 1:02:32 AM UTC+9 dim...@gmail.com wrote:

Volker is against this.
(while such a branch exists, it's likely to get rewritten a lot before
it becomes a beta)

When I first saw the notice of merge conflicts with Volker's branch and my positively-reviewed ticket, I thought wrongly that I need to resolve the merge conflicts with the Volker's branch. I didn't realize that I was supposed to identify those tickets among the tickets merged to Volker's branch that conflict with my ticket, and put those tickets as dependencies to my ticket. I think this should be explained somewhere, perhaps in the  notice itself.

[Kwankyu Lee]

On Saturday, July 2, 2022 at 12:33:38 PM UTC+9 Kwankyu Lee wrote:

... I think this should be explained somewhere, perhaps in the  notice itself.

Added to 

https://trac.sagemath.org/ticket/33849

which needs review.