You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xmlgraphics.apache.org by bu...@apache.org on 2010/05/12 21:06:27 UTC
DO NOT REPLY [Bug 49280] New: Release version 1.4
https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
Summary: Release version 1.4
Product: XMLGraphicsCommons
Version: Trunk
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Utilities
AssignedTo: general@xmlgraphics.apache.org
ReportedBy: spepping@apache.org
Release version 1.4
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 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 49280] Release version 1.4
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
--- Comment #3 from Simon Pepping <sp...@apache.org> 2010-05-25 05:17:16 EDT ---
Step 4: Releasing
4a. Make the Artifacts Available
* Upload to people.apache.org. (An account on minotaur is needed):
o scp xmlgraphics-commons-1.4-bin-*
<you>@people.apache.org:/www/www.apache.org/dist/xmlgraphics/commons/binaries/
o scp xmlgraphics-commons-1.4-src.*
<you>@people.apache.org:/www/www.apache.org/dist/xmlgraphics/commons/source/
* Check permissions: chmod 664 ... ; chgrp xmlgraphics ...
* Make a test download.
* Update HEADER.html and README.html in
people.apache.org:/www/www.apache.org/dist/xmlgraphics/commons/
4b. Make and release Maven Artifacts
* Instructions on how to build the Maven artifacts for Commons, see Maven.
4c. Merge Back the Changes in the Trunk
* svnmerge.py is your friend. Only the version number must not be merged
back (that's why it's important to commit atomic changes). Note: Change from
using svnmerge.py to svn 1.5's inbuilt merge support.
* Put the exact release date in the website sources: status.xml and
xdocs/news.xml
* Update src/documentation/content/doap.rdf
* Publish the website
4d. Post Announcements
* Wait 24 hours (for the mirrors to catch up).
* Post announcements on general@xmlgraphics.apache.org and other related
mailing lists. Note: Which?
* Add the release version to the XMLGraphicsCommons Bugzilla component
(just ask Christian as he has Bugzilla karma to do it)
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: Release version 1.4
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:06:27PM -0400, bugzilla@apache.org wrote:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
>
> Summary: Release version 1.4
> Product: XMLGraphicsCommons
> Version: Trunk
> Platform: All
> OS/Version: All
> Status: NEW
> Severity: normal
> Priority: P2
> Component: Utilities
> AssignedTo: general@xmlgraphics.apache.org
> ReportedBy: spepping@apache.org
>
>
> Release version 1.4
>
> 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 wiki.
--
Simon Pepping
home page: http://www.leverkruid.eu
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 49280] Release version 1.4
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
--- Comment #6 from Simon Pepping <sp...@apache.org> 2010-07-10 10:26:16 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 49280] Release version 1.4
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
--- Comment #5 from Simon Pepping <sp...@apache.org> 2010-06-02 02:04:38 EDT ---
(In reply to comment #4)
> Regarding step 1:
>
> I think that the bugs/enhancements with a PATCH provided should also be looked
> at:
> If the changes are simple, and do not introduce an incompatibility, they should
> also be put in the release.
>
> I am willing to produce patches for pending bugs
>
> Any thoughts ?
This release is long overdue, and I am going to proceed.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: DO NOT REPLY [Bug 49280] Release version 1.4
Posted by Simon Pepping <sp...@leverkruid.eu>.
Wednesday I did some work on the release. Now I have a new
assignment. This makes it likely that I will resume work on the
release in early July.
Simon
On Tue, May 25, 2010 at 11:29:23AM +0200, Simon Pepping wrote:
> Step 1, list blocking bugs, and step 2 below are more or less the same
> activities. Until now no blocking bugs have been reported. With some
> luck I will start working on the release next week.
>
> Simon
>
> On Tue, May 25, 2010 at 05:09:45AM -0400, bugzilla@apache.org wrote:
> > https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
> >
> > --- Comment #1 from Simon Pepping <sp...@apache.org> 2010-05-25 05:09:43 EDT ---
> > Step 2: Before the Release
> >
> > * Determine whether further testing is required.
> > * Commit any outstanding changes
--
Simon Pepping
home page: http://www.leverkruid.eu
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: DO NOT REPLY [Bug 49280] Release version 1.4
Posted by Simon Pepping <sp...@leverkruid.eu>.
Step 1, list blocking bugs, and step 2 below are more or less the same
activities. Until now no blocking bugs have been reported. With some
luck I will start working on the release next week.
Simon
On Tue, May 25, 2010 at 05:09:45AM -0400, bugzilla@apache.org wrote:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
>
> --- Comment #1 from Simon Pepping <sp...@apache.org> 2010-05-25 05:09:43 EDT ---
> Step 2: Before the Release
>
> * Determine whether further testing is required.
> * Commit any outstanding changes
--
Simon Pepping
home page: http://www.leverkruid.eu
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 49280] Release version 1.4
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
--- Comment #1 from Simon Pepping <sp...@apache.org> 2010-05-25 05:09:43 EDT ---
Step 2: Before the 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 49280] Release version 1.4
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
Simon Pepping <sp...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
Re: DO NOT REPLY [Bug 49280] Release version 1.4
Posted by Simon Pepping <sp...@leverkruid.eu>.
Hi Julien,
I am pleased to see your interest in and contributions to the
XMLGraphics Commons project. However, this release is long overdue,
and I am going to proceed. When enough patches are added, we can have
another release.
Simon
On Thu, May 27, 2010 at 09:03:46AM -0400, bugzilla@apache.org wrote:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
>
> --- Comment #4 from Julien Aymé <ju...@gmail.com> 2010-05-27 09:03:41 EDT ---
> Regarding step 1:
>
> I think that the bugs/enhancements with a PATCH provided should also be looked
> at:
> If the changes are simple, and do not introduce an incompatibility, they should
> also be put in the release.
>
> I am willing to produce patches for pending bugs
>
> Any thoughts ?
>
> --
> Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are the assignee for the bug.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: general-help@xmlgraphics.apache.org
>
--
Simon Pepping
home page: http://www.leverkruid.eu
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 49280] Release version 1.4
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
--- Comment #4 from Julien Aymé <ju...@gmail.com> 2010-05-27 09:03:41 EDT ---
Regarding step 1:
I think that the bugs/enhancements with a PATCH provided should also be looked
at:
If the changes are simple, and do not introduce an incompatibility, they should
also be put in the release.
I am willing to produce patches for pending bugs
Any thoughts ?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org
DO NOT REPLY [Bug 49280] Release version 1.4
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49280
--- Comment #2 from Simon Pepping <sp...@apache.org> 2010-05-25 05:13:31 EDT ---
Step 3: Preparing the Release
* Create a temporary branch for the release: svn copy
https://svn.apache.org/repos/asf/xmlgraphics/commons/trunk
https://svn.apache.org/repos/asf/xmlgraphics/commons/branches/commons-1_4
* Checkout a copy of the new branch and work on it from now on
* Edit release notes (README, status.xml in the root and in xdocs).
* Update version number in build.xml, and commit the change. Also update
the version number in the Trunk version of build.xml and commit it. This is the
only change in the branch that won't have to be merged back in the Trunk.
* Update the index.xml for the new version.
* Make a test build and check everything's ok
* Tag the source tree with the release ID: svn copy
https://svn.apache.org/repos/asf/xmlgraphics/commons/branches/commons-1_4
https://svn.apache.org/repos/asf/xmlgraphics/commons/tags/commons-1_4
* Make a fresh checkout with the just created tag:
https://svn.apache.org/repos/asf/xmlgraphics/commons/tags/commons-1_4
* Alternatively, create a build-local.properties file that points to the
above libs.
* Run ant[.sh] dist. Do this with Sun JDK 1.4.2_08 or later. A Forrest
installation is needed.
* Create signatures if they are not already added by the dist build. Don't
forget to upload your KEY: gpg -a -b --force-v3-sigs
xmlgraphics-commons-1.4.tar.gz etc.
* Add MD5 sums if they are not already added by the dist build: md5
xmlgraphics-commons-1.4-bin.tar.gz > xmlgraphics-commons-1.4-bin.tar.gz.md5
* Upload the release files to your "public_html" on people.apache.org and
start a release vote on general@xmlgraphics.apache.org quoting the MD5 values
for each file and their URLs.
* After the 72h release vote send a summary to
general@xmlgraphics.apache.org and CC private@xmlgraphics.apache.org.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: general-help@xmlgraphics.apache.org