harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stepan Mishura" <stepan.mish...@gmail.com>
Subject Re: [general] snapshots and a developers build
Date Wed, 07 Feb 2007 04:04:16 GMT
On 2/7/07, Mikhail Loenko <mloenko@gmail.com> wrote:
>
> Well if everything that is done nightly is completely automatic,
> then let's have them


Agree.

Stepan.

Thanks,
> Mikhail
>
> 2007/2/7, Geir Magnusson Jr. <geir@pobox.com>:
> > Oh - just to be really clear... :)
> >
> > I'm talking about a modification of what we do now into :
> >
> > 1) Automated daily snapshots - these are created once a day,
> > automatically, and automatically uploaded to somewhere.   I'm
> > guessing that unless we're clever, they are going to be
> > unsynchronized (different revs).  They are there simply for
> > convenience.   They aren't mirrored or have any human effort involved
> > (other than working out the details of how to get this to work from
> > around the community.)
> >
> > 2) Developer builds - these are what we have been doing, where we
> > carefully choose a svn revision number, create the builds from the
> > same rev, give it some basic testing and oversight, and vote for the
> > release.
> >
> > Does that help clear it up?  Sorry that I wasn't communicating
> > clearly...
> >
> > geir
> >
> >
> > On Feb 6, 2007, at 10:46 PM, Geir Magnusson Jr. wrote:
> >
> > >
> > > On Feb 6, 2007, at 10:38 PM, Mikhail Loenko wrote:
> > >
> > >> I'd support Stepan here. What IMHO makes sense is a weekly or a bi-
> > >> weekly
> > >> snapshots that runs all the CC scenarios fine. We could create
> > >> wiki pages for
> > >> each build so that people could try their apps (that not included
> > >> into CCs) and
> > >> report there.
> > >
> > > Yes, those would be the developers build.  Something that we look
> > > at and test.  Get them going on a regular schedule.
> > >
> > >>
> > >> So anyone who downloads the snapshot could have a feeling what the
> > >> snapshot can run
> > >>
> > >> I don't see any value in nightly snapshots that might be broken
> > >
> > > in my experience, nightlies are useful and harmless because they
> > > are automatically generated and posted, and just make it really
> > > simple for daily builds to be available.
> > >
> > > If it wasn't clear, I'm suggesting *both*.  There's no harm in
> > > having the nightlies, because they are labeled as such, with
> > > appropriate warnings, and if someone wants something "stable", they
> > > can get the weekly/bi-weekly developers build.
> > >
> > > If a snapshot is broken, it's broken.  That's ok.  People
> > > understand that.
> > >
> > > And it's good motivation to never let them get broken :)
> > >
> > > geir
> > >
> > >
> > >>
> > >> Thanks,
> > >> Mikhail
> > >>
> > >> 2007/2/6, Geir Magnusson Jr. <geir@pobox.com>:
> > >>>
> > >>> On Feb 6, 2007, at 10:27 AM, Stepan Mishura wrote:
> > >>>
> > >>> > On 2/6/07, Geir Magnusson Jr. wrote:
> > >>> >>
> > >>> >> This has been on my mind for the last couple of days, and
an note
> > >>> >> from Stepan reminded me to get this convo started.
> > >>> >>
> > >>> >> I'd like to start doing daily snapshots of Harmony from whatever
> > >>> >> platforms we happen to be building on.  These would be created
> > >>> every
> > >>> >> day.  They wouldn't require community review - we'd just get
> > >>> them up
> > >>> >> there, broken or not, and fix what needs to be fixed for the
next
> > >>> >> day.
> > >>> >
> > >>> >
> > >>> > I'm not sure about daily. I think we should work out mechanism
and
> > >>> > start
> > >>> > publishing them regularly (for example, weekly or in 2 weeks)
> > >>> > first. Then we
> > >>> > can reduce snapshot period if there such need. Also I don't see
> > >>> any
> > >>> > value in
> > >>> > a broken snapshot.
> > >>>
> > >>> They are snapshots.  We used to call them the "nightly build" in
> > >>> other projects.   The only point is to make it easy for people to
> > >>> use
> > >>> "the bleeding edge" w/o having to build.
> > >>>
> > >>> The thing we do every 2 weeks or so that is known good could be the
> > >>> "developer release".
> > >>>
> > >>> There is zero value in a broken snapshot (hence, please ensure that
> > >>> SVN isn't broken :).  But these are just an automated build, not
> > >>> something touched and judged by us humans.
> > >>>
> > >>> >
> > >>> > I'd like to get volunteers for this, and we can work out the
> > >>> >> mechanics. I'm not sure how much duplication we want for given
> > >>> >> operating systems.   I volunteer to do linux x86/x86_64 based
on
> > >>> >> ubuntu, and maybe we should also get a second set on RH or
> > >>> >> something.  Someone needs to also volunteer for windows.
> > >>> >
> > >>> >
> > >>> > I can do snapshots for SLES x86/x86_64 and Windows x86.
> > >>> >
> > >>> > Thanks,
> > >>> > Stepan.
> > >>> >
> > >>> > Secondly, we should think about doing periodic "developer builds",
> > >>> >> where we decide on a specific SVN revision, and do the builds,
> > >>> >> review, and vote for release.  These would be something we
> > >>> consider
> > >>> >> stable.
> > >>> >>
> > >>> >> geir
> >
>

-- 
Stepan Mishura
Intel Enterprise Solutions Software Division

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message