Niall Douglas | 7 Feb 15:39 2016

[gsoc16] ATTN: Project ideas deadline 19th Feb

Tomorrow 8th February the application period for Google Summer of 
Code 2016 begins, and yet we have just *one* idea on the ideas page:

https://svn.boost.org/trac/boost/wiki/SoC2016

We need *plenty* more if we are to be approved again this year as a 
Google Summer of Code org, the deadline for which is the 19th 
February.

So if you have some project ideas and think you could mentor a 
student this summer, *please* consider adding a project idea to the 
ideas list or stepping forward with a list of Boost libraries or 
topics you'd be willing to mentor.

Our thanks in advance.

--- 
Boost C++ Libraries Google Summer of Code 2016 admin
https://svn.boost.org/trac/boost/wiki/SoC2016

Attachment (SMime.p7s): application/x-pkcs7-signature, 8 KiB
Tomorrow 8th February the application period for Google Summer of 
Code 2016 begins, and yet we have just *one* idea on the ideas page:

https://svn.boost.org/trac/boost/wiki/SoC2016

We need *plenty* more if we are to be approved again this year as a 
Google Summer of Code org, the deadline for which is the 19th 
(Continue reading)

Niall Douglas | 18 Jan 10:27 2016

[gsoc16] Attn: We need 2016 mentors and project ideas for Boost!

Dear Boost community,

We are now within one month of the beginning of Google Summer of Code
2016! Last year's GSoC was a particularly momentus one as we 
witnessed the approval by the community for Boost.Hana to enter Boost 
- congratulations to Louis and his mentor Joel for bringing to Boost 
a very exciting new C++ library which pushes C++ compilers to their 
limits. We have also seen greatly improved retention of GSoC students 
in the community thanks to the improved student selection procedures 
introduced last year, and the fresh blood brought into Boost has been 
very evident on the mailing list this year.

As part of filling in our application for 2016, we must supply to 
Google a
list of potential GSoC mentors and potential GSoC projects for summer
2016 in order to be approved as an organisation this year. Therefore 
a lengthy page of awesome project ideas at 
https://svn.boost.org/trac/boost/wiki/SoC2016 before *February 8th* 
would be an enormous help to getting us approved again this year and 
bringing to Boost another US$35,000 of Google funding.

If you think yourself able to mentor a student doing some work on 
Boost
this summer, *please* consider adding a description of the proposed 
work
item and your name to the list. Last year we had more slots awarded 
to us by Google than we had good combinations of student and mentor, 
so we had to return slots which I believe has not happened here at 
Boost GSoC in at least a decade. That means that your project ideas 
have a better chance than ever of receiving funding if you can find a 
(Continue reading)

Adam Wulkiewicz | 4 Jan 16:41 2016
Picon
Gravatar

[boost][review][qvm] QVM formal review result

Dear Boost community,

The review period for Emil Dotchevski's QVM library has concluded. I'd 
like to thank everyone who participated in the discussions, esspecially 
those who sent formal reviews.

Only four votes were casted however more people commented on issues on 
the mailing list. Comments received during the course of the review were 
generally positive, with a number of technical issues identified that 
need to be addressed. The review identified no fundamental problems in 
the design or implementation of the library that would entail rejection. 
The final version of the library can be fully accepted once Emil has 
addressed the issues identified during the review. Therefore I'm happy 
to say:

      Emil Dotchevski's Boost.QVM library is CONDITIONALLY ACCEPTED.

Full report can be found here:
http://lists.boost.org/Archives/boost/2016/01/227027.php

Regards,
Adam
Marshall Clow | 17 Dec 21:00 2015
Picon

Boost 1.60.0 has been released

Release 1.60.0 of the Boost C++ Libraries is now available.

These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. 
The Boost license encourages both commercial and non-commercial use.

This release contains one new library and numerous enhancements and bug fixes for existing libraries.

New Libraries
* VMD: Variadic Macro Data library, from Edward Diener

For details, including download links, see http://www.boost.org/users/news/version_1.60.0

You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.60.0/

Tom Kent has made pre-built windows binaries, and they are available at:


Thanks,

