Jira (PDB-5514) Update ticket templates (Puppet Platform 6.28.0)

16 views
Skip to first unread message

tefoji (Jira)

unread,
Jun 22, 2022, 6:44:01 PM6/22/22
to puppe...@googlegroups.com
tefoji updated an issue
 
PuppetDB / Task PDB-5514
Update ticket templates (Puppet Platform 6.28.0)
Change By: tefoji
Epic Link: PUP-11572
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Atlassian logo

tefoji (Jira)

unread,
Jun 22, 2022, 6:44:02 PM6/22/22
to puppe...@googlegroups.com
tefoji created an issue
Issue Type: Task Task
Assignee: Stel Abrego
Created: 2022/06/22 3:43 PM
Due Date: 2022/07/13
Priority: Normal Normal
Reporter: tefoji

(Initial planned release date: 2022-07-12)

If appropriate, raise a PR to adjust the
ticket templates
more accurate for the next time.

Molly Waggett (Jira)

unread,
Jul 19, 2022, 12:30:01 PM7/19/22
to puppe...@googlegroups.com
Molly Waggett updated an issue
Change By: Molly Waggett
Sprint: Dumpling Ready to Groom

Stel Abrego (Jira)

unread,
Jul 19, 2022, 2:14:03 PM7/19/22
to puppe...@googlegroups.com

Stel Abrego (Jira)

unread,
Jul 19, 2022, 2:17:03 PM7/19/22
to puppe...@googlegroups.com
Stel Abrego updated an issue
Change By: Stel Abrego
Sprint: Dumpling Ready to Groom 8-2-22

Stel Abrego (Jira)

unread,
Aug 2, 2022, 2:44:03 PM8/2/22
to puppe...@googlegroups.com
Stel Abrego updated an issue
(Initial planned release date: 2022-07-12)

If appropriate, raise a PR to adjust the

more accurate for the next time.
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Atlassian logo

Stel Abrego (Jira)

unread,
Aug 2, 2022, 2:45:04 PM8/2/22
to puppe...@googlegroups.com

Stel Abrego (Jira)

unread,
Aug 2, 2022, 3:27:01 PM8/2/22
to puppe...@googlegroups.com
Stel Abrego updated an issue
(Initial planned release date: 2022-07-12)

If appropriate, raise a PR to adjust the
[ticket templates|https://github.com/puppetlabs/tefoji-puppet-templates/blob/main/puppetdb.yaml]
more accurate for the next time.

PuppetDB docs are published via the doc-* branches:
  - docs for Puppet 7 (`main` branch): `doc-latest` branch
  - docs for Puppet 6 (`6.x` branch): `doc-6.y` branch

These `doc-*` branches control what docs are published at https://puppet.com/docs/puppetdb. To publish new docs, the branches are bumped to a newer commit on their respective development branch. This is traditionally done by updating the branch locally and pushing directly. Here is an example using the `main` and `doc-latest` branches:

{code}
git fetch origin
git switch doc-latest
git log --oneline --graph origin/main
# Look at commits on main branch to pick out one for docs to publish from
git reset --hard <tag-or-commit-from-the-main-branch>
git push origin
{code}

After a short time the changes should be live. Check https://puppet.com/docs/puppetdb and confirm that the new changes look right. You can check what documentation changed with `git diff`. Here is an example using the `main` and `doc-latest` branches:
{code}
git diff <previous-doc-latest-branch-head>..doc-latest -- documentation
{code}

Stel Abrego (Jira)

unread,
Aug 2, 2022, 3:28:01 PM8/2/22
to puppe...@googlegroups.com

Stel Abrego (Jira)

unread,
Aug 2, 2022, 5:07:02 PM8/2/22
to puppe...@googlegroups.com
Stel Abrego updated an issue
(Initial planned release date: 2022-07-12)

If appropriate, raise a PR to adjust the
[ticket templates|https://github.com/puppetlabs/tefoji-puppet-templates/blob/main/puppetdb.yaml]
more accurate for the next time.

      PuppetDB docs are published via the doc-* branches:

      ||Major Release Version||Development Branch||Doc Branch||
      |PuppetDB 7|main|doc-latest|
      |PuppetDB 6|6.x|doc-6.y|

      These doc-* branches control what docs are published at https://puppet.com/docs/puppetdb. To publish new docs, the doc branches are bumped to a newer commit on their respective development branch. This is traditionally done by updating the branch locally and pushing directly. Here is an example of updating the PuppetDB 7 docs by bumping the doc-latest branch:


      {code}
      git fetch origin
      git switch doc-latest
      git log --oneline --graph origin/main
      # Look at commits on main branch to pick out one for docs to publish from
      git reset --hard <tag-or-commit-from-the-main-branch>
      git push origin
      {code}

      After a short time the changes should be live. Check https://puppet.com/docs/puppetdb and confirm that the new changes look right. You can check what documentation changed with git diff. Here is an example using the main and doc-latest branches:

      {code}
      git diff <previous-doc-latest-branch-head>..doc-latest -- documentation
      {code}

Stel Abrego (Jira)

unread,
Aug 2, 2022, 5:07:02 PM8/2/22
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages