Re: JIRA "unification" proposal

[Kaj Kandler]

Thanks for the update Cedric,
I don't think that should be an open issue. I just saw this commit comment
http://mail-archives.apache.org/mod_mbox/cocoon-cvs/200809.mbox/%3c20080911163750.7a39f2388...@eris.apache.org%3E

Which refers to the Ajax block (and I use JX forms, that seem to
depend on that)

K
Chief Screencaster at http://plan-b-for-openoffice.org/ - a site
powered by Apache Cocoon 2.1.


On 2/28/12 4:10 AM, Cédric Damioli wrote:
> Hi,
> 
> Unfortunately I don't had enough time to do this in the past
> weeks. I'd also like to have a stable 2.1.12 release soon, but I
> must admit that I've never used Dojo-related features in Cocoon
> 2.1.x. BTW, I just take a look at open JIRA issues targeted for
> 2.1.12 and nothing seems to be related to Dojo
> 
> Regards, Cédric
> 
> Le 27/02/2012 22:16, Kaj Kandler a écrit : On 1/3/12 6:18 AM,
> Cédric Damioli wrote:

Re: JIRA "unification" proposal

[Cédric Damioli]

  
  
Hi,

Unfortunately I don't had enough time to do this in the past weeks.
I'd also like to have a stable 2.1.12 release soon, but I must admit
that I've never used Dojo-related features in Cocoon 2.1.x.
BTW, I just take a look at open JIRA issues targeted for 2.1.12 and
nothing seems to be related to Dojo

Regards,
Cédric

Le 27/02/2012 22:16, Kaj Kandler a écrit :

  -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 1/3/12 6:18 AM, Cédric Damioli wrote:

  
Hi,

I will actually work soon on 2.1 issues (at least those I've
opened). I also want to have a look to all existing 2.1 issues, to
measure the distance to an eventual 2.1.12 release in a near
future. So please don't close all 2.1 entries right now.

  
  Hi Cedric,
any update on this measurement? I saw some good things flowing into
2.1.12 in 2008, like Dojo being pulled from Google's script CDN. So
I'm eager to see a (stable) 2.1.12 come out three years later ;-)

K
Chief Screencaster at http://plan-b-for-libreoffie.org/ - a site
powered by Apache Cocoon.
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9L8psACgkQRDUvrJRNjTBHxgCghbS8Fyj9IrLB3GkyU3AqLNW4
LIUAn3K8RAcOVRikH9bvF31IrLcXMuIR
=jKj4
-END PGP SIGNATURE-



-- 
  
  

  
 
   www.anyware-services.com
  
 
Inscrivez-vous
  à notre newsletter
   

  

  
 
Cédric Damioli
   
Directeur technique
cedric.dami...@anyware-services.com
Tel : +33(0)5 62 19 19 07
Mob : +33(0)6 87 03 61 63
Fax : +33(0)5 61 75 84 12
Adresse : Innopole 13 - 254 avenue de l'Occitane
- B.P 97672 - 31676 LABEGE CEDEX - France 

Ametys: Smart Web CMS
 www.ametys.org
   
  

  

  

  
  
Ce message et toutes les pièces jointes (le "Message") sont
confidentiels et établis à l'intention exclusive de ses
destinataires.
Toute modification, édition, utilisation ou diffusion non
autorisée est interdite.
Anyware Services décline
toute responsabilité au titre de ce Message s'il a été altéré,
déformé, falsifié ou édité, diffusé sans autorisation.
  

  

Re: JIRA "unification" proposal