--The Boost release team

  Vladimir Prus
  Rene Rivera
  Marshall Clow
  Eric Niebler
  Daniel James
  Beman Dawes

<div><div dir="ltr">
<div>Release 1.60.0 of the Boost C++ Libraries is now available.</div>
<div><br></div>
<div>These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications.&nbsp;</div>
<div>The Boost license encourages both commercial and non-commercial use.</div>
<div><br></div>
<div>This release contains one new library and numerous enhancements and bug fixes for existing libraries.</div>
<div><br></div>
<div>New Libraries</div>
<div>* VMD: Variadic Macro Data library, from Edward Diener</div>
<div><br></div>
<div>For details, including download links, see <a href="http://www.boost.org/users/news/version_1.60.0">http://www.boost.org/users/news/version_1.60.0</a>
</div>
<div><br></div>
<div>You can also download directly from SourceForge: <a href="http://sourceforge.net/projects/boost/files/boost/1.60.0/">http://sourceforge.net/projects/boost/files/boost/1.60.0/</a>
</div>
<div><br></div>
<div>Tom Kent has made pre-built windows binaries, and they are available at:</div>
<div><a href="https://sourceforge.net/projects/boost/files/boost-binaries/1.60.0/">https://sourceforge.net/projects/boost/files/boost-binaries/1.60.0/</a></div>
<div><br></div>
<div>To install this release on your system, see <a href="http://www.boost.org/doc/libs/release/more/getting_started/index.html">http://www.boost.org/doc/libs/release/more/getting_started/index.html</a>
</div>
<div><br></div>
<div>Thanks,</div>
<div><br></div>
<div>--The Boost release team</div>
<div><br></div>
<div>&nbsp; Vladimir Prus</div>
<div>&nbsp; Rene Rivera</div>
<div>&nbsp; Marshall Clow</div>
<div>&nbsp; Eric Niebler</div>
<div>&nbsp; Daniel James</div>
<div>&nbsp; Beman Dawes</div>
<div><br></div>
</div></div>
Marshall Clow | 14 Dec 16:54 2015
Picon

Boost 1.60.0 rc1 is now available

Release candidate files for 1.60.0 are available at: http://boost.cowic.de/rc/

As always, the release managers would appreciate it if you download
the candidate of your choice and give building it a try. Please report
both success and failure, and anything else that is noteworthy.

This helps ensure the candidates build OK before we push them out to SourceForge.

The files (and associated md5s) are:
MD5 (boost_1_60_0_rc1.7z) = 7ce7f5a4e396484da8da6b60d4ed7661
MD5 (boost_1_60_0_rc1.tar.bz2) = 65a840e1a0b13a558ff19eeb2c4f0cbe
MD5 (boost_1_60_0_rc1.tar.gz) = 28f58b9a33469388302110562bdf6188
MD5 (boost_1_60_0_rc1.zip) = 0cc5b9cf9ccdf26945b225c7338b4288

Thanks!

-- The release managers


<div><div dir="ltr">
<div>Release candidate files for 1.60.0 are available at: <a href="http://boost.cowic.de/rc/">http://boost.cowic.de/rc/</a>
</div>
<div><br></div>
<div>As always, the release managers would appreciate it if you download</div>
<div>the candidate of your choice and give building it a try. Please report</div>
<div>both success and failure, and anything else that is noteworthy.</div>
<div><br></div>
<div>This helps ensure the candidates build OK before we push them out to SourceForge.</div>
<div><br></div>
<div>The files (and associated md5s) are:</div>
<div>
<span class="">	</span>MD5 (boost_1_60_0_rc1.7z) = 7ce7f5a4e396484da8da6b60d4ed7661</div>
<div>
<span class="">	</span>MD5 (boost_1_60_0_rc1.tar.bz2) = 65a840e1a0b13a558ff19eeb2c4f0cbe</div>
<div>
<span class="">	</span>MD5 (boost_1_60_0_rc1.tar.gz) = 28f58b9a33469388302110562bdf6188</div>
<div>
<span class="">	</span>MD5 (boost_1_60_0_rc1.zip) = 0cc5b9cf9ccdf26945b225c7338b4288</div>
<div><br></div>
<div>Thanks!</div>
<div><br></div>
<div>-- The release managers</div>
<div><br></div>
<div>P.S.<span class="">	</span>Release notes are here: <a href="http://www.boost.org/users/history/version_1_60_0.html">http://www.boost.org/users/history/version_1_60_0.html</a>
</div>
<div><br></div>
</div></div>
Marshall Clow | 8 Dec 18:11 2015
Picon

Boost release 1.60.0 beta 1 is now available from SourceForge

Boost release 1.60.0 beta 1 is now available from SourceForge.


For details of what's in the release, see http://www.boost.org/users/history/version_1_60_0.html

Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files.

Please download the beta, give it a try, and report any problems you encounter.

Known issues:
* Errors when building Boost.TypeErasure for older versions of Visual Studio.
* Boost.Test fails when building on Darwin with gcc 4.9.2

The files (and associated md5s) are:
MD5 (boost_1_60_0_b1.7z) = 63530c9594b24f56e5df79d910c9daeb
MD5 (boost_1_60_0_b1.tar.bz2) = 29af12a1028536219a21517e953df4eb
MD5 (boost_1_60_0_b1.tar.gz) = 74df7f5eb5e32f3a92b6141af3c6f541
MD5 (boost_1_60_0_b1.zip) = 90c25c34b64eb6cc88845ec5372938d7

Thanks,

-- The Boost Release Team

<div><div dir="ltr">
<div>Boost release 1.60.0 beta 1 is now available from SourceForge.</div>
<div><br></div>
<div>See <a href="http://sourceforge.net/projects/boost/files/boost/1.60.0.beta.1/">http://sourceforge.net/projects/boost/files/boost/1.60.0.beta.1/</a>
</div>
<div><br></div>
<div>For details of what's in the release, see <a href="http://www.boost.org/users/history/version_1_60_0.html">http://www.boost.org/users/history/version_1_60_0.html</a>.&nbsp;</div>
<div><br></div>
<div>Note that the links to files on this web page are for the final release - use the SourceForge link above to get the beta files.</div>
<div><br></div>
<div>Please download the beta, give it a try, and report any problems you encounter.</div>
<div><br></div>
<div>Known issues:</div>
<div>* Errors when building Boost.TypeErasure for older versions of Visual Studio.</div>
<div>* Boost.Test fails when building on Darwin with gcc 4.9.2</div>
<div><br></div>
<div>The files (and associated md5s) are:</div>
<div>
<span class="">	</span>MD5 (boost_1_60_0_b1.7z) = 63530c9594b24f56e5df79d910c9daeb</div>
<div>
<span class="">	</span>MD5 (boost_1_60_0_b1.tar.bz2) = 29af12a1028536219a21517e953df4eb</div>
<div>
<span class="">	</span>MD5 (boost_1_60_0_b1.tar.gz) = 74df7f5eb5e32f3a92b6141af3c6f541</div>
<div>
<span class="">	</span>MD5 (boost_1_60_0_b1.zip) = 90c25c34b64eb6cc88845ec5372938d7</div>
<div><br></div>
<div>Thanks,</div>
<div><br></div>
<div>-- The Boost Release Team</div>
<div><br></div>
</div></div>
Adam Wulkiewicz | 7 Dec 11:40 2015
Picon
Gravatar

[boost][boost-users][boost-announce][QVM] Formal review begins today

Dear Boost community,

The formal review of Emil Dotchevski's QVM library begins today on 7th Dec
and ends on 16th Dec.

Boost QVM defines a set of generic functions and operator overloads for 
working
with quaternions, vectors and matrices of static size with the emphasis 
on 2, 3
and 4-dimensional operations needed in graphics, video games and simulation
applications. While it provides its own quaternion, matrix and vector 
types, it
is designed to work primarily with user-defined types through user
specializations of the q_traits, v_traits and m_traits templates.

QVM's source code is available on Github:
https://github.com/zajo/boost-qvm

Full documentation is also viewable on Github:
http://zajo.github.io/boost-qvm/

We encourage your participation in this review. At a minimum, kindly
state:
- Whether you believe the library should be accepted into Boost
   * Conditions for acceptance
- Your name
- Your knowledge of the problem domain.

You are strongly encouraged to also provide additional information:
- What is your evaluation of the library's:
   * Design
   * Implementation
   * Documentation
   * Tests
   * Usefulness
- Did you attempt to use the library? If so:
   * Which compiler(s)
   * What was the experience? Any problems?
- How much effort did you put into your evaluation of the review?

More information about the review process can be found here:
http://www.boost.org/community/reviews.html

We await your feedback!

Best regards,
Adam Wulkiewicz
Adam Wulkiewicz | 5 Dec 12:55 2015
Picon
Gravatar

[boost][qvm] Formal review for QVM

Dear Boost community,

The formal review of Emil Dotchevski's QVM library begins on 7th Dec
and ends on 16th Dec.

Boost QVM defines a set of generic functions and operator overloads for working
with quaternions, vectors and matrices of static size with the emphasis on 2, 3
and 4-dimensional operations needed in graphics, video games and simulation
applications. While it provides its own quaternion, matrix and vector types, it
is designed to work primarily with user-defined types through user
specializations of the q_traits, v_traits and m_traits templates.

QVM's source code is available on Github:
https://github.com/zajo/boost-qvm

Full documentation is also viewable on Github:
http://zajo.github.io/boost-qvm/

We encourage your participation in this review. At a minimum, kindly
state:
- Whether you believe the library should be accepted into Boost
  * Conditions for acceptance
- Your name
- Your knowledge of the problem domain.

You are strongly encouraged to also provide additional information:
- What is your evaluation of the library's:
  * Design
  * Implementation
  * Documentation
  * Tests
  * Usefulness
- Did you attempt to use the library? If so:
  * Which compiler(s)
  * What was the experience? Any problems?
- How much effort did you put into your evaluation of the review?

More information about the review process can be found here:
http://www.boost.org/community/reviews.html

We await your feedback!

Best regards,
Adam Wulkiewicz
<div><div dir="ltr">Dear Boost community,<br><br>The formal review of Emil Dotchevski's QVM library begins on 7th Dec<br>and ends on 16th Dec.<br><br>Boost QVM defines a set of generic functions and operator overloads for working<br>with quaternions, vectors and matrices of static size with the emphasis on 2, 3<br>and 4-dimensional operations needed in graphics, video games and simulation<br>applications. While it provides its own quaternion, matrix and vector types, it<br>is designed to work primarily with user-defined types through user<br>specializations of the q_traits, v_traits and m_traits templates.<br><br>QVM's source code is available on Github:<br><a href="https://github.com/zajo/boost-qvm" target="_blank">https://github.com/zajo/boost-qvm</a><br><br>Full documentation is also viewable on Github:<br><a href="http://zajo.github.io/boost-qvm/" target="_blank">http://zajo.github.io/boost-qvm/</a><br><br>We encourage your participation in this review. At a minimum, kindly<br>state:<br>- Whether you believe the library should be accepted into Boost<br>&nbsp; * Conditions for acceptance<br>- Your name<br>- Your knowledge of the problem domain.<br><br>You are strongly encouraged to also provide additional information:<br>- What is your evaluation of the library's:<br>&nbsp; * Design<br>&nbsp; * Implementation<br>&nbsp; * Documentation<br>&nbsp; * Tests<br>&nbsp; * Usefulness<br>- Did you attempt to use the library? If so:<br>&nbsp; * Which compiler(s)<br>&nbsp; * What was the experience? Any problems?<br>- How much effort did you put into your evaluation of the review?<br><br>More information about the review process can be found here:<br><a href="http://www.boost.org/community/reviews.html" target="_blank">http://www.boost.org/community/reviews.html</a><br><br>We await your feedback!<br><br>Best regards,<br>Adam Wulkiewicz</div></div>
Nat Goodspeed | 10 Oct 15:45 2015

Boost.Fiber mini-review report

The mini-review of Boost.Fiber by Oliver Kowalke ran from Friday
September 4th through Sunday September 13th. There was lively
discussion, but only two actual reviews:

Agustín K-ballo Bergé: not yet (list of issues below)
Niall Douglas: yes, plus suggestions (below)[0]

In addition I received two "review withheld" notes:

Vicente J. Botet Escriba wanted me to address the previous review
point by point. That seems like a reasonable request, and I apologize,
but I too have time pressures.

Giovanni Piero Deretta made suggestions (synopsized below) with the
statement that he will make a recommendation when he sees the library
author's progress along those lines.

While in theory these results might seem like a hung jury, the very
paucity of formal reviews supports a cautious approach.

The verdict is: not yet, with specific points as noted below.

No reviewer explicitly designated specific points as being essential.
(Niall Douglas explicitly designated his suggestions as post-adoption
enhancements.)

I have made an attempt to rank the recommendations received in
descending order of importance to the community. My criteria are:

Robustness: does lack of this request pose significant risk to a
consuming program?

API stability: could this request be considered an implementation
detail, or would the change break early adopters?

Demand: how many people requested the same thing?

If you feel that I have misrepresented the importance of one of your
points (or omitted something entirely), please respond. Ultimately, of
course, the importance of any given point to the community at large
will be reflected in the next mini-review.

-----------------------------------------------------------------
Requests:

Cross-thread fiber migration: Evidently the community strongly desires
the ability to transfer a suspended fiber from one thread to
another.[1] Of course there must be controls. Migration might be
explicit; but if implicit, there must be a way to designate which
fibers may and may not be migrated. An RAII class that temporarily
disables migration would also be desirable -- for instance, to
guarantee TLS consistency for some specific period.

Cross-thread migration support implies a requirement to document the
thread safety requirements of the customization API.

Standard required timing specifications: meet (30.2.4 Timing
specifications [thread.req.timing]).

Adapt one or more existing test suites for thread facilities to
validate the correctness of the Fiber library's synchronization
constructs: e.g. from libc++, libstdc++, Boost.Thread, HPX.

std::chrono support: ensure that wait_until() can accept any supported
time_point specialization. (The library author asserts that this has
already been fixed on the 'develop' branch.)

C++11 compatibility: Agustín K-ballo Bergé volunteered to help with
this point post-adoption. Paul Fultz offered fit::capture to emulate
C++14 move capture.

Document that this_fiber::yield() (et al.) are valid from main(), or
in general from a thread function, as well as from explicitly-launched
fibers.

Make shared_state lock requirements explicit: for example, make
mark_ready_and_notify_() accept a std::unique_lock<>& (or &&) to force
its caller to provide one.

Avoid holding mutex during condition_variable::notify_*() calls. (The
library author asserts that this has already been fixed on the
'develop' branch.)

packaged_task must not decay-copy its task arguments.

Align fibers::async() signature, result description and invoke_helper
implementation with std::async(). Avoid returning std::move(...).

Wait list implementation: try an intrusive linked list of fiber_context objects.

Avoid sleeping thread when no fibers are ready -- block on external
event. Better handling of waiting tasks (decentralized wait queues?).

Optimization to resume awakened fiber on the thread that awakens it.

Template redundancy: eliminate duplication between specializations for
T, T& and void. The future, shared_future, shared_state, promise and
task_object templates were specifically cited.

Leverage predicate-based condition::wait() overload internally.

Nested schedulers: make schedulers be schedulable entities themselves.

