Bug 9223

Summary:	Add a note about Hob's deprecation to the Build Appliance and Hob project pages
Product:	[Infrastructure] Website	Reporter:	Belen Barros Pena <belen.barros.pena>
Component:	web-content	Assignee:	Jeff Osier-Mixon <jefro>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	jefro, melissa, mhalstead, srifenbark
Version:	unspecified
Target Milestone:	Q1
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Belen Barros Pena 2016-03-07 15:18:35 UTC

I don't seem to able to the edit the content of the pages inside the Internal Projects section of the website, so I will need someone else to add the note about the deprecation of Hob. 

In https://www.yoctoproject.org/tools-resources/projects/hob we could use this:

<p><strong>NOTE</strong>: <a href="tools-resources/projects/hob">Hob</a> is now deprecated and will no longer be available starting from the upcoming 2.1 release of the Yocto Project. You can <a href="tools-resources/projects/toaster">use Toaster</a> instead.</p>

For the Build Appliance page (https://www.yoctoproject.org/tools-resources/projects/build-appliance), we could use: 

<p><strong>NOTE</strong>: <a href="tools-resources/projects/hob">Hob</a> is now deprecated and will no longer be available starting from the upcoming 2.1 release of the Yocto Project. You can <a href="tools-resources/projects/toaster">use Toaster</a> instead. Hob will still be available inside the Build Appliance, but might not work as expected, since it is no longer maintained.</p>

Thanks!

Comment 1 Belen Barros Pena 2016-03-07 15:20:51 UTC

Just found another page that needs the note:

https://www.yoctoproject.org/tools-resources/projects/gui-development-tools

Comment 2 Jeff Osier-Mixon 2016-05-12 17:24:33 UTC

Michael - any ideas? This set and the set for 1.7.3 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=9558) both have the same permissions in the tree as all other docs. I don't know why they wouldn't be accessible.

also adding Scott on Cc and posting this same message in the other bug

Comment 3 Jeff Osier-Mixon 2016-05-12 17:42:16 UTC

sorry, I edited the wrong bug with previous comment. This is one that I can fix.

the short answer is that the internal projects page is an amalgam of nodes with content type "project", so we just need to edit the particular project for the fix to appear on this page. I will take care of it asap.

Comment 4 Belen Barros Pena 2016-05-13 09:43:05 UTC

Ah, the Drupal mysteries ;) Sorry: I didn't realise it worked that way. Thanks for taking care of it.

Comment 5 Jeff Osier-Mixon 2016-05-16 21:22:11 UTC

These have been edited. Please take a look so I can close the bug. thanks!

Comment 6 Belen Barros Pena 2016-05-17 09:21:49 UTC

(In reply to comment #5)
> These have been edited. Please take a look so I can close the bug. thanks!

Looks good to me. Thanks!

Belén

Comment 7 Scott Rifenbark 2016-05-19 17:21:29 UTC

I went in and cleaned up the text to reflect a released 2.1 YP rather than a pending 2.1.  see the links for the changed wording. 

I think you can close this bug now.

Scott

Comment 8 Jeff Osier-Mixon 2016-05-19 17:22:39 UTC

closed!