Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [emft-dev] Re: [modeling-pmc] EMFT "Project" Compare 0.7.0 release without a Release Review?


The rules for components are certainly not well established.  Generally a
whole project releases at once and hence it would be a project review that
includes all components.   In fact, a lot of times a whole top level
project will release at once so includes all subprojects as well as their
constituent components.  Since much of this comes down to terminology, some
folks take the approach of producing a "final" build rather than a
"release" build.  There's also a such thing as a continuation review,
according to the rules I've read, but I've never seen one of those happen.
(I know Bjorn doesn't like unenforced rules because the weaken other
rules.)  It would be simpler for you just to produce a final build and then
wait to do a release review of your subsequent stream as part of the
overall Ganymede release cycle next year...

Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265  (t/l 969)

             Cédric Brun                                             
             .fr>                                                       To
             09/27/2007 11:43                                           cc
             AM                        Ed Merks/Toronto/IBM@IBMCA, PMC 
                                       members mailing list            
                                       Re: [emft-dev] Re: [modeling-pmc]
                                       EMFT "Project" Compare 0.7.0    
                                       release without a     Release   

The 0.7.0 release has been removed and I'm starting the docuware for the
I'll ask for the review soon. Though I still feel unsure about the process
incubation projects.
Lately I've seen other component releases implying many plugins, and I
find the corresponding release review.
I don't deny the need of this reviews and the fact that it helps in
the community, I don't want to start a pointless debate about this or that
component/project  but I would just like to clearly understand the rules
telling if yes, or no, a component should ask for a review.



Le Wednesday 12 September 2007 21:16:18 Ed Merks, vous avez écrit :
> Bjorn,
> I'll ask Cedric to rename it as a release candidate and to schedule a
> *component* release review before declaring a release publicly like this.
> Please take note other component leads!
> And I'll ask Nick to looking into using ?component= instead of ?project=
> avoid potential confusion (because goodness knows things are confusing
> enough already).
> Ed Merks/Toronto/IBM@IBMCA
> mailto: merks@xxxxxxxxxx
> 905-413-3265  (t/l 969)
>              Bjorn
>              Freeman-Benson
>              <bjorn.freeman-be
>              nson@xxxxxxxxxxx>         modeling-pmc@xxxxxxxxxxx,
>              Sent by:                  emft-dev@xxxxxxxxxxx
>              modeling-pmc-boun
>              ces@xxxxxxxxxxx           emo@xxxxxxxxxxx, "'Janet
>                                        <janet.campbell@xxxxxxxxxxx>
>              09/12/2007 02:40          [modeling-pmc] EMFT "Project"
>              PM                        Compare 0.7.0 release without a
>                                        Release Review?
>              Please respond to
>                 PMC members
>                mailing list
>              <modeling-pmc@ecl
>        >
> Dear Modeling PMC and EMFT Developers,
> Why is it that the EMFT Compare component has released a 0.7.0 release
> without an official Release Review?
> All projects must have Release Reviews for M.N releases, including 0.N
> releases. The Release Reviews are important for a number of reasons.
> Please explain how the EMFT project did not have a Release Review.
> - Bjorn
> P.S. And why does it say "?project=" on that URL when it's a component,
> a project?
> --
>  Bjorn
>  Freeman-Ben
>  son
>  Director,
>  Open Source
>  Process
>  Eclipse
>  Foundation
>       voice: 971-327-7323 (Pacific Time)
>       email: bjorn.freeman-benson@xxxxxxxxxxx
> _______________________________________________
> modeling-pmc mailing list
> modeling-pmc@xxxxxxxxxxx
> _______________________________________________
> emft-dev mailing list
> emft-dev@xxxxxxxxxxx

Back to the top