search for: releaseprocess

Hi, (this is general Xiph.org project stuff, not sure what lists are more appropriate) I just made a stab at documenting a release project for Xiph.org, as taught to me recently by Ralph when I moved liboggz and libfishsound over to Xiph.org: http://wiki.xiph.org/index.php/ReleaseProcess Please edit! and please add a link from the Project Management part of the main page :-) Also the reason I cross-posted to advocacy is: if you know appropriate mailing lists etc. to send release announcements to, please add them. cheers, Conrad.

Hi, I have just tagged the first release candidate for the 3.4.1 release, so testers may begin testing. Please refer to http://llvm.org/docs/ReleaseProcess.html for information on how to validate a release. If you have any questions or need something clarified, just email the list. For the 3.4.1 release we want to compare test results against 3.4-final. I have added support to the test-release.sh script for dot releases and have done basic testing....

...ked the article you linked because it seemed to be targeted at an audience of external developers and packagers, for whom we don't (AFAIK) really have any docs about the release process, how to get involved, etc. Since the audience is different, I think it should be its own page (probably "ReleaseProcess.rst" would be fine, but I don't have a strong preference). -- Sean Silva -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130525/ef64f761/attachment.html>

...linked because it seemed to be targeted at an > audience of external developers and packagers, for whom we don't (AFAIK) > really have any docs about the release process, how to get involved, etc. > Since the audience is different, I think it should be its own page > (probably "ReleaseProcess.rst" would be fine, but I don't have a strong > preference). > Hi Sean, I've created ReleaseProcess.rst, how can I force generation of HTML on the rst file without rebuilding the whole thing? cheers, --renato -------------- next part -------------- An HTML attachment was scrub...

...t seemed to be targeted at an >> audience of external developers and packagers, for whom we don't (AFAIK) >> really have any docs about the release process, how to get involved, etc. >> Since the audience is different, I think it should be its own page >> (probably "ReleaseProcess.rst" would be fine, but I don't have a strong >> preference). >> > > Hi Sean, > > I've created ReleaseProcess.rst, how can I force generation of HTML on the > rst file without rebuilding the whole thing? > > The following incantation should work (invoke...

Hi, I have tagged the 3.6.1-rc1 so testing can begin. We can always use more testers, so if you are interested in helping, let me know. Instructions for validating an LLVM release can be found here: http://llvm.org/docs/ReleaseProcess.html Reminder: We are using 3.6.0 as our baseline for regression testing. Thanks, Tom

Hi, 3.5.1-rc1 has been tagged, so it is time to begin testing. We can always use more testers, so if you would like to volunteer, let me know. For those that are new to testing, please review the documentation for how validate a new release: http://llvm.org/docs/ReleaseProcess.html Remember that when we check for regressions we want to compare the test results of 3.5.1-rc1 with 3.5.0-final. There is one undocumented step, which is how to package build/package the binaries so they can be uploaded to the website. I think there may be a script for this, but I'm not s...

...recently have changed to allow more C++11 goodness, and I have no idea about Mingw. Also, is there *any* pre-GPLv3 GCC in Mac or BSD that can compile Clang at this day and age? Please, let me know and I'll update the doc to the appropriate values. cheers, --renato [1] http://llvm.org/docs/ReleaseProcess.html

Vedant, Thanks for building the packages before. Could you detail what's required to build these binaries on macOS so that someone else could replicate it? Thanks, Tobias On Mon, Oct 14, 2019 at 8:29 PM Vedant Kumar via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Gio, > > I prepared the macOS packages for the past few releases, but have less time to keep up with

...at my logs, it looks like the test-suite used to configure in 3.6.2 but didn't build as part of test-release.sh and then 3.7.0 stopped since we had switched to cmake and there was no CMakeLists.txt. > I've always run the test-suite as a separate step as described in http://llvm.org/docs/ReleaseProcess.html. Should we stop creating the projects/test-suite symlink to get back to the behaviour from 3.7.0 or should we do something else? Yes, I made the script stop making the symlink in r257791 and merged it to the branch. Did that not work for you, or were you at an earlier revision? Thanks, Hans