[Kaj Kandler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 1/3/12 6:18 AM, Cédric Damioli wrote:
> Hi,
> 
> I will actually work soon on 2.1 issues (at least those I've
> opened). I also want to have a look to all existing 2.1 issues, to
> measure the distance to an eventual 2.1.12 release in a near
> future. So please don't close all 2.1 entries right now.
Hi Cedric,
any update on this measurement? I saw some good things flowing into
2.1.12 in 2008, like Dojo being pulled from Google's script CDN. So
I'm eager to see a (stable) 2.1.12 come out three years later ;-)

K
Chief Screencaster at http://plan-b-for-libreoffie.org/ - a site
powered by Apache Cocoon.
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9L8psACgkQRDUvrJRNjTBHxgCghbS8Fyj9IrLB3GkyU3AqLNW4
LIUAn3K8RAcOVRikH9bvF31IrLcXMuIR
=jKj4
-END PGP SIGNATURE-

Re: JIRA "unification" proposal

[Jasha Joachimsthal]

2012/1/3 Francesco Chicchiriccò 

> On 03/01/2012 12:41, Simone Tripodi wrote:
> > Hi all,
> > and Happy New Year!!
> >
> >> ...but yeah IMO we need to have a apply-patches phase prior to the
> >> merge, to get the outstanding patches for 2.x closed and we have a
> >> cleaner list.
> > I am +1 on this, sounds like a more than reasonable plan!
>
> I am +1 for this as well, provided that this apply-patches phase is
> somehow time-constraint...
>

+1 for the time-constraint. Like I mentioned before we can always reopen
closed issues when they are being picked up later.


>
> Regards.
>
> --
> Francesco Chicchiriccò
>
> Apache Cocoon Committer and PMC Member
> http://people.apache.org/~ilgrosso/
>
>

Re: JIRA "unification" proposal

[Francesco Chicchiriccò]

On 03/01/2012 12:41, Simone Tripodi wrote:
> Hi all,
> and Happy New Year!!
>
>> ...but yeah IMO we need to have a apply-patches phase prior to the
>> merge, to get the outstanding patches for 2.x closed and we have a
>> cleaner list.
> I am +1 on this, sounds like a more than reasonable plan!

I am +1 for this as well, provided that this apply-patches phase is
somehow time-constraint...

Regards.

-- 
Francesco Chicchiriccò

Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/

Re: JIRA "unification" proposal

[Simone Tripodi]

Hi all,
and Happy New Year!!

> ...but yeah IMO we need to have a apply-patches phase prior to the
> merge, to get the outstanding patches for 2.x closed and we have a
> cleaner list.

I am +1 on this, sounds like a more than reasonable plan!
Thanks all, best,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/

Re: JIRA "unification" proposal

[Thorsten Scherler]

On Tue, 2012-01-03 at 11:59 +0100, Jasha Joachimsthal wrote:
> Merging those projects is good, but only if we clean up COCOON. There
> is a long list of issues with patches (there used to be a weekly mail
> with them) and an even longer list of unresolved issues. If we keep
> these issues open, it will be harder to see what we're working on and
> what we're dragging with us for years. IMO we can close the 2.1 and
> 2.2 issues that were created in 2010 or earlier with resolution "won't
> fix". They can always be reopened (or re-created) when someone is
> actually going to work on them.

Something like they do in the linux dist. Everything that did not get
attention for x month get "won't fix". I could life with that.

...but yeah IMO we need to have a apply-patches phase prior to the
merge, to get the outstanding patches for 2.x closed and we have a
cleaner list.

salu2
-- 
Thorsten Scherler 
codeBusters S.L. - web based systems

http://www.codebusters.es/

Re: JIRA "unification" proposal

[Francesco Chicchiriccò]

On 03/01/2012 12:18, Cédric Damioli wrote:
> Hi,
>
> I will actually work soon on 2.1 issues (at least those I've opened).
> I also want to have a look to all existing 2.1 issues, to measure the
> distance to an eventual 2.1.12 release in a near future. So please
> don't close all 2.1 entries right now.

Good.

> It is IMHO a good thing to merge the two JIRA projects, but we should
> take care to the various components spread accross different versions.
> Cocoon 2.1 blocks are for instance a non sense for Cocoon 3, as well
> as Cocoon 3 components does not mean anything for Cocoon 2.x
> We could maybe rename such components with a prefix indicating their
> version ?

This seems fine to me.
We could anyway ask INFRA people for JIRA best-practices in such cases.

Regards.

> Le 03/01/2012 11:59, Jasha Joachimsthal a écrit :
>> Merging those projects is good, but only if we clean up COCOON. There
>> is a long list of issues with patches (there used to be a weekly mail
>> with them) and an even longer list of unresolved issues. If we keep
>> these issues open, it will be harder to see what we're working on and
>> what we're dragging with us for years. IMO we can close the 2.1 and
>> 2.2 issues that were created in 2010 or earlier with resolution
>> "won't fix". They can always be reopened (or re-created) when someone
>> is actually going to work on them.
>>  
>> Jasha Joachimsthal
>>
>> 2012/1/3 Francesco Chicchiriccò > >
>>
>> Hi devs,
>> as you all know, you currently have two separate projects on
>> Apache JIRA, COCOON and COCOON3.
>>
>> Since there is currently a plan for restructuring the SVN tree
>> [1], what if we unify these two projects on JIRA as well?
>> AFAIK, this should involve:
>> 1. create new versions and components on COCOON
>> 2. move all tickets from COCOON3 to COCOON
>> 3. close COCOON3
>>
>> WDYT?
>>
>> Regards.
>>
>> [1]
>> 
>> http://old.nabble.com/Re%3A--C3--Import-subprojects-proposal--WAS%3A-Re%3A--c3--Log4j-injection-in-target-of-blocks--td32880500.html
>>
-- 
Francesco Chicchiriccò

Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/

Re: JIRA "unification" proposal

[Cédric Damioli]

  
  
Hi,

I will actually work soon on 2.1 issues (at least those I've
opened). I also want to have a look to all existing 2.1 issues, to
measure the distance to an eventual 2.1.12 release in a near future.
So please don't close all 2.1 entries right now.

It is IMHO a good thing to merge the two JIRA projects, but we
should take care to the various components spread accross different
versions. Cocoon 2.1 blocks are for instance a non sense for Cocoon
3, as well as Cocoon 3 components does not mean anything for Cocoon
2.x
We could maybe rename such components with a prefix indicating their
version ?

Cédric

Le 03/01/2012 11:59, Jasha Joachimsthal a écrit :
Merging those projects is good, but only if we clean
  up COCOON. There is a long list of issues with patches (there used
  to be a weekly mail with them) and an even longer list of
  unresolved issues. If we keep these issues open, it will be harder
  to see what we're working on and what we're dragging with us for
  years. IMO we can close the 2.1 and 2.2 issues that were created
  in 2010 or earlier with resolution "won't fix". They can always be
  reopened (or re-created) when someone is actually going to work on
  them.
  
 
Jasha Joachimsthal

Europe - Amsterdam -
Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466
US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414
4776 (toll free)

www.onehippo.com


2012/1/3 Francesco Chicchiriccò 
  
 Hi devs,
  as you all know, you currently have two separate projects
  on Apache JIRA, COCOON and COCOON3.
  
  Since there is currently a plan for restructuring the SVN
  tree [1], what if we unify these two projects on JIRA as
  well?
  AFAIK, this should involve:
  1. create new versions and components on COCOON
  2. move all tickets from COCOON3 to COCOON
  3. close COCOON3
  
  WDYT?
  
  Regards.
  
  [1] http://old.nabble.com/Re%3A--C3--Import-subprojects-proposal--WAS%3A-Re%3A--c3--Log4j-injection-in-target-of-blocks--td32880500.html
  
-- 
Francesco Chicchiriccò

Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/

  
  


  


-- 
  
  

  
 
   www.anyware-services.com
  
 
Inscrivez-vous
  à notre newsletter
   

  

  
 
Cédric Damioli
   
Directeur technique
cedric.dami...@anyware-services.com
Tel : +33(0)5 62 19 19 07
Mob : +33(0)6 87 03 61 63
Fax : +33(0)5 61 75 84 12
Adresse : Innopole 13 - 254 avenue de l'Occitane
- B.P 97672 - 31676 LABEGE CEDEX - France 

Ametys: Smart Web CMS
 www.ametys.org
   
  

  

  

  
  
Ce message et toutes les pièces jointes (le "Message") sont
confidentiels et établis à l'intention exclusive de ses
destinataires.
Toute modification, édition, utilisation ou diffusion non
autorisée est interdite.
Anyware Services décline
toute responsabilité au titre de ce Message s'il a été altéré,
déformé, falsifié ou édité, diffusé sans autorisation.
  

  

Re: JIRA "unification" proposal

[Jasha Joachimsthal]

Merging those projects is good, but only if we clean up COCOON. There is a
long list of issues with patches (there used to be a weekly mail with them)
and an even longer list of unresolved issues. If we keep these issues open,
it will be harder to see what we're working on and what we're dragging with
us for years. IMO we can close the 2.1 and 2.2 issues that were created in
2010 or earlier with resolution "won't fix". They can always be reopened
(or re-created) when someone is actually going to work on them.

Jasha Joachimsthal

Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466
US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll free)

www.onehippo.com


2012/1/3 Francesco Chicchiriccò 

>  Hi devs,
> as you all know, you currently have two separate projects on Apache JIRA,
> COCOON and COCOON3.
>
> Since there is currently a plan for restructuring the SVN tree [1], what
> if we unify these two projects on JIRA as well?
> AFAIK, this should involve:
> 1. create new versions and components on COCOON
> 2. move all tickets from COCOON3 to COCOON
> 3. close COCOON3
>
> WDYT?
>
> Regards.
>
> [1]
> http://old.nabble.com/Re%3A--C3--Import-subprojects-proposal--WAS%3A-Re%3A--c3--Log4j-injection-in-target-of-blocks--td32880500.html
>
> --
> Francesco Chicchiriccò
>
> Apache Cocoon Committer and PMC Memberhttp://people.apache.org/~ilgrosso/
>
>