Hi
The vote has passed. The original proposal was modified based on the
feedback received.
The proposal is now incorporated into the Maven site, and will show up
at the address below once the site has synced:
http://maven.apache.org/developers/retirement-plan-plugins.html
On 2010-12-15 22:52, D
Dennis Lundberg wrote:
One comment I would make is if the plugin moves to another forge (hence different
groupId) a relocation pom should be created at the "old" location - not just an
update to the SCM.
This would mean that we (the Maven project) would have to deploy
relocation POMs everyti
I've done most of the requested changes on the wiki:
* Clarify that reitrement must be announced on the plugin's site
* Add apache-extras.org as a possible forge
* Remove creation of new plugins from the plan
* We can't change the SCM URL for the final release, so we fix the
reports on the site in
org]
> Sent: 15 December 2010 21:52
> To: Maven Developers List
> Subject: [VOTE] Establish a creation and retirement plan for plugins
>
> Hi
>
> No one objected to the proposal I made on November 1. Jason and I have
> polished the proposal based on the comments that
On 2010-12-16 00:17, Brett Porter wrote:
>
> On 16/12/2010, at 10:00 AM, Dennis Lundberg wrote:
>
>> On 2010-12-15 23:03, Jesse Farinacci wrote:
>>> Greetings,
>>>
>>> On Wed, Dec 15, 2010 at 4:52 PM, Dennis Lundberg wrote:
https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+
+1 for the retirement language
I'm confused about the creation language too, but I'm guessing that's
just a sidetrack. For retirement this seems okay, but I'd also urge the
injection of a relocation POM instead of a final release...for the
reasons already covered (related to releasing from a S
+0.9
The proposal starts off talking about creation and retirement and then
speaks exclusively about retirement on step 2 and then step 3 is back
to both.
I'd like to see a clearer outline for creation
-Stephen
On 15 December 2010 21:52, Dennis Lundberg wrote:
> Hi
>
> No one objected to the p
]
Sent: 15 December 2010 21:52
To: Maven Developers List
Subject: [VOTE] Establish a creation and retirement plan for plugins
Hi
No one objected to the proposal I made on November 1. Jason and I have polished
the proposal based on the comments that were made. The final
(?) version can be found he
+1
Agree too on apache-extras.org as a nice place.
2010/12/15 Dennis Lundberg :
> Hi
>
> No one objected to the proposal I made on November 1. Jason and I have
> polished the proposal based on the comments that were made. The final
> (?) version can be found here:
>
> https://cwiki.apache.org/con
+1 for the retirement part of the proposal but I'm a bit confused about
icluding a creation plan (I haven't followed the discussion up to now
though).
The current procedure for adding new plugins IIRC is to first put it in
the sandbox and then call a vote to promote it out of there. Is this
I agree that the final release should be optional. I would also add that the
site must be updated to say the plugin is retired whether it is moved somewhere
else or not.
Ralph
On Dec 15, 2010, at 3:17 PM, Brett Porter wrote:
>
> On 16/12/2010, at 10:00 AM, Dennis Lundberg wrote:
>
>> On 201
On Dec 15, 2010, at 4:52 PM, Dennis Lundberg wrote:
> Hi
>
> No one objected to the proposal I made on November 1. Jason and I have
> polished the proposal based on the comments that were made. The final
> (?) version can be found here:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Prop
On 16/12/2010, at 10:00 AM, Dennis Lundberg wrote:
> On 2010-12-15 23:03, Jesse Farinacci wrote:
>> Greetings,
>>
>> On Wed, Dec 15, 2010 at 4:52 PM, Dennis Lundberg wrote:
>>>
>>> https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins
>>
>>>
On 2010-12-15 23:03, Jesse Farinacci wrote:
> Greetings,
>
> On Wed, Dec 15, 2010 at 4:52 PM, Dennis Lundberg wrote:
>>
>> https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins
>
>>From the proposal:
>
> 2. Make one final release of the plugin
>
> 2. Make one final release of the plugin before it is retired. This
> allows us to make a clean break. The final release must change the POM
> so that SCM URLs are removed or changed to reflect the decision made
> in the vote. If the plugin is moved elsewhere a prominent notice must
> be placed
Greetings,
On Wed, Dec 15, 2010 at 4:52 PM, Dennis Lundberg wrote:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins
>From the proposal:
2. Make one final release of the plugin before it is retired. This
allows us to make a clean break.
Hi
No one objected to the proposal I made on November 1. Jason and I have
polished the proposal based on the comments that were made. The final
(?) version can be found here:
https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins
Please vote on w
17 matches
Mail list logo
