I'm doing it right now, so if there's no objection to release pax-url, I can cut a release today or tomorrow.
On Mon, Oct 25, 2010 at 09:38, Andreas Pieber <anpie...@gmail.com> wrote: > When do you like to implement the changes? I mean, after I've pushed the > snapshots I can wait, but nevertheless I prefere minor frequent releases > above > huge and rare ones. I've no problem cutting another release (pax-web-0.8.1) > in > two or three weeks... > > kind regards > > On Mon, Oct 25, 2010 at 08:15:55AM +0200, Guillaume Nodet wrote: > > On Mon, Oct 25, 2010 at 05:20, Andreas Pieber <[1]anpie...@gmail.com> > > wrote: > > > > hey, > > Its been a while since the last pax-web release and I think with the > > upgrade to > > jetty 7 it's time to do it again :) Nevertheless, it's my first > > release of a pax > > project so I share my ideas with you; feel free to correct me :) > > I've scanned the pax-web JIRA project for opened issues assigend to > > 0.8.0 [1]. > > There are 4 issues assigned for this release (opened for about a > > year now...). > > How should I proceed with them (I can't fix them in time and IMHO > > they're not > > critical for this release...). Should I assign them to 0.9.0 or > > simply to no > > direct milestone? > > Another question to all: Is there anything opened you really want to > > get into > > the 0.8er release? > > > > Yes, but indirectly. > > I'd like to enhance pax-url war url handler to have a simple way to > > optional import the pax-logging exported packages, so that the logging > > in those apps would work by default when deployed with pax-logging > > already deployed. > > Those imports would be optional and use the provider=paxlogging > > attribute to ensure they're actaully wired to pax-logging. > > I'm not sure if this should be a default or based on a > > system/bundlecontext property yet. > > The reason i'm talking about that is that the features file contain a > > reference to pax-url, so i'd like to have it released before that. > > > > Some questions: > > [2] Describes the release process of ops4j proejcts. The following > > point's I'm > > not sure about: > > *) [2] makes difference between releases <1.0 and >=1.0 Is this > > really of > > relevance? IMHO all artifacts should be located at mvn central, > > shouldn't they? > > *) A profile with staging and a profile with non-staging exists. > > What is the > > typical process at opsj: simply release (non-staging) and add new > > releases as > > problems with the current build occur or (staging) releases with a > > vote? > > *) access sonatype repos. I have a sonatype account already (pieber) > > for other > > projects, but I'm not sure if it does work for ops4j? Do you need to > > add me to > > some list to access the staging/release repos? > > kind regards, > > andreas > > [1] > > [2] > http://issues.ops4j.org/secure/IssueNavigator.jspa?reset=true&mod > > e=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=101 > > 10&fixfor=10376 > > [2] [3]http://wiki.ops4j.org/display/ops4j/Releasing > > _______________________________________________ > > general mailing list > > [4]gene...@lists.ops4j.org > > [5]http://lists.ops4j.org/mailman/listinfo/general > > > > -- > > Cheers, > > Guillaume Nodet > > ------------------------ > > Blog: [6]http://gnodet.blogspot.com/ > > ------------------------ > > Open Source SOA > > [7]http://fusesource.com > > > > References > > > > 1. mailto:anpie...@gmail.com > > 2. > http://issues.ops4j.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10110&fixfor=10376 > > 3. http://wiki.ops4j.org/display/ops4j/Releasing > > 4. mailto:general@lists.ops4j.org > > 5. http://lists.ops4j.org/mailman/listinfo/general > > 6. http://gnodet.blogspot.com/ > > 7. http://fusesource.com/ > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
