[PDB-1421] PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt Created: 2015/04/10  Updated: 2015/05/07  Resolved: 2015/04/20

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 2.3.4

Type: Task Priority: Normal
Reporter: gepetto-bot Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: github
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Story Points: 0
Sprint: PuppetDB 2015-04-22

 Description   

(maint) add upgrading from v3 document to stable branch

Pull Request Description


This adds the upgrading from v3 document to our stable branch,
for better visibility to users.


(webhooks-id: 878025164833eb22cb4a4704105a3df9)



 Comments   
Comment by gepetto-bot [ 2015/04/10 ]

wkalt commented:

this was a change suggested by @MosesMendoza. The stable branch has much better user visibility than master, so to the extent that we can communicate these changes from the stable docs, we should.

We need to be careful that we are sure that everything mentioned in this document will remain true through release time, and we should be sure to cut out mention of any changes that we may yet revert.

Comment by gepetto-bot [ 2015/04/10 ]

pljenkinsro commented:

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1031/

Comment by gepetto-bot [ 2015/04/16 ]

kbarber commented:

I think my concern is around the message in that document, it concerns itself with people upgrading from v3 to v4 final, not experimental. Plus it also mentions version 3.0 things. I just think we need to be careful about the message we are sending here, I don't want people to look at the document thinking this is how they go from v3 to v4 experimental etc. Maybe the note you've made already about this not being about v4 experimental needs to be put in highlights, like we do for other notes or something? Whatever we do, we have to be absolutely clear . Otherwise I'm +1 on the concept.

Comment by gepetto-bot [ 2015/04/16 ]

wkalt commented:

I added more emphasis on the fact that these changes don't all relate to released code. I left the 3.0 stuff in there though because I think some of it's pretty important and is set in stone, like dashes->underscores. If there are specific things we want to omit or qualify I'm open to it, but nothing pops out at me.

Comment by gepetto-bot [ 2015/04/16 ]

pljenkinsro commented:

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1041/

Comment by gepetto-bot [ 2015/04/17 ]

kbarber commented:

@wkalt just thinking about this some more, I realised that if we add a feature to v4, and we change this document there, we'll need to backport this each time to this document. What if ... we just hyperlink instead? We can talk about this some more when you're alive.

Comment by gepetto-bot [ 2015/04/17 ]

pljenkinsro commented:

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1049/

Comment by gepetto-bot [ 2015/04/20 ]

pljenkinsro commented:

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1068/

Comment by gepetto-bot [ 2015/04/20 ]

Pull request (maint) add upgrading from v3 document to stable branch has been closed.

Generated at Thu Jun 20 02:57:47 PDT 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.