Improve robustness of `promise' handling in Asynchronous Callbacks
documentation. Avoid overconfident remarks about it.

Fix Note overstating the requirements on condition_variable::wait().

The discussion also surfaced the desirability of Grand Unified Future
Theory, but it was generally agreed that this is out of scope. Put
differently, it would be unreasonable to put the onus on Fiber to
solve that very broad cross-library problem.

Many thanks to all participants, and thanks especially to Oliver
Kowalke for all his work on this library!

Nat Goodspeed
Boost.Fiber Review Manager
________________________________

[0] Niall Douglas snuck his review recommendation into the following
mail message:
http://lists.boost.org/Archives/boost/2015/09/225228.php
(second to final paragraph). His suggestions were in private mail.

[1] Giovanni Deretta suggests that it might be possible to allocate --
without actually running -- an actual kernel thread per fiber, simply
to give each fiber its own TLS area.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-announce
Antony Polukhin | 25 Sep 18:26 2015
Picon

[Boost-users] Compile and run Boost examples online

Hi all,

I've just launched the beta version of online examples for the "Boost Application Development Cookbook":

http://apolukhin.github.io/Boost-Cookbook-4880OS/

There you can do online compilation of Boost related code, run examples, freely experiment with code from the book, read intros for the code and play around with the Boost libraries.

I hope the site would be useful!


P.S.: If you wish to report an error or wish to have some functionality added to the site, use the "Issues" link at https://github.com/apolukhin/Boost-Cookbook-4880OS or even make a pull request.

P.P.S.: Intros for Chapters 7-12 are missing at this moment. I'll add them in a few months, sorry for the delay.


--
Best regards,
Antony Polukhin
<div><div dir="ltr">Hi all,<br><br>I've just launched the beta version of online examples for the "Boost Application Development Cookbook":<br><br><a href="http://apolukhin.github.io/Boost-Cookbook-4880OS/">http://apolukhin.github.io/Boost-Cookbook-4880OS/</a><br><br>There you can do online compilation of Boost related code, run examples, freely experiment with code from the book, read intros for the code and play around with the Boost libraries.<br><br>I hope the site would be useful!<br><br><br>P.S.: If you wish to report an error or wish to have some functionality added to the site, use the "Issues" link at <a href="https://github.com/apolukhin/Boost-Cookbook-4880OS">https://github.com/apolukhin/Boost-Cookbook-4880OS</a> or even make a pull request.<br><br>P.P.S.: Intros for Chapters 7-12 are missing at this moment. I'll add them in a few months, sorry for the delay.<br><br clear="all"><br>-- <br><div class="gmail_signature">Best regards,<br>Antony Polukhin</div>
</div></div>
Nat Goodspeed | 4 Sep 17:14 2015

Boost.Fiber mini-review September 4-13

Hi all,

The mini-review of Boost.Fiber by Oliver Kowalke begins today, Friday
September 4th, and closes Sunday September 13th. It was reviewed in
January 2014; the verdict at that time was "not in its present form."
Since then Oliver has substantially improved documentation,
performance, library customization and the underlying implementation,
and is bringing the library back for mini-review.

The substance of the library API remains the same, which is why a
mini-review is appropriate.

The Fiber library now requires a C++14-conforming compiler.

I will monitor reviews and discussion on both the boost-users <at>  list
and the boost <at>  developers' list. Please include at least "fiber" and
"review" in your mail subject, e.g. by replying to this message.
(Please reply to only ONE list, however.)

Thank you for your interest and your feedback!

-----------------------------------------------------

About the library:

Boost.Fiber provides a framework for micro-/userland-threads (fibers)
scheduled cooperatively. The API contains classes and functions to
manage and synchronize fibers similar to Boost.Thread. Each fiber has
its own stack.

A fiber can save the current execution state, including all registers
and CPU flags, the instruction pointer, and the stack pointer and
later restore this state. The idea is to have multiple execution paths
running on a single thread using a sort of cooperative scheduling
(versus threads, which are preemptively scheduled). The running fiber
decides explicitly when it should yield to allow another fiber to run
(context switching). Boost.Fiber internally uses execution_context
from Boost.Context; the classes in this library manage, schedule and,
when needed, synchronize those contexts. A context switch between
threads usually costs thousands of CPU cycles on x86, compared to a
fiber switch with a few hundred cycles. A fiber can only run on a
single thread at any point in time.

docs: http://olk.github.io/libs/fiber/doc/html/index.html
git: https://github.com/olk/boost-fiber

---------------------------------------------------

Please always state in your review whether you think the library
should be accepted as a Boost library!

Additionally please consider giving feedback on the following general topics:

- What is your evaluation of the design?
- What is your evaluation of the implementation?
- What is your evaluation of the documentation?
- What is your evaluation of the potential usefulness of the library?
- Did you try to use the library? With what compiler? Did you have any problems?
- How much effort did you put into your evaluation? A glance? A quick
reading? In-depth study?
- Are you knowledgeable about the problem domain?

Nat Goodspeed
Boost.Fiber Review Manager
________________________________

Gmane