Skip to content

adding changelog info, again#5

Open
jvanasco wants to merge 3 commits into
sqlalchemyorg:mainfrom
jvanasco:feature-changelog_docs_2
Open

adding changelog info, again#5
jvanasco wants to merge 3 commits into
sqlalchemyorg:mainfrom
jvanasco:feature-changelog_docs_2

Conversation

@jvanasco

@jvanasco jvanasco commented Apr 6, 2020

Copy link
Copy Markdown
Contributor

abandoning #2 in favor of this

  • worked in mike's requests-for-changes
  • standardized tags/indetentation because some broken tags were hard to find
  • removed some "preferred" text and replaced with "required", in line with mike's latest direction

* standardized tags/indetentation because some broken tags were hard to find
* removed some "preferred" text and replaced with "required", in line with mike's latest direction
@jvanasco jvanasco mentioned this pull request Apr 6, 2020

@zzzeek zzzeek left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's the only content that changed, the rest is formatting right?

we don't have an example .rst file now unless they look at the other ones that are there. I usually don't attempt to get outside contributors to bother as it's too much to ask for one-time folks. but if someone wants to help more consistently it is very handy that they do these.

Comment thread develop.html.mako Outdated
</li>
<li>The file format for a changelog file uses the `.rst` markup described at
<a href="https://github.com/sqlalchemyorg/changelog">sqlalchemyorg/changelog</a>.
See the `README.txt` file in the `/doc/build/unreleased_XX` directory

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doc/build/changelog/unreleased_XX/README.txt is the path

however README.txt doesn't have an example right now

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section now links to #pr-requires-issue above

I started working on the example; it's in the other repo though so can't be part of this commit.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok can you push out the fix to that path i can merge and publish

@jvanasco jvanasco Apr 6, 2020

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zzzeek a few questions.

I am making an actual unreleased_XX/README.txt folder/file for the example in the sqlalchemy repo. I can redo that for something here.

That file has two sections. The first is a basically the existing README.txt from versioned. The second section is a quick example and overview.

I noticed the .rst files tend to use :tickets: but the https://github.com/sqlalchemyorg/changelog/blob/master/README.rst notes :ticket:

Looking at the code, it seems most of the per-ticket items .rst files use :tickets: but the generated files typically use :ticket:

Are these interchangable? Am I overthinking this?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's supposed to be :tickets: because there can be mutiple present there.

There's a README.txt already present, we can add to that? https://github.com/sqlalchemy/sqlalchemy/blob/master/doc/build/changelog/unreleased_13/README.txt the unreleased_XX folder is there too already?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a new unreleased_xx folder, and used the README from the 1.x branches as the starting point. I was thinking about updating the existing README files to reference that one

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can call it unreleased_XX here but it means to look in each numbered folder

@jvanasco jvanasco left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zzzeek there is on other place where content changed. The document originally had Issues "preferred"; I standardized the messaging to required. I'm calling out in this review:

Comment thread develop.html.mako
@CaselIT

CaselIT commented Apr 6, 2020

Copy link
Copy Markdown
Contributor

looks good to me

Comment thread develop.html.mako
Comment thread develop.html.mako Outdated
@jvanasco

Copy link
Copy Markdown
Contributor Author

updated SqlAlchemy > SQLAlchemy

@jvanasco jvanasco requested a review from zzzeek May 14, 2020 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants