You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Lukas Theussl <lt...@apache.org> on 2009/07/24 11:05:51 UTC

site plugin release planning

Hi,

I was looking at the jira roadmap for the site plugin, thinking about a release 
plan for 2.1. The main change so far is the upgrade to doxia 1.1, I think it would 
be a good idea to concentrate the next release on issues that are related that. In 
particular, I'd like to fix all these annoying bugs with links (eg MSITE-395, 
MSITE-404, MSITE-409 and many others), which might necessitate another doxia release.


Right now there are also a number of other issues scheduled that are not related 
(eg MSITE-79, MSITE-206, MSITE-326) which I would like to leave out and schedule 
for a later release.


Is this ok with everyone?
-Lukas

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


Re: site plugin release planning

Posted by Joerg Hohwiller <jo...@j-hohwiller.de>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Hi,

Hello,

> 
> I was looking at the jira roadmap for the site plugin, thinking about a
> release plan for 2.1. The main change so far is the upgrade to doxia
> 1.1, I think it would be a good idea to concentrate the next release on
> issues that are related that. In particular, I'd like to fix all these
> annoying bugs with links (eg MSITE-395, MSITE-404, MSITE-409 and many
> others), which might necessitate another doxia release.
> 

great to hear.
Did already someone report that if <distributionManagement>
is present but has no <site> then site:stage fails.
This is bad if you need to have <distributionManagement>
for having a <repository> section.

I personally think that the entire <distributionManagement>
in the pom.xml was a design mistake because this is something
that should be covered by settings.xml but however...

I currently comment out my <distributionManagement>
to invoke site:stage and get the expected result
because with a <site> section wired subfolders are created
that break my rsync-script.

Shall I file a jira ticket or is this already known?

> 
> Right now there are also a number of other issues scheduled that are not
> related (eg MSITE-79, MSITE-206, MSITE-326) which I would like to leave
> out and schedule for a later release.
> 
> 
> Is this ok with everyone?
> -Lukas

+1 for me but I am no committer...

Thanks
  Jörg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkpqCEsACgkQmPuec2Dcv/8w4gCePN6jqbMPLVb28Kfh30ETeyf7
jqIAoJbE6jMzKn0AN/4lSuk8B1boGmWN
=P0+H
-----END PGP SIGNATURE-----

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


Re: site plugin release planning

Posted by Dennis Lundberg <de...@apache.org>.
Lukas Theussl wrote:
> 
> 
> Dennis Lundberg wrote:
>> Lukas Theussl wrote:
>>> Hi,
>>>
>>> I was looking at the jira roadmap for the site plugin, thinking about a
>>> release plan for 2.1. The main change so far is the upgrade to doxia
>>> 1.1, I think it would be a good idea to concentrate the next release on
>>> issues that are related that. In particular, I'd like to fix all these
>>> annoying bugs with links (eg MSITE-395, MSITE-404, MSITE-409 and many
>>> others), which might necessitate another doxia release.
>>
>> It's good to keep the releases small and focused. So +1 from me for a
>> special Doxia upgrade release.
>>
>> +1 also for fixing the path issues you mentioned in the near future. My
>> findings on those issues are that the problem lies somewhere inside
>> Doxia, so I think another Doxia release will be necessary. If that is
>> the case, I think it is wise to do a release of the Site plugin with
>> Doxia 1.1.1 first.
> 
> 
> I have fixed DOXIASITETOOLS-29 and checked that MSITE-404 gets fixed
> with it.

That's great news!

One question on this though, as I read through your commits: Doesn't
Doxia Sitetools need to upgrade it's dependency on Plexus Utils, since
DOXIASITETOOLS-29 is related to PLXUTILS-116? Or did you work around
PLXUTILS-116 in your patch for DOXIASITETOOLS-29?

> My preference would be to bump the doxia dep in site-plugin to
> 1.1.2-SNAP, and push the number of MSITE issues down, fixing doxia bugs
> as we go along (finally we can use the site plugin to test doxia
> again... :) ). Some of the open issues have blocker status so I don't
> see the point of another site release before those are fixed. WDYT?

I have difficulties making my mind up about this.

On one hand I think it would be good to get Doxia 1.1.x out ASAP to have
it tried in the real world. If we delay the real world deployment for
too long, the jump might be to high to release it and it might also drag
out over time.

On the other hand I acknowledge that the issues you listed are very
important to fix, because they are causing users a lot of grief. The
blocker status has often been set by users rather than developers though.

I do believe that MSITE-404 is the core of these issues and if that is
fixed the others might be solved as well.

Let's do a 1.1.2 release of Doxia and have Site plugin 2.1 use that
version. But let us keep the number of bug fixes for 1.1.2 low, so that
it can be released fairly soon.

> 
> -Lukas
> 
> 
>>
>>> Right now there are also a number of other issues scheduled that are not
>>> related (eg MSITE-79, MSITE-206, MSITE-326) which I would like to leave
>>> out and schedule for a later release.
>>
>> +1 to leave those issues out.
>>
>>>
>>> Is this ok with everyone?
>>> -Lukas
>>>
>>> ---------------------------------------------------------------------
>>> 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
> 
> 


-- 
Dennis Lundberg

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


Re: site plugin release planning

Posted by Lukas Theussl <lt...@apache.org>.

Dennis Lundberg wrote:
> Lukas Theussl wrote:
>> Hi,
>>
>> I was looking at the jira roadmap for the site plugin, thinking about a
>> release plan for 2.1. The main change so far is the upgrade to doxia
>> 1.1, I think it would be a good idea to concentrate the next release on
>> issues that are related that. In particular, I'd like to fix all these
>> annoying bugs with links (eg MSITE-395, MSITE-404, MSITE-409 and many
>> others), which might necessitate another doxia release.
> 
> It's good to keep the releases small and focused. So +1 from me for a
> special Doxia upgrade release.
> 
> +1 also for fixing the path issues you mentioned in the near future. My
> findings on those issues are that the problem lies somewhere inside
> Doxia, so I think another Doxia release will be necessary. If that is
> the case, I think it is wise to do a release of the Site plugin with
> Doxia 1.1.1 first.


I have fixed DOXIASITETOOLS-29 and checked that MSITE-404 gets fixed with it. My 
preference would be to bump the doxia dep in site-plugin to 1.1.2-SNAP, and push 
the number of MSITE issues down, fixing doxia bugs as we go along (finally we can 
use the site plugin to test doxia again... :) ). Some of the open issues have 
blocker status so I don't see the point of another site release before those are 
fixed. WDYT?

-Lukas


> 
>> Right now there are also a number of other issues scheduled that are not
>> related (eg MSITE-79, MSITE-206, MSITE-326) which I would like to leave
>> out and schedule for a later release.
> 
> +1 to leave those issues out.
> 
>>
>> Is this ok with everyone?
>> -Lukas
>>
>> ---------------------------------------------------------------------
>> 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: site plugin release planning

Posted by Dennis Lundberg <de...@apache.org>.
Lukas Theussl wrote:
> 
> Hi,
> 
> I was looking at the jira roadmap for the site plugin, thinking about a
> release plan for 2.1. The main change so far is the upgrade to doxia
> 1.1, I think it would be a good idea to concentrate the next release on
> issues that are related that. In particular, I'd like to fix all these
> annoying bugs with links (eg MSITE-395, MSITE-404, MSITE-409 and many
> others), which might necessitate another doxia release.

It's good to keep the releases small and focused. So +1 from me for a
special Doxia upgrade release.

+1 also for fixing the path issues you mentioned in the near future. My
findings on those issues are that the problem lies somewhere inside
Doxia, so I think another Doxia release will be necessary. If that is
the case, I think it is wise to do a release of the Site plugin with
Doxia 1.1.1 first.

> Right now there are also a number of other issues scheduled that are not
> related (eg MSITE-79, MSITE-206, MSITE-326) which I would like to leave
> out and schedule for a later release.

+1 to leave those issues out.

> 
> 
> Is this ok with everyone?
> -Lukas
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 


-- 
Dennis Lundberg

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


Re: site plugin release planning

Posted by Benjamin Bentmann <be...@udo.edu>.
Lukas Theussl wrote:

> Right now there are also a number of other issues scheduled that are not 
> related (eg MSITE-79, MSITE-206, MSITE-326) which I would like to leave 
> out and schedule for a later release.
> 
> Is this ok with everyone?

+1, I don't see the point in blocking a release or even just a 
particular version number just because of some issues that were 
scheduled long time back and that currently have no committer working on 
them.

Let's move forward, with whatever issue set we can fix.


Benjamin

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