You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <br...@apache.org> on 2005/09/27 15:08:38 UTC

plan for plugin releases

Hi,

What shall we do for the plugin releases as we lead up to the final?

I'm thinking:
- get them basically finished first (unless the current betas are
fundamentally flawed)
- fix all bugs in the matrix slated for that plugin, polish up docs
(most have had this done by Allan and Johnny - thanks!)
- release a beta
- fix remaining issues
- release final beta of that plugin
- wait for 2.0 release
- upgrade libs and release "final" of the plugin
- celebrate, and move on to the next version :)

I'd very much like them to be done one at a time (not 15 releases at the
same time as the core), and driven by those that primarily use them and
work on the issues.

Sound ok? Any feedback?

Cheers,
Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: plan for plugin releases

Posted by Trygve Laugstøl <tr...@codehaus.org>.
On Thu, 2005-09-29 at 09:26 +1000, Brett Porter wrote:
> anyone?
> 
> Brett Porter wrote:
> 
> >Hi,
> >
> >What shall we do for the plugin releases as we lead up to the final?
> >
> >I'm thinking:
> >- get them basically finished first (unless the current betas are
> >fundamentally flawed)
> >- fix all bugs in the matrix slated for that plugin, polish up docs
> >(most have had this done by Allan and Johnny - thanks!)
> >- release a beta
> >- fix remaining issues
> >- release final beta of that plugin
> >- wait for 2.0 release
> >- upgrade libs and release "final" of the plugin
> >- celebrate, and move on to the next version :)
> >
> >I'd very much like them to be done one at a time (not 15 releases at the
> >same time as the core), and driven by those that primarily use them and
> >work on the issues.
> >
> >Sound ok? Any feedback?

Sounds ok. I'm looking forward to the celebration part ;)

--
Trygve


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: plan for plugin releases

Posted by Emmanuel Venisse <em...@venisse.net>.
+1

Emmanuel

Brett Porter a écrit :
> anyone?
> 
> Brett Porter wrote:
> 
> 
>>Hi,
>>
>>What shall we do for the plugin releases as we lead up to the final?
>>
>>I'm thinking:
>>- get them basically finished first (unless the current betas are
>>fundamentally flawed)
>>- fix all bugs in the matrix slated for that plugin, polish up docs
>>(most have had this done by Allan and Johnny - thanks!)
>>- release a beta
>>- fix remaining issues
>>- release final beta of that plugin
>>- wait for 2.0 release
>>- upgrade libs and release "final" of the plugin
>>- celebrate, and move on to the next version :)
>>
>>I'd very much like them to be done one at a time (not 15 releases at the
>>same time as the core), and driven by those that primarily use them and
>>work on the issues.
>>
>>Sound ok? Any feedback?
>>
>>Cheers,
>>Brett
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>For additional commands, e-mail: dev-help@maven.apache.org
>>
>> 
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: plan for plugin releases

Posted by Brett Porter <br...@apache.org>.
anyone?

Brett Porter wrote:

>Hi,
>
>What shall we do for the plugin releases as we lead up to the final?
>
>I'm thinking:
>- get them basically finished first (unless the current betas are
>fundamentally flawed)
>- fix all bugs in the matrix slated for that plugin, polish up docs
>(most have had this done by Allan and Johnny - thanks!)
>- release a beta
>- fix remaining issues
>- release final beta of that plugin
>- wait for 2.0 release
>- upgrade libs and release "final" of the plugin
>- celebrate, and move on to the next version :)
>
>I'd very much like them to be done one at a time (not 15 releases at the
>same time as the core), and driven by those that primarily use them and
>work on the issues.
>
>Sound ok? Any feedback?
>
>Cheers,
>Brett
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>  
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: plan for plugin releases

Posted by Carlos Sanchez <ca...@apache.org>.
+1

