Hi Mike,
On Thu, 2008-12-11 at 05:11 -0500, Mike Frysinger wrote:
> On Thursday 11 December 2008 04:28:34 Subrata Modak wrote:
> > On Fri, 2008-12-05 at 12:36 -0500, Mike Frysinger wrote:
> > > On Friday 05 December 2008 10:41:45 Dmitry Guryanov wrote:
> > > > On Friday 05 December 2008 02:12:52 pm Pradeep K Surisetty wrote:
> > > > > i run autoconf. Build fails here too. It requires higher
> > > > > version of autoconf (2.61 or higher).
> > > > > Please find the below logs.
> > > > >
> > > > >
> > > > > <machine> ltp-full-20081130]# make autoconf
> > > > > autoconf
> > > > > configure.ac:1: error: Autoconf version 2.61 or higher is required
> > > > > configure.ac:1: the top level
> > > > > autom4te: /usr/bin/m4 failed with exit status: 63
> > > > > make: *** [configure] Error 63
> > > >
> > > > I think it will be good to publish ltp releases with created
> > > > ./configure script, Because not all distributions has autoconf >= 2.61
> > > > and not all users knows how to use it.
> > >
> > > it should be. i dont know how Subrata makes releases, but i'm guessing
> > > we should add a "dist" target so all these little gotchas can be
> > > prevented.
> >
> > Please go ahead and add it/them to the CVS.
>
> could you describe how you currently make a release tarball ?
I just follow a documentation procedure my predecessors´ followed at IBM
and left for me. I can summarise them as:
External Process:
* Build Release
* Document all major changes since previous release in
ChangeLog:
1. Run: #cvs log -d "MM/DD/YY<MM/DD/YY" > cvslog
* The first MM/DD/YY should be the date of
the previous release, and the second
MM/DD/YY should be the current release
date. Use the file, "output", to
retrieve the ChangeLog information.
2. You must now update the ChangeLog file using the
information contained in the changelog file.
* Commit the ChangeLog file to the CVS tree: #cvs commit
ChangeLog
* Create the LTP release package: #cvs export -D "MONTH
DAY, YEAR HH:MMam/pm" ltp
* This will pull down the latest LTP without the
CVS directories. Make sure to use the current
date and time.
* Check the ChangeLog file to make sure your
updates are there.
* Remove the "scratch" directory and any tests still in
development.
* Rename /ltp directory to /ltp-full-YYYYMMDD
* Copy the /ltp-full-YYYYMMDD directory
to /ltp-base-YYYYMMDD: # cp -r ltp-full-YYYYMMDD
ltp-base-YYYYMMDD
* Move the commands, network, open_posix_testsuite, and
open_hpi_testsuite directories out
of /ltp-base-YYYYMMDD/testcases, leaving only the
kernel and misc directories:
* /testcases # mv commands ../../
* /testcases # mv network ../../
* /testcases # mv open_hpi_testsuite ../../
* /testcases # mv open_posix_testsuite ../../
* Create the 6 g'zipd tarball release packages:
* # tar -czf ltp-full-YYYYMMDD.tgz
ltp-full-YYYYMMDD
* # tar -czf ltp-base-YYYYMMDD.tgz
ltp-base-YYYYMMDD
* # tar -czf ltp-commands_module-YYYYMMDD.tgz
commands
* # tar -czf ltp-network_module-YYYYMMDD.tgz
network
* # tar -czf
ltp-open_hpi_testsuite_module-YYYYMMDD.tgz
open_hpi_testsuite
* # tar -czf
ltp-open_posix_testsuite_module-YYYYMMDD.tgz
open_posix_testsuite
* Verify Release (optional)
* Untar release onto a Intel-based and PowerPC64-based
test machine.
* Execute and verify a successful build and install on
both machines.
* 32-bit on Intel
* 32-bit on PPC64
* 64-bit on PPC64
* Execute "runalltests.sh" script and verify results, i.e.
no surprise failures
* Post the results on the ltp-results mailing list.
* Compose Announcement
* Announcement should contain any major updates, changes,
and additions to the LTP.
* Include the ChangeLog to the bottom.
* Send to Robbert Williamson for approval.
* Example:
The Linux Test Project test suite
<http://www.linuxtestproject.org> has
been released. The latest version of the testsuite
contains 2100+ tests
for the Linux OS. Our web site also contains other
information such as:
test results, a Linux test tools matrix, technical
papers and HowTos on
Linux testing, and a code coverage analysis tool.
Developers from the Linux Test Project co-authored the
whitepaper,
"Putting Linux Reliability to the Test". This article
documents the
test results and analysis of the Linux kernel and other
core OS
components, including everything from libraries and
device drivers to
file systems and networking, all under some fairly
adverse conditions,
over a period of 60 days. You can find the paper at:
http://www.ibm.com/developerworks/linux/library/l-rel
Release Highlights:
* Code cleanups by Erik Andersen, Glen Foster,
Jay Turner, and
Ming Gao.
* Removal of a memory leak in one of the test
harness libraries
by Randy Hron.
* Improvements to allow tests to build and
execute under more
environments and distributions.
We encourage the community to post results to
[EMAIL PROTECTED],
and patches, new tests, or comments/questions to
[EMAIL PROTECTED]
See ChangeLog below.
* Upload Release to Sourceforge
* Follow upload instructions to FTP package to
Sourceforge
* Log into Sourceforge with ID
* Go to LTP New Release Management page.
* The "Release Name" should be "ltp-YYYYMMDD"
* Status should be "Active"
* Package should be "ltp"
* Copy ChangeLog information into "Change Log"
section
* Check the "Preserve my pre-formatted text" box
* Press Submit button and verify proper
formatting
* Check the LTP package in the "Add Files to this
Release" section
* Press "Add Files and/or Refresh View" button
* Change Processor field to "Any" and File Type to
"Source .gz"
* Press "Update/Refresh"
* Press "Send Notice"
* Rename previous release to "*OLD* YYYYMMDD"
* Verify release by going to LTP "Files" section.
* Update the website with the latest announcement,
highlights and links to the latest release.
* Send APPROVED announcement to appropriate locations
* Websites
* Sourceforge
* Newsforge
* Your Name: (Your Name)
* Your Email or Homepage: ltp.sf.net
* Headline: The Linux Test project
ltp-YYYYMMDD released
* Topic: Announcements
* Freshmeat (You must have an ID)
* Choose appropriate release focus
* Fill out version with ltp-YYYYMMDD
* Fill out changes with announcement
* Make sure to update the ChangeLog cvsweb
link.
* Mailing Lists - Make sure to include "[ANNOUNCE]" to the
beginning of the subject line.
* Kernel.org
* LTP
* LTP Announcements
Although, there has been some changes in the above process owning to
changes in the no. of packages.
Regards--
Subrata
> -mike
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
