[release] master branch closes soon - check build status

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[release] master branch closes soon - check build status

Boost - Dev mailing list
The master branch will be closing soon (in about 30-hours). Please check
the build status of your library.

<https://www.boost.org/development/tests/master/developer/summary.html>


- Your Friendly Boost Release Team

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] master branch closes soon - check build status

Boost - Dev mailing list
On Tuesday, August 6, 2019 at 8:39 PM, Michael Caisse wrote:
> The master branch will be closing soon (in about 30-hours).
Is the master branch closed now?

Cromwell D. Enage

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] master branch closes soon - check build status

Boost - Dev mailing list
On Tuesday, August 6, 2019 at 8:39 PM, Michael Caisse wrote:
> The master branch will be closing soon (in about 30-hours).

Is there time to merge Boost.Parameter PR #90, a documentation change?

Cromwell D. Enage

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] master branch closes soon - check build status

Boost - Dev mailing list
On 8/8/19 21:54, Cromwell Enage via Boost wrote:
> On Tuesday, August 6, 2019 at 8:39 PM, Michael Caisse wrote:
>> The master branch will be closing soon (in about 30-hours).
>
> Is there time to merge Boost.Parameter PR #90, a documentation change?
>
> Cromwell D. Enage
>

It is currently closed.

--
Michael Caisse
Ciere Consulting
ciere.com

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] master branch closes soon - check build status

Boost - Dev mailing list
In reply to this post by Boost - Dev mailing list
On Friday, August 9, 2019, Cromwell Enage  wrote:

> Is there time to merge Boost.Parameter PR #90, a documentation change?
>


Looks like PR #90 removes ALL the documentation sources with a commit
message "Temporarily remove documentation until they are fixed...".

Why _temporarily_ remove anything? Just disable the relevant step in
doc/Jamfile? Before shipping a Boost.Parameter in a Boost release, have at
least the fixed documentation sources int here, or the existing ones.

There's no value in PR90 going into Boost 1.71 for users is there?

Glen

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] master branch closes soon - check build status

Boost - Dev mailing list
On August 9, 2019 2:04:32 PM Glen Fernandes via Boost
<[hidden email]> wrote:

> On Friday, August 9, 2019, Cromwell Enage  wrote:
>
>> Is there time to merge Boost.Parameter PR #90, a documentation change?
>
>
> Looks like PR #90 removes ALL the documentation sources with a commit
> message "Temporarily remove documentation until they are fixed...".
>
> Why _temporarily_ remove anything? Just disable the relevant step in
> doc/Jamfile? Before shipping a Boost.Parameter in a Boost release, have at
> least the fixed documentation sources int here, or the existing ones.
>
> There's no value in PR90 going into Boost 1.71 for users is there?

If the current docs are completely wrong then I'd say revert the code to
correspond to docs, at least remotely. The new code should be considered
not ready for release in this case.

I doubt though that the old docs are completely useless. I don't think we
had to completely rewrite Boost.Parameter-related code in other libraries,
which means the old interfaces and their docs are still relevant.

In any case, releasing a library with no docs is not acceptable.





_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Reply | Threaded
Open this post in threaded view
|

Re: [release] master branch closes soon - check build status

Boost - Dev mailing list
On Friday, August 9, 2019 at 7:04 AM, Glen Fernandes wrote:
> Looks like PR #90 removes ALL the documentation sources
> with a commit message "Temporarily remove documentation
> until they are fixed...".

Then let me be clear: PR #90 does *not* remove all the documentation, only
the .rst files and the Jamfile.v2 that is processing them.  The .html files
still in the repository *are* correct.

> Why _temporarily_ remove anything?
> Just disable the relevant step in doc/Jamfile?

I figured that removing the .rst source files and the doc/Jamfile.v2 would
make it clear to library users that the existing .html documentation was
not generated by the .rst source files.

Cromwell D. Enage

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost