Dear release managers, MSM is now almost ready for the 1.44 branch (hear hear, I didn't lie at the BoostCon ;-) ). I need a little help for some of the steps. The current status is: *root/index.html includes the library in its list of new libraries. Not done. How should I proceed? *root/libs/libraries.htm entry is OK, both in the alphabetic list and in the category lists. Done. *root/libs/maintainers.txt entry is OK. Done *website/public_html/beta/feed/history/ entry is OK Not done. Who does this? *The library has been added to the website documentation list Not done. Who does this? *The library's root/libs/xxx directory contains an index.html file with either the main docs or a redirection to the main docs Done *The primary docs pages meet Boost requirements and guidelines. Don't leave this until too late; it has turned up lots of issues in the past I suppose. Any comment on what I could have done wrong? *Component has been added to Trac Not done. How to do? *Trunk inspection report is clean Done (only irrelevant warnings about license in html files left) *Trunk regression tests are reasonably clean or marked up Done How do we proceed further? What do I also need to do to get MSM into the 1.44 branch? Thanks, Christophe
On 6/10/2010 3:19 PM, Christophe Henry wrote:
*root/index.html includes the library in its list of new libraries. Not done. How should I proceed?
Hm.. I don't know what that one is about :-\
*website/public_html/beta/feed/history/ entry is OK Not done. Who does this?
You could do it, or you could post what you want in the release announcement and Daniel will likely do it (or I will eventually). The file to edit is <https://svn.boost.org/svn/boost/website/public_html/beta/feed/history/boost_1_44_0.qbk>.
*The library has been added to the website documentation list Not done. Who does this?
Usually Daniel, or me eventually :-) Again, just post what you want. Or if you are brave edit the database file yourself <https://svn.boost.org/svn/boost/website/public_html/beta/doc/libraries.xml>.
*Component has been added to Trac Not done. How to do?
One of the admins will do it.. Which is often me.. Just tell me what your trac user ID is.
How do we proceed further? What do I also need to do to get MSM into the 1.44 branch?
Before the deadline, you'll need to merge your code to the release branch at <https://svn.boost.org/svn/boost/branches/release/>. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
Rene Rivera wrote:
How do we proceed further? What do I also need to do to get MSM into the 1.44 branch?
Before the deadline, you'll need to merge your code to the release branch at <https://svn.boost.org/svn/boost/branches/release/>.
I don't mean to hijack this thread, but I'm in very much the same boat as Christophe. Is commit access to the release branch automatic once a developer has commit access to the trunk or do we need to get our permissions upgraded before we can perform the merge? Thanks, Luke
On 6/10/2010 4:18 PM, Simonson, Lucanus J wrote:
Rene Rivera wrote:
How do we proceed further? What do I also need to do to get MSM into the 1.44 branch?
Before the deadline, you'll need to merge your code to the release branch at<https://svn.boost.org/svn/boost/branches/release/>.
I don't mean to hijack this thread, but I'm in very much the same boat as Christophe.
Is commit access to the release branch automatic once a developer has commit access to the trunk or do we need to get our permissions upgraded before we can perform the merge?
AFAIK it should be automatic. But I'm not in charge of the svn permissions. So I could be totally wrong ;-) -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
At Thu, 10 Jun 2010 16:24:43 -0500, Rene Rivera wrote:
Is commit access to the release branch automatic once a developer has commit access to the trunk or do we need to get our permissions upgraded before we can perform the merge?
AFAIK it should be automatic.
It is. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
On 10 June 2010 22:05, Rene Rivera <grafikrobot@gmail.com> wrote:
On 6/10/2010 3:19 PM, Christophe Henry wrote:
*root/index.html includes the library in its list of new libraries. Not done. How should I proceed?
Hm.. I don't know what that one is about :-\
We generally sort that before the beta. Don't worry about it. Same for the website.
*website/public_html/beta/feed/history/ entry is OK Not done. Who does this?
You could do it, or you could post what you want in the release announcement and Daniel will likely do it (or I will eventually). The file to edit is <https://svn.boost.org/svn/boost/website/public_html/beta/feed/history/boost_1_44_0.qbk>.
I normally just copy the description for libs/libraries.htm. If you want anything more, let me know.
How do we proceed further? What do I also need to do to get MSM into the 1.44 branch?
Before the deadline, you'll need to merge your code to the release branch at <https://svn.boost.org/svn/boost/branches/release/>.
Can you wait until we give you the go ahead. If we're slow then that's our fault, so we're not going to stop you releasing. We need to check the documentation, inspect report, test results etc. Daniel
participants (6)
-
Christophe Henry -
Daniel James -
David Abrahams -
Marshall Clow -
Rene Rivera -
Simonson, Lucanus J