You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2010/05/12 21:08:44 UTC
DO NOT REPLY [Bug 49281] New: Release version 1.0
https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
Summary: Release version 1.0
Product: Fop
Version: 1.0dev
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: fop-dev@xmlgraphics.apache.org
ReportedBy: spepping@apache.org
Release version 1.0
Step 1: List all bugs that must be solved before a release can take place
(release critical bugs). Make this bug depend on each release critical bug and
write a short argument why the bug is release critical.
Steps 2ff: See web site.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 49281] Release version 1.0
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
Glenn Adams <gl...@skynav.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #5 from Glenn Adams <gl...@skynav.com> 2012-03-28 06:27:27 UTC ---
this is good process information that should be exported into the FOP Dev docs
or FOP Wiki
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 49281] Release version 1.0
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
--- Comment #1 from Simon Pepping <sp...@apache.org> 2010-07-02 08:56:53 EDT ---
Step 2: Before the release
# Determine whether this is a Release Candidate or a Release.
# Determine whether further testing is required.
# Commit any outstanding changes
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 49281] Release version 1.0
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
--- Comment #6 from Glenn Adams <gl...@skynav.com> 2012-04-06 21:52:04 UTC ---
update release checklist in site docs at:
http://xmlgraphics.apache.org/fop/dev/release.html
see http://svn.apache.org/viewvc?view=revision&revision=1310603
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Re: Release version 1.0
Posted by The Web Maestro <th...@gmail.com>.
You're just doing this so you have something to talk about in the next
Board update! J/k!
I bet it felt *good* to create that BugZilla entry!
Thanks for your efforts!
Clay
On Wednesday, May 12, 2010, Simon Pepping <sp...@leverkruid.eu> wrote:
> Indeed, this means that I have a vague plan to work on this. Since I
> have lots of other things to do and because it is summer, I cannot
> make a firm commitment. Moreover, I filed this bug in advance, so that
> there is time for everyone to think about release critical bugs.
>
> Simon
>
> On Wed, May 12, 2010 at 03:08:44PM -0400, bugzilla@apache.org wrote:
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
>>
>> Summary: Release version 1.0
>> Product: Fop
>> Version: 1.0dev
>> Platform: All
>> OS/Version: All
>> Status: NEW
>> Severity: normal
>> Priority: P2
>> Component: general
>> AssignedTo: fop-dev@xmlgraphics.apache.org
>> ReportedBy: spepping@apache.org
>>
>>
>> Release version 1.0
>>
>> Step 1: List all bugs that must be solved before a release can take place
>> (release critical bugs). Make this bug depend on each release critical bug and
>> write a short argument why the bug is release critical.
>>
>> Steps 2ff: See web site.
>
> --
> Simon Pepping
> home page: http://www.leverkruid.eu
>
--
Regards,
The Web Maestro
--
<th...@gmail.com> - <http://ourlil.com/>
My religion is simple. My religion is kindness.
- HH The 14th Dalai Lama of Tibet
Re: Release version 1.0
Posted by Simon Pepping <sp...@leverkruid.eu>.
Indeed, this means that I have a vague plan to work on this. Since I
have lots of other things to do and because it is summer, I cannot
make a firm commitment. Moreover, I filed this bug in advance, so that
there is time for everyone to think about release critical bugs.
Simon
On Wed, May 12, 2010 at 03:08:44PM -0400, bugzilla@apache.org wrote:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
>
> Summary: Release version 1.0
> Product: Fop
> Version: 1.0dev
> Platform: All
> OS/Version: All
> Status: NEW
> Severity: normal
> Priority: P2
> Component: general
> AssignedTo: fop-dev@xmlgraphics.apache.org
> ReportedBy: spepping@apache.org
>
>
> Release version 1.0
>
> Step 1: List all bugs that must be solved before a release can take place
> (release critical bugs). Make this bug depend on each release critical bug and
> write a short argument why the bug is release critical.
>
> Steps 2ff: See web site.
--
Simon Pepping
home page: http://www.leverkruid.eu
DO NOT REPLY [Bug 49281] Release version 1.0
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
--- Comment #2 from Simon Pepping <sp...@apache.org> 2010-07-02 09:02:43 EDT ---
Step 3: Preparing the release
# Create a branch called branches/fop-v_vv
# Edit release notes (README and status.xml in the root).
# Update the index.xml, site.xml and download.xml for the new version.
# Update the version numbers in the release column on the compliance page
(compliance.xml); update the compliance in the release column to the current
state (development column).
# Update version number in build.xml (not to be merged back into trunk).
# Copy trunk documentation directory to a new directory with the version
number, and update any links and the .htaccess file for redirections.
# Copy test/fotree/disabled-testcases.xml and
test/layoutengine/disabled-testcases.xml to the new version directory
<version>/fotree/disabled-testcases.xml and
<version>/layoutengine/disabled-testcases.xml. Copy known-issues.xml to the new
version directory. Copy knownissues-overview.xml from the previous to the new
version directory.
# Delete the previous version directory.
# Build the dist files (build[.sh] dist) and upload them to your web directory
on people.apache.org
# Ask on fop-dev to check the branch and the generated dist files for errors.
# Tag the source tree with the release ID. For example, if the release is 1.0:
svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-1_0
https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0
# Make a fresh checkout with the just created tag: svn co
https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0
# Copy the hyphenation patterns jar file fop-hyph.jar to lib/ (e.g. from
http://sourceforge.net/projects/offo
# Alternatively, create a build-local.properties file that points to the above
libs.
# Run build[.sh] dist. Do this using Sun JDK 1.4.2_08 or later. A Forrest
installation is needed.
# Create signatures. Don't forget to upload your KEY: gpg -a -b --force-v3-sigs
fop-1.0-src.tar.gz etc.
# Upload the dist and signature files to your web directory on
people.apache.org (An account on minotaur is needed): scp fop-1.0*.tar.gz*
<your name>@people.apache.org:public_html/ etc.
# Check permissions: chmod 664 ... ; chgrp xmlgraphics ...
# Add MD5 sums: md5 fop-1.0-src.tar.gz > fop-1.0-src.tar.gz.md5 etc.
# Make a test download.
# Start a vote for the release on general@xmlgraphics.a.o. The message should
point to the release files and list the MD5 sums (cat *.md5). The vote is open
for 72hrs.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 49281] Release version 1.0
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
--- Comment #3 from Simon Pepping <sp...@apache.org> 2010-07-02 09:04:21 EDT ---
Step 4: After the release
# When the release is accepted, copy the release files, their md5 sum files and
the signature files to /www/www.apache.org/dist/xmlgraphics/fop/ in the
subdirectories source and binaries. Create links to all files in the fop
directory. Remove the links to the files of the previous version.
# Update HEADER.html and README.html in
people.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/
# Wait 24 hours (for the mirrors to catch up).
# Merge the changes of the subversion release branch back into trunk (not the
version number in the build file) and delete the branch.
# Deploy the updated documentation to the FOP website.
# Post announcements on fop-dev and fop-user and other related mailing lists.
# Ask a Bugzilla admin (Christian Geisert) to add a bugzilla entry for the new
release id, or create an issue at https://issues.apache.org/jira/browse/INFRA.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
DO NOT REPLY [Bug 49281] Release version 1.0
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49281
Simon Pepping <sp...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #4 from Simon Pepping <sp...@apache.org> 2010-07-23 02:51:01 EDT ---
Almost completed. Left to be done: deploy the maven bundle. I have no
experience with Maven and I do not have it installed, so I cannot do this task.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.