hi, On Mon, Oct 25, 2010 at 6:20 AM, Andreas Pieber <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?
Assign those issues to a future release or even remove the fix version for now as we do not know when will be solved. > > Another question to all: Is there anything opened you really want to get into > the 0.8er release? Not me. > > 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? We were thinking about an some years ago that just releases over 1.0 to be in central. I do not know if that is relevant. From my side those should be in central as soon as they mature. But then maybe those should be 1.0 so teh rule does not change. > *) 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? Is not about the vote. If you use staging you can in case of an release problem to drop the stage repository. Otherwise, in case of a problem you could be releasing only some modules form project. > *) 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? You will have to create an issue with oss project and ask for rights to do release management for ops4j projects. > > kind regards, > andreas > > [1] > http://issues.ops4j.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10110&fixfor=10376 > [2] http://wiki.ops4j.org/display/ops4j/Releasing > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > -- Alin Dreghiciu Software Developer My profile: http://www.linkedin.com/in/alindreghiciu My blog: http://adreghiciu.wordpress.com http://sonatype.com - Sonatype - The Maven Company http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
