On 6/25/07, Mikhail Loenko <[EMAIL PROTECTED]> wrote:
2007/6/25, Xiao-Feng Li <[EMAIL PROTECTED]>:
> On 6/25/07, Mikhail Loenko <[EMAIL PROTECTED]> wrote:
> > Let's create snapshots and then decide (based on testing results?)
> > what to release
>
> Why not to have them all? I don't understand. Sorry if I missed
It depends on testing results. For example, it does not make much sense
to release IPF build as a stable build (IIRC it currently runs apps
like "hello world"
only)
If we have excellent testing results on the first platform and pretty
modest ones on
the second one (or no testing for the second platform) I'd prefer to
release only the first one.
I agree with the criteria, well I think we are talking about
Linux-X86/Win-X86/Win-X86-64 per Stepan's question, and these three
configurations are rather stable (?) in my understanding. I wish I am
right since that's what the feature/code freezes were/are intended
for. Otherwise, we might want to reexamine the M-series release
process.
Thanks,
xiaofeng
Thanks,
Mikhail
> anything, but I think it's always good to have the choices available,
> otherwise the users who want to try will build them anyway.
>
> Thanks,
> xiaofeng
>
> > Thanks,
> > Mikhail
> >
> > 2007/6/25, Stepan Mishura <[EMAIL PROTECTED]>:
> > > On 6/24/07, Mikhail Loenko <[EMAIL PROTECTED]> wrote:
> > > > We have passed our code freeze date for M2
> > > >
> > >
> > > Mikhail,
> > >
> > > Just to be clear - M1 milestone published snapshots include build for
> > > Windows x86, Linux (libstdc++ v5 and libstdc++ v6) x86 and Windows
> > > x86_64.
> > >
> > > I assume that we still aimed to x86 architecture and I need to build
> > > milestone candidates for:
> > > - Windows x86
> > > - Linux x86. BWT, again for both libstdc++ versions?
> > >
> > > And what about x86_64?
> > >
> > > As I said M1 includes Windows x86_64. Should we publish them to let
> > > the community test them to see how good they are?
> > >
> > > Thanks,
> > > Stepan.
> > >
> > > > Last time we executed Tim's policy that each commit should have
> > > > approval from two committers, let's follow the same way -- no more
> > > > commits please, without agreement from two committers on the dev list.
> > > >
> > > > Now let's test what we have and see if any critical bugs were
> > > > introduced just before the code freeze. Please raise anything you
> > > > think is critical/blocker for consideration.
> > > >
> > > > Thanks,
> > > > Mikhail
> > > >
> > >
> > >
> > > --
> > > Stepan Mishura
> > > Intel Enterprise Solutions Software Division
> > >
> >
>
>
> --
> http://xiao-feng.blogspot.com
>
--
http://xiao-feng.blogspot.com
