harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ray Chen <clrayc...@gmail.com>
Subject Re: Next milestones: 5.0M16 and 6.0M4
Date Wed, 08 Dec 2010 01:55:32 GMT
OK.
Code Freeze 10th December
Publish 17th December

On Tue, Dec 7, 2010 at 6:48 PM, Tim Ellison <t.p.ellison@gmail.com> wrote:

> On 06/Dec/2010 15:31, Ray Chen wrote:
> > Sure,  I propose the following dates:
> >
> >  Feature Freeze  Wed 15th December
> >  Code Freeze     Wed 22nd December
> >  Publish         Wed 29th December
>
> Unless somebody shouts, I don't think we need to adopt a length feature
> freeze.  I don't see any major work in flight at the moment.  So how
> about code freeze sooner (say Dec 10th) and publish the net milestone a
> week later (Dec 17th)?
>
> > Please help to run the tests.
> >
> > Tim,
> > I found Kevin has attached a patch for
> > https://issues.apache.org/jira/browse/HARMONY-6419,  would you please
> help
> > to review it?
>
> Sure.  If others want to review it too that is fine ;-)
>
> Regards,
> Tim
>
> > Let's make new milstones for the coming New Year!  :)
> >
> > On Mon, Dec 6, 2010 at 6:22 PM, Tim Ellison <t.p.ellison@gmail.com>
> wrote:
> >
> >> On 30/Nov/2010 13:55, Ray Chen wrote:
> >>> Hmmm... Ok, I think it will take some time to understand these for some
> >> time.
> >>> Maybe we should put this milestone off for serveral days before I
> >>> understand all the process.
> >>
> >> Hi Ray,
> >>
> >> Thanks for volunteering to do some RM.  I can also help with the
> process.
> >>
> >> How about we set a new proposed date for the next milestone, and work
> >> towards that?  Encouraging people to report test results and getting the
> >> list of JIRA must fixes sorted would be the first step.
> >>
> >> Regards,
> >> Tim
> >>
> >>
> >>> On Tue, Nov 30, 2010 at 5:38 PM, Mark Hindess
> >>> <mark.hindess@googlemail.com> wrote:
> >>>>
> >>>> In message <
> >> AANLkTimb6FfNVpGmSTYcKLXMnM5ZNmMEkSxJOPXS62di@mail.gmail.com>,
> >>>> Ray Chen writes:
> >>>>>
> >>>>> Hi Mark,
> >>>>> Does release manager must be a PMC?
> >>>>
> >>>> No.  See:
> >>>>
> >>>>  http://www.apache.org/dev/release-publishing.html#release_manager
> >>>>
> >>>>> If not, maybe I can take the responsibility.
> >>>>
> >>>> That would be great.
> >>>>
> >>>>> However, I don't know much about how to do it, I think we need some
> >>>>> transferring work.
> >>>>
> >>>> Ask here if you have questions.  My activity as release manager for
> >>>> previous releases was something like ...
> >>>>
> >>>> Suggest dates, announce freezes, encourage people to do testing and
> >>>> move things along a bit when people send test results, work to resolve
> >>>> release critical issues, produce signed source artifacts, start a
> vote,
> >>>> conclude the vote and produce signed binaries.
> >>>>
> >>>> The scripts I use to create linux source and binary artifacts are in
> svn
> >>>> at:
> >>>>
> >>>>  https://svn.apache.org/repos/asf/harmony/standard/tools/release
> >>>>
> >>>> I do the equivalent manual process for both windows platforms.
> >>>>
> >>>> The last crucial part is populating the /dist/ tree for mirroring.
> >>>> You need to be careful doing this so as to avoid messing up lots of
> >>>> mirrors.  I tend to make the tree elsewhere then check that it matches
> >>>> the size/shape of the previous release tree before using rsync to put
> >>>> it in to /dist/.
> >>>>
> >>>> Just ask if you have question about any of the process.
> >>>>
> >>>> Regards,
> >>>>  Mark.
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>
> >
> >
> >
>



-- 
Regards,

Ray Chen

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