...eemed to be targeted at an audience of external developers and >>> packagers, for whom we don't (AFAIK) really have any docs about the release >>> process, how to get involved, etc. Since the audience is different, I think >>> it should be its own page (probably "ReleaseProcess.rst" would be fine, but >>> I don't have a strong preference). >>> >> >> Hi Sean, >> >> I've created ReleaseProcess.rst, how can I force generation of HTML on >> the rst file without rebuilding the whole thing? >> >> > The...

I see that some of the announcements of binaries for Windows include the script using for compiling. Is there anything similar (or some other form of documentation) for the binaries distributed on http://releases.llvm.org/download.html for other platforms? (I'm particularly interested in Ubuntu) Thanks, Maurizio -------------- next part -------------- An HTML attachment was scrubbed...

...suite used to configure in 3.6.2 but >> didn't build as part of test-release.sh and then 3.7.0 stopped since we had >> switched to cmake and there was no CMakeLists.txt. >> > I've always run the test-suite as a separate step as described in >> http://llvm.org/docs/ReleaseProcess.html. Should we stop creating the >> projects/test-suite symlink to get back to the behaviour from 3.7.0 or should >> we do something else? >> >> Yes, I made the script stop making the symlink in r257791 and merged >> it to the branch. Did that not work for you, or wer...

Hi Oliver, If you look at http://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library that lists the tools and minimum version required. There is some documentation for how to build a release: http://llvm.org/docs/ReleaseProcess.html For the official windows builds, Hans Wennborg provides the batch file used to create any given upload when he reports on the release-testers list (e.g. http://lists.llvm.org/pipermail/release-testers/2018-March/000677.html). The steps for unix based are mostly encoded into the test-release....

Hi, if I wanted to reproduce the official build, for example in order to get a code-signed Windows build [1], to which documentation can I turn to find out about the steps and tools (and their versions) used? That is, I am interested in the steps done by the respective maintainers which yield the packages at http://releases.llvm.org/download.html Thanks and with best regards, Oliver [1] I

And so the release process begins. The 3.8 branch was created today from trunk at r257626, and the trunk version was then bumped to 3.9. Release blockers are tracked by http://llvm.org/PR26059. If you find any bugs (either new or already in the tracker) that you think need to be fixed before the release, please mark them as blocking this bug. To get a change committed on the branch, first

...is > mostly automated, so all it really requires is some spare CPU cycles. > I have created the rc2 tag, so testing can begin. We could still use testers, so if you are interested, let me know. The testing is pretty simple, and you can find detailed instructions here: http://llvm.org/docs/ReleaseProcess.html Since rc1 was a practice release candidate, you will want to compare the test results from 3.3.1-rc2 with 3.3 final. There is a new argument for the test-release.sh script: -dot for specifying the dot release number, so when testing 3.3.1-rc2 you should invoke the script like this: ./test-r...

On 03/10/2014 03:37 PM, Eric Christopher wrote: > cc'ing Bill as Release Manager > > On Mon, Mar 10, 2014 at 2:53 PM, reed kotler <rkotler at mips.com> wrote: >> I'm trying to understand how Mips will fit into the official release >> procedure. >> >> There are two Mips compilers: >> 1) The X86 resident llvm/clang compiler that can generate

...t 09:57:32AM -0400, Tom Stellard wrote: > On Fri, Apr 11, 2014 at 03:02:21PM -0700, Tom Stellard wrote: > > Hi, > > > > I have just tagged the first release candidate for the > > 3.4.1 release, so testers may begin testing. Please refer to > > http://llvm.org/docs/ReleaseProcess.html for information on how to > > validate a release. If you have any questions or need > > something clarified, just email the list. > > > > For the 3.4.1 release we want to compare test results against 3.4-final. > > > > I have added support to the test-rel...

...hing on this list. Stable releases need to be a community effort, there is too much work for just a few people to do. 2. Choose a release manger. I will volunteer for this, but if someone else wants to do it, I have no problem relinquishing the role. 3. Make sure this page: http://llvm.org/docs/ReleaseProcess.html is updated and correct: It would be great if someone who just participated in the release process could look over this page and make sure it is correct and easy to follow. For example, to me it's not clear how to compare the results of the test-release.sh script from different release...