Bug 5857 - update release time for 1.5.1 in the latest ref manual
Summary: update release time for 1.5.1 in the latest ref manual
Status: RESOLVED FIXED
Alias: None
Product: Reference
Classification: Documentation
Component: handbook (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Scott Rifenbark
QA Contact:
URL:
Whiteboard: 20 March 2014: Doc flag reset
Depends on:
Blocks:
 
Reported: 2014-02-21 01:51 UTC by Chengwei Yang
Modified: 2014-03-20 10:07 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Done (doc changes complete)


Attachments
[PATCH] ref-manual: fix release time for 1.5.1 (939 bytes, patch)
2014-02-21 01:51 UTC, Chengwei Yang
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Chengwei Yang 2014-02-21 01:51:38 UTC
Created attachment 1783 [details]
[PATCH] ref-manual: fix release time for 1.5.1

the document released with yocto 1.5.1 has been updated but the latest one doesn't, so let's fix it.
Comment 1 Scott Rifenbark 2014-02-21 13:08:53 UTC
Here is what happened for the release dates listed in the Manual revision tables for the 1.5.1 release.  The tarball for the release was made before getting that last commit it.  So, the manual set available with the released 1.5.1 tarball will not have the commit, but the manual on the website does.

It cannot be fixed for the tarball.  

see http://www.yoctoproject.org/docs/1.5.1/ref-manual/ref-manual.html for the current 1.5.1 HTML version of the manual available through the website.

Please provide more context if I am not understanding this issue correctly.

Scott
Comment 2 Chengwei Yang 2014-02-24 01:17:00 UTC
Hmm, sorry to make your confused.

Yes, I know we can not change the released tarball, I made this patch for current master branch, say the comming 1.6 release, see this bug here http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html
Comment 3 Scott Rifenbark 2014-02-24 13:53:35 UTC
Ahh... okay.  Thanks for the explanation.  If the bug is for the upcoming 1.6 release then we probably can mark it as not a bug since when I release a set of manuals the actual release time for the tables should be correct.  As the manuals are being developed.  I leave in the "Sometime in xxx" date in the tables until I know the month of release.  It is usually April and October... We have never missed yet.  Maybe I should just put in April 2014 for the 1.6 release now in the "latest" manuals?  ..... 

I will see if I can get some feedback on that "policy" change and if there are no issues I will just start dong that with the major releases.

Scott
Comment 4 Chengwei Yang 2014-02-24 14:21:11 UTC
No, not really, I mean this is a bug because in the latest document, there has lines

             <revision>
                 <revnumber>1.5.1</revnumber>
                 <date>Sometime in 2013</date>

In fact, we all know that 1.5.1 was already released in January 2014.

I did mean this patch is for the upcomming 1.6 because you can't fix this for 1.5.1 now because it has been released. :-)

Hmm, just see the simple patch.
Comment 5 Scott Rifenbark 2014-02-24 14:41:21 UTC
Doh... Sorry.  I get it now.  I did not see that at all.  I will take care of this for all the 1.6 manuals.

Thanks, 
Scott
Comment 7 Scott Rifenbark 2014-03-20 10:07:51 UTC
Setting Doc flag to "Done"