Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reorganize the 3.0 Misc/NEWS file #46563

Closed
gvanrossum opened this issue Mar 16, 2008 · 8 comments
Closed

Reorganize the 3.0 Misc/NEWS file #46563

gvanrossum opened this issue Mar 16, 2008 · 8 comments
Labels
docs Documentation in the Doc dir release-blocker

Comments

@gvanrossum
Copy link
Member

BPO 2310
Nosy @gvanrossum, @birkenfeld, @tiran, @benjaminp

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2008-08-16.16:16:05.253>
created_at = <Date 2008-03-16.21:25:57.887>
labels = ['release-blocker', 'docs']
title = 'Reorganize the 3.0 Misc/NEWS file'
updated_at = <Date 2008-08-16.16:16:05.214>
user = 'https://github.com/gvanrossum'

bugs.python.org fields:

activity = <Date 2008-08-16.16:16:05.214>
actor = 'gvanrossum'
assignee = 'none'
closed = True
closed_date = <Date 2008-08-16.16:16:05.253>
closer = 'gvanrossum'
components = ['Documentation']
creation = <Date 2008-03-16.21:25:57.887>
creator = 'gvanrossum'
dependencies = []
files = []
hgrepos = []
issue_num = 2310
keywords = []
message_count = 8.0
messages = ['63597', '63720', '63729', '64253', '64259', '70756', '71210', '71222']
nosy_count = 4.0
nosy_names = ['gvanrossum', 'georg.brandl', 'christian.heimes', 'benjamin.peterson']
pr_nums = []
priority = 'release blocker'
resolution = 'wont fix'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue2310'
versions = ['Python 3.0']

@gvanrossum
Copy link
Member Author

The 3.0 Misc/NEWS file is a mess. It is vastly incomplete because it
usually gets skipped during merges rather than resolving the conflicts.

@gvanrossum gvanrossum added the docs Documentation in the Doc dir label Mar 16, 2008
@birkenfeld
Copy link
Member

Stuff ported from 2.6 needn't be in the 3.0 NEWS, needs it?

@gvanrossum
Copy link
Member Author

Correct. Martin & I just discussed this. We'll empty the current 3.0
NEWS file and start adding stuff consistently from 3.0a3, but skipping
stuff merged from 3.0. For the big changes since 2.x, people will have
to refer to other porting docs, like whatsnew.

@tiran
Copy link
Member

tiran commented Mar 21, 2008

but skipping stuff merged from 3.0.

Do you mean "skipping stuff merged from 2.6" ?

@gvanrossum
Copy link
Member Author

Do you mean "skipping stuff merged from 2.6" ?

Yes :)

@birkenfeld birkenfeld assigned gvanrossum and unassigned birkenfeld Mar 29, 2008
@gvanrossum
Copy link
Member Author

Let's see if we can fix this by beta3.

@gvanrossum gvanrossum removed their assignment Aug 5, 2008
@benjaminp
Copy link
Contributor

I'm a little confused on what needs to happen here. It's "incomplete"
because it gets skipped in merges, but "2.6 ports don't need to be in 3.0".

@gvanrossum
Copy link
Member Author

I worry that many things were not recoded in Misc/NEWS at all,
especially in the early days of 3.0 development (e.g. in the p3yk branch
:-).

I'm not sure if it's possible to fix this retroactively, however. As
long as we keep the changes between the betas complete, and as long as
somebody updates the "what's new" document (I have volunteered for that
though I'm not sure I'll get to it :-( ) I'm okay.

So let's close this. We don't need more busy-work.

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir release-blocker
Projects
None yet
Development

No branches or pull requests

4 participants