List
Subject: Development process (was: Controlling extension-exported
classes)
That's completely true. I've implemented a new extension mechanism
with little or no documentation in the wiki or on the developers'
list. I was just about the only one committing on trunk at the
That's completely true. I've implemented a new extension mechanism
with little or no documentation in the wiki or on the developers'
list. I was just about the only one committing on trunk at the time,
I was pretty careful to avoid bugs with this new implementation (and
made it number one p
.
- Brett
Jason van Zyl wrote:
> Hi,
>
> If anyone has anything to add take a peek at:
>
> http://docs.codehaus.org/display/MAVEN/Development+Process
>
> Nothing is cast in stone but would be nice to get some feedback as only
> four people I know of have
Hi,
If anyone has anything to add take a peek at:
http://docs.codehaus.org/display/MAVEN/Development+Process
Nothing is cast in stone but would be nice to get some feedback as only
four people I know of have taken a look.
Jason
s should also review before a vote is called. We
might as well have the process sorted and have the vote be a formality
then bounce back and forth after the vote has been issued. So anyone who
is interested in the development process take a look at
http://docs.codehaus.org/display/MAVEN/Developm
I've finally reviewed the dev process and made some edits. I made them
independently so they can relatively easily be rolled back.
a) Put the burden of merging on developers instead of a "release
manager". Changes need to go to the branch sooner and I think this is
what we were doing anyway. Also
[ http://jira.codehaus.org/browse/MNG-1305?page=all ]
Jason van Zyl updated MNG-1305:
---
Component: (was: documentation - general)
design
> Document Maven's own development
[ http://jira.codehaus.org/browse/MNG-1305?page=all ]
Jason van Zyl reopened MNG-1305:
Still needs to be reviewed and I shouldn't have closed this issue until there
was agreement on the document as being final
> Document Maven's ow
[ http://jira.codehaus.org/browse/MNG-1305?page=all ]
Jason van Zyl closed MNG-1305:
--
Resolution: Fixed
Now documented here:
http://docs.codehaus.org/display/MAVEN/Development+Process
May undergo a few changes but that's pretty much the end r
[ http://jira.codehaus.org/browse/MNG-1305?page=comments#action_51737 ]
Brett Porter commented on MNG-1305:
---
I've put this to a vote on the list so we can move forward with it
> Document Maven's own develo
Document Maven's own development process
Key: MNG-1305
URL: http://jira.codehaus.org/browse/MNG-1305
Project: Maven 2
Type: Task
Reporter: Jason van Zyl
There is a thread on the dev mailing list: dev process for 2.0.
arate JIRA projects for each plugin
> Document Maven's own development process
>
>
> Key: MNG-1305
> URL: http://jira.codehaus.org/browse/MNG-1305
> Project: Maven 2
> Type: Task
> Components: docu
would be better but some documentation would work for now.
> Document Maven's own development process
>
>
> Key: MNG-1305
> URL: http://jira.codehaus.org/browse/MNG-1305
> Project: Maven 2
> Type: Tas
[ http://jira.codehaus.org/browse/MNG-1305?page=all ]
Jason van Zyl updated MNG-1305:
---
Assign To: Jason van Zyl
Component: documentation
> Document Maven's own development process
>
>
>
[ http://jira.codehaus.org/browse/MPXDOC-170?page=all ]
Lukas Theussl closed MPXDOC-170:
Resolution: Fixed
> Development Process page with external link
> ---
>
> Key: MPXDOC-170
>
[ http://jira.codehaus.org/browse/MPXDOC-170?page=all ]
Lukas Theussl updated MPXDOC-170:
-
Description:
The "Development Process" menu link in it's current state causes much confusion
to users. (And there is a simple solution).
Alth
)
> Development Process page with external link
> ---
>
> Key: MPXDOC-170
> URL: http://jira.codehaus.org/browse/MPXDOC-170
> Project: maven-xdoc-plugin
> Type: Wish
> Versions: 1.9.2
> Report
This has been fixed in cvs but the change has not been pushed to the
site yet.
--
Dennis Lundberg
Raphaël Piéroni wrote:
the page
http://maven.apache.org/development/branches.html
shows link to "CVS book" the link is
http://www.red-bean.com/cvsbook/
but the correct link is :
http://cvsbook.red-
the page
http://maven.apache.org/development/branches.html
shows link to "CVS book" the link is
http://www.red-bean.com/cvsbook/
but the correct link is :
http://cvsbook.red-bean.com/
R
=
| Raphaël Piéroni |
| 33+ 223 351 354
: MPSITE-14
Summary: Development Process page with external link
Type: Wish
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-site-plugin
Versions:
1.5
Assignee:
Reporter: Geoffrey
overview of the issue:
-
Key: MPXDOC-70
Summary: 'Development Process' link removal
Type: Improvement
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spen
of the issue:
-
Key: MAVEN-877
Summary: development process has link to old wiki
Type: Bug
Status: Closed
Priority: Trivial
Resolution: FIXED
Time Spent: Unknown
Remaining: Unknown
Project
:
-
Key: MAVEN-877
Summary: development process has link to old wiki
Type: Bug
Status: Unassigned
Priority: Trivial
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
documentation
Fix Fors:
1.0-final
Versions
ssue:
-
Key: MAVEN-580
Summary: 'Development Process' link removal
Type: Improvement
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Fix Fors:
1.1
Versions:
:
-
Key: MAVEN-580
Summary: 'Development Process' link removal
Type: Improvement
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Versions:
1.0-beta-10
Assignee:
Reporter: Andy
25 matches
Mail list logo
