airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lahiru Gunathilake <glah...@gmail.com>
Subject Re: Frequent release builds
Date Mon, 25 Mar 2013 18:12:50 GMT
On Mon, Mar 25, 2013 at 2:08 PM, Suresh Marru <smarru@apache.org> wrote:

> On Mar 25, 2013, at 2:02 PM, Lahiru Gunathilake <glahiru@gmail.com> wrote:
>
> > Sounds good.. will do ! I thought we need to do version changes etc..
>
> Ideally yes, a version number and a tag to refer to refer to each RC. But
> I think since we are doing a very early RC for testing, we can probably
> live without them. Unless some one has an objection, I would suggest you to
> assume lazy consensus here.
>
Noted.

Lahiru

>
> Suresh
>
> >
> > I'll do the RC1 then.
> >
> > Lahiru
> >
> > On Mon, Mar 25, 2013 at 1:42 PM, Suresh Marru <smarru@apache.org> wrote:
> >
> >> On Mar 25, 2013, at 1:37 PM, Lahiru Gunathilake <glahiru@gmail.com>
> wrote:
> >>
> >>> Hi Chris,
> >>>
> >>> Thanks for pointing this out. Our Jenkin build is failing continuously,
> >> but
> >>> locally build works fine. We need to fix Jenkin build, but I thought we
> >>> should start the release work.
> >>>
> >>> First I'd like to be the release manager for 0.7 release, and next
> build
> >> I
> >>> do not want it a RC, I'd just like to do a build and then ask people to
> >>> testing, after that I'd like to start proper RC1 (hopefully release
> RC1).
> >>
> >> Hi Lahiru,
> >>
> >> Thank you for volunteering to be the release manager, I will be happy
> >> assist if you need any help. Why don't you call it a RC1 anyway? the RC
> >> number might increase with lot of iterations, but atleast you will get
> some
> >> testing done on the potential release right?
> >>
> >> You don't need to change anything, just create a 0.7/RC1 directory
> within
> >> svn dist dev location and the follow the rest of process as you are
> doing.
> >> Also adding a [DISCUSS] prefix to email might and saying 0.7 RC1 might
> help.
> >>
> >> Thanks,
> >> Suresh
> >>
> >>
> >>> Regards
> >>> Lahiru
> >>>
> >>>
> >>> On Fri, Mar 22, 2013 at 4:44 PM, Mattmann, Chris A (388J) <
> >>> chris.a.mattmann@jpl.nasa.gov> wrote:
> >>>
> >>>> Hi Lahiru,
> >>>>
> >>>> First off, great job trying to push this forward!
> >>>>
> >>>> However, I am going to have to ask you to remove those build artifacts
> >>>> from your personal people.a.o account.
> >>>>
> >>>> There are several reasons for this:
> >>>>
> >>>> 1. It doesn't seem like you are calling for a release VOTE or the RM
> >> here,
> >>>> and as such we can't confuse people that these are Apache Airavata
> >>>> sanctioned
> >>>> RCs (in process by an RM and according to:
> >>>>
> >>>> http://www.apache.org/dev/release.html#host-rc
> >>>>
> >>>>
> >>>>
> >>>> 2. There are other ways to have release snapshots, one of which is to
> >>>> make Jenkins produce such artifacts for you and publish to
> >>>> https://repository.apache.org/
> >>>>
> >>>> HTH and if you have questions let me know. Sorry, just trying to help
> >> here.
> >>>>
> >>>> Cheers,
> >>>> Chris
> >>>>
> >>>>
> >>>> On 3/22/13 9:18 AM, "Lahiru Gunathilake" <glahiru@gmail.com> wrote:
> >>>>
> >>>>> Hi Devs,
> >>>>>
> >>>>> I am going to start release builds, so that people can test. As
we
> are
> >> not
> >>>>> going with new features, we can keep on testing. But please feel
free
> >> to
> >>>>> send an email to the dev list if there's a very urgent feature
> someone
> >>>>> wants to add to 0.7 release. Please find the release packs here[1].
> >>>>>
> >>>>> If you can reply to the thread what are you doing to test (which
> pack,
> >>>>> what
> >>>>> functionalities) it would be easy for us to do fast test cycle.
So
> they
> >>>>> can
> >>>>> keep doing the same test for each build.
> >>>>>
> >>>>> I came up with few abstract test check list.
> >>>>>
> >>>>> 1. Test XBaya GUI functionality - including registry operations
etc.
> >>>>> 2. Test Airavata server backend with gram jobs and a currently
> >> production
> >>>>> workflows - Lahiru
> >>>>> 3. Do the step 2 on tomcat deployment - Lahiru
> >>>>> 4. Test Airavata API with basic functionality.
> >>>>> 5. Changing backend configurations and see they all works
> >>>>> (gfac-config,airavata-server.properties).
> >>>>>
> >>>>> If you can come up with more test list that would be great. Please
> >> report
> >>>>> all the issues in Jira and fixed version as 0.7.
> >>>>>
> >>>>> [1]http://people.apache.org/~lahiru/airavata/0.7/
> >>>>>
> >>>>> Regards
> >>>>> Lahiru
> >>>>>
> >>>>> --
> >>>>> System Analyst Programmer
> >>>>> PTI Lab
> >>>>> Indiana University
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> System Analyst Programmer
> >>> PTI Lab
> >>> Indiana University
> >>
> >>
> >
> >
> > --
> > System Analyst Programmer
> > PTI Lab
> > Indiana University
>
>


-- 
System Analyst Programmer
PTI Lab
Indiana University

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