On 9/27/05, Brett Porter <br...@apache.org> wrote:
> Hi,
>
> What shall we do for the plugin releases as we lead up to the final?
>
> I'm thinking:
> - get them basically finished first (unless the current betas are
> fundamentally flawed)
> - fix all bugs in the matrix slated for that plugin, polish up docs
> (most have had this done by Allan and Johnny - thanks!)
> - release a beta
> - fix remaining issues
> - release final beta of that plugin
> - wait for 2.0 release
> - upgrade libs and release "final" of the plugin
> - celebrate, and move on to the next version :)
>
> I'd very much like them to be done one at a time (not 15 releases at the
> same time as the core), and driven by those that primarily use them and
> work on the issues.
>
> Sound ok? Any feedback?
>
> Cheers,
> Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: plan for plugin releases

Posted by John Casey <jd...@commonjava.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry for the late reply...I agree, it's probably time for the release
cycles of the plugins to be somewhat separated, and driven by the needs
of each plugin project.

You got my +1.

- -john

Brett Porter wrote:
| Hi,
|
| What shall we do for the plugin releases as we lead up to the final?
|
| I'm thinking:
| - get them basically finished first (unless the current betas are
| fundamentally flawed)
| - fix all bugs in the matrix slated for that plugin, polish up docs
| (most have had this done by Allan and Johnny - thanks!)
| - release a beta
| - fix remaining issues
| - release final beta of that plugin
| - wait for 2.0 release
| - upgrade libs and release "final" of the plugin
| - celebrate, and move on to the next version :)
|
| I'd very much like them to be done one at a time (not 15 releases at the
| same time as the core), and driven by those that primarily use them and
| work on the issues.
|
| Sound ok? Any feedback?
|
| Cheers,
| Brett
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
| For additional commands, e-mail: dev-help@maven.apache.org
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDPAP7K3h2CZwO/4URArMWAJ97PgKLBY7Ei3ks/UdfonMpXwt+QwCfY8vq
Ec1mLJZM7BFUbcKyCRw8ZfQ=
=SAH6
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

Re: plan for plugin releases

Posted by Arnaud HERITIER <ah...@gmail.com>.
+1

Arnaud

On 9/29/05, Jason van Zyl <ja...@maven.org> wrote:
>
> On Tue, 2005-09-27 at 23:08 +1000, Brett Porter wrote:
> > Hi,
> >
> > What shall we do for the plugin releases as we lead up to the final?
> >
> > I'm thinking:
> > - get them basically finished first (unless the current betas are
> > fundamentally flawed)
> > - fix all bugs in the matrix slated for that plugin, polish up docs
> > (most have had this done by Allan and Johnny - thanks!)
> > - release a beta
> > - fix remaining issues
> > - release final beta of that plugin
> > - wait for 2.0 release
> > - upgrade libs and release "final" of the plugin
> > - celebrate, and move on to the next version :)
> >
> > I'd very much like them to be done one at a time (not 15 releases at the
> > same time as the core), and driven by those that primarily use them and
> > work on the issues.
> >
> > Sound ok? Any feedback?
>
> That plan sounds good, +1
>
> When we don't respond we inherently agree with you!
>
> > Cheers,
> > Brett
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> --
> jvz.
>
> Jason van Zyl
> jason at maven.org <http://maven.org>
> http://maven.apache.org
>
> We know what we are, but know not what we may be.
>
> -- Shakespeare
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: plan for plugin releases

Posted by Jason van Zyl <ja...@maven.org>.
On Tue, 2005-09-27 at 23:08 +1000, Brett Porter wrote:
> Hi,
> 
> What shall we do for the plugin releases as we lead up to the final?
> 
> I'm thinking:
> - get them basically finished first (unless the current betas are
> fundamentally flawed)
> - fix all bugs in the matrix slated for that plugin, polish up docs
> (most have had this done by Allan and Johnny - thanks!)
> - release a beta
> - fix remaining issues
> - release final beta of that plugin
> - wait for 2.0 release
> - upgrade libs and release "final" of the plugin
> - celebrate, and move on to the next version :)
> 
> I'd very much like them to be done one at a time (not 15 releases at the
> same time as the core), and driven by those that primarily use them and
> work on the issues.
> 
> Sound ok? Any feedback?

That plan sounds good, +1

When we don't respond we inherently agree with you!

> Cheers,
> Brett
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

We know what we are, but know not what we may be.

  -- Shakespeare


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org