Including the Zone lines? I suppose if Issue 4501 decides to drop them, we can ...
12 years, 5 months ago
(2012-12-15 18:24:23 UTC)
#3
Including the Zone lines?
I suppose if Issue 4501 decides to drop them, we can remove them from
next.txt.
In general I still don't understand our policy (or whether there is one) of
when we update next.txt.
On Sat, Dec 15, 2012 at 10:16 AM, Russ Cox <rsc@golang.org> wrote:
> LGTM
>
On Sun, Dec 16, 2012 at 2:24 AM, Brad Fitzpatrick <bradfitz@golang.org>wrote: > I suppose if ...
12 years, 5 months ago
(2012-12-15 18:35:07 UTC)
#4
On Sun, Dec 16, 2012 at 2:24 AM, Brad Fitzpatrick <bradfitz@golang.org>wrote:
> I suppose if Issue 4501 decides to drop them, we can remove them from
> next.txt.
>
i think so. I also think we need to carefully review next.txt before Go 1.1
release regardless
of whether we update it or not, so just silent all the 318 lines of warning
text during every
build is worthwhile for now.
Anyone can update next.txt as often or rarely as they want. Being in next.txt does ...
12 years, 5 months ago
(2012-12-16 23:11:28 UTC)
#5
Anyone can update next.txt as often or rarely as they want.
Being in next.txt does not mean we promise it will be in Go 1.1,
just that we know it was an addition and don't need to see it at
the end of all.bash.
I have only one rule for next.txt: update it in CLs by itself, so
that trying to patch CLs into point releases does not run into
merge conflicts trying to update next.txt.
Russ
Thanks. Makes sense. On Dec 16, 2012 3:11 PM, "Russ Cox" <rsc@golang.org> wrote: > Anyone ...
12 years, 5 months ago
(2012-12-16 23:13:09 UTC)
#6
Thanks. Makes sense.
On Dec 16, 2012 3:11 PM, "Russ Cox" <rsc@golang.org> wrote:
> Anyone can update next.txt as often or rarely as they want.
> Being in next.txt does not mean we promise it will be in Go 1.1,
> just that we know it was an addition and don't need to see it at
> the end of all.bash.
>
> I have only one rule for next.txt: update it in CLs by itself, so
> that trying to patch CLs into point releases does not run into
> merge conflicts trying to update next.txt.
>
> Russ
>
Issue 6935061: code review 6935061: api/next.txt: update
(Closed)
Created 12 years, 5 months ago by minux1
Modified 12 years, 5 months ago
Reviewers:
Base URL:
Comments: 0