Just getting back after being sick for a week.
On 10-Jul-09, at 7:18 PM, Brett Porter wrote:
sorry, these changes should have been on a branch. I'll move that
across now so that trunk is still deployable. I'm heading out now
but I can respond to these issues later.
No biggie. I just
+1 on keeping all the release notes online!!
On Sun, Jul 19, 2009 at 8:07 AM, Jason van Zyljvan...@sonatype.com wrote:
Just getting back after being sick for a week.
On 10-Jul-09, at 7:18 PM, Brett Porter wrote:
sorry, these changes should have been on a branch. I'll move that across
now so
On Sat, Jul 11, 2009 at 2:00 AM, Brian Foxbri...@infinity.nu wrote:
I think jira should remain the consolidated list of bugs fixed during
a release. Having it on the site is important, but specifically I
don't want to have yet another file to update each time i fix a bug.
Grabbing the release
Thanks,t hat might be worth a try
On 13/07/2009, at 9:34 AM, Barrie Treloar wrote:
On Sat, Jul 11, 2009 at 2:00 AM, Brian Foxbri...@infinity.nu wrote:
I think jira should remain the consolidated list of bugs fixed during
a release. Having it on the site is important, but specifically I
don't
On 11/07/2009, at 12:27 AM, Jason van Zyl wrote:
* push all release notes into docs/$version/release-notes.html
instead of the consolidated older format and add a page to list
them in order
So if someone wants to see the historical list of changes they will
need to look at N
+1 for all that improve our horrible website.Your proposal is good, giving a
better management of // branches, thus +1
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Fri, Jul 10, 2009 at 7:48 AM, Brett
+1 for all
Emmanuel
On Fri, Jul 10, 2009 at 7:48 AM, Brett Porter br...@apache.org wrote:
Hi,
I've committed some changes that I'd like reviewed to go forward with which
makes Maven releases easier.
1) see http://maven.apache.org/docs/2.0.11-RC1-SNAPSHOT/release-notes.html
(may
not be
On 10-Jul-09, at 1:48 AM, Brett Porter wrote:
Hi,
I've committed some changes that I'd like reviewed to go forward
with which makes Maven releases easier.
1) see http://maven.apache.org/docs/2.0.11-RC1-SNAPSHOT/release-notes.html
(may not be present yet due to proxying), and relevant
2) see commits in site branch.
The basic approach is this:
* push all release notes into docs/$version/release-notes.html instead of
the consolidated older format and add a page to list them in order
So if someone wants to see the historical list of changes they will need to
look at N
I think jira should remain the consolidated list of bugs fixed during
a release. Having it on the site is important, but specifically I
don't want to have yet another file to update each time i fix a bug.
Grabbing the release notes from jira and updating the site is nice and
efficient and pretty
sorry, these changes should have been on a branch. I'll move that
across now so that trunk is still deployable. I'm heading out now but
I can respond to these issues later.
On 11/07/2009, at 12:27 AM, Jason van Zyl wrote:
On 10-Jul-09, at 1:48 AM, Brett Porter wrote:
Hi,
I've committed
Hi,
I've committed some changes that I'd like reviewed to go forward with
which makes Maven releases easier.
1) see http://maven.apache.org/docs/2.0.11-RC1-SNAPSHOT/release-notes.html
(may not be present yet due to proxying), and relevant commits in
that RC branch
2) see commits in
12 matches
Mail list logo
