On Thu, Jan 19, 2023 at 6:01 PM Sebastiaan Couwenberg
wrote:
>
> On 1/19/23 10:26, Shengjing Zhu wrote:
> > On Thu, Jan 19, 2023 at 4:55 PM Paul Gevers wrote:
> >>> The history record for golang point release doesn't show regressions.
> >>
> >> That's good, are you talking about point release in
On 1/19/23 10:26, Shengjing Zhu wrote:
On Thu, Jan 19, 2023 at 4:55 PM Paul Gevers wrote:
The history record for golang point release doesn't show regressions.
That's good, are you talking about point release in general, or releases
to stable?
Missed this one. I'm talking about the
Control: tag -1 confirmed
Hi,
On 19-01-2023 10:22, Shengjing Zhu wrote:
On Thu, Jan 19, 2023 at 4:55 PM Paul Gevers wrote:
On 11-01-2023 09:32, Shengjing Zhu wrote:
This is a point release for golang 1.19 which happens today.
Where can I find the upstream policy on point release updates?
On Thu, Jan 19, 2023 at 4:55 PM Paul Gevers wrote:
> > The history record for golang point release doesn't show regressions.
>
> That's good, are you talking about point release in general, or releases
> to stable?
Missed this one. I'm talking about the upstream point release. We
haven't met
On Thu, Jan 19, 2023 at 4:55 PM Paul Gevers wrote:
>
> Dear Shengjing,
>
> On 11-01-2023 09:32, Shengjing Zhu wrote:
> > This is a point release for golang 1.19 which happens today.
>
> Where can I find the upstream policy on point release updates? Or, if
> not documented in one place, can you
Dear Shengjing,
On 11-01-2023 09:32, Shengjing Zhu wrote:
This is a point release for golang 1.19 which happens today.
Where can I find the upstream policy on point release updates? Or, if
not documented in one place, can you describe it? Is 1.19 a bug-fix only
branch already, or are new
Hi,
On 19-01-2023 03:17, Shengjing Zhu wrote:
Sorry not to make it clear. It's a pre-approval request.
Sorry from my side too, I forgot the context and only looked at the
subject and my first reply... (There was an other unblock request that
didn't require any action and I thought it was
Control: reopen -1
Control: retitle -1 [pre-approval] unblock: golang-1.19/1.19.5-1
Hi,
On Thu, Jan 19, 2023 at 3:45 AM Debian Bug Tracking System
> On Thu, 12 Jan 2023 16:28:51 +0100 Paul Gevers wrote:
> > But golang-1.19 is in sync between unstable and testing.
>
> Closing.
>
> Paul
Sorry
Am Thu, Jan 12, 2023 at 09:17:18PM +0100 schrieb Paul Gevers:
> On 12-01-2023 16:50, Shengjing Zhu wrote:
> > > But this bug report triggered me: did the golang security situation
> > > already improved during this release cycle. I may be misremembering, but
> > > I recall the problems on the
Hi Security team,
We stumbled upon golang...
On 12-01-2023 16:50, Shengjing Zhu wrote:
But this bug report triggered me: did the golang security situation
already improved during this release cycle. I may be misremembering, but
I recall the problems on the security archive side haven't been
On Thu, Jan 12, 2023 at 11:28 PM Paul Gevers wrote:
>
> Hi Shengjing,
>
> On 11-01-2023 09:32, Shengjing Zhu wrote:
> > Please unblock package golang-1.19
>
> But golang-1.19 is in sync between unstable and testing.
>
Because I haven't uploaded. This unblock request is for 1.19.5-1,
while
Hi Shengjing,
On 11-01-2023 09:32, Shengjing Zhu wrote:
Please unblock package golang-1.19
But golang-1.19 is in sync between unstable and testing.
This is a point release for golang 1.19 which happens today.
I suspect you're asking for an exception as golang is on our toolchain
list
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: golang-1...@packages.debian.org, z...@debian.org
Control: affects -1 + src:golang-1.19
Please unblock package golang-1.19
This is a point release for golang 1.19 which
13 matches
Mail list logo
