Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Pig >> mail # dev >> Pig 0.11


Alan,

Are there any blog posts or whatnot explaining the logic behind this?

Just curious
Jon

2012/10/25 Alan Gates <[EMAIL PROTECTED]>

> There's one other issue I believe we should resolve before we release
> 0.11.  As part of my work with the Incubator I've learned that official
> Apache releases aren't supposed to have any binary code (including any
> jars) in them.  Due to some recent issues with projects in the incubator
> this has become a hot topic and some Apache members/officers have become
> keen on making sure projects are in compliance.  Obviously Pig has been in
> violation of this for a while now (oops).  We are still free to provide
> "convenience packages" that contain the binaries, but they cannot be what
> we vote on or what we sign and release.
>
> What this practically means for us is we need a new ant target that just
> tars up the source and we need to change the release procedures slightly to
> sign and checksum the resulting tarball.  We would then post both the
> source release and the "convenience package" which would be the same
> release we have always done.
>
> All the changes for this can be done in build.xml and the build procedures
> wiki and are thus quite low risk.  I volunteer to do it.  I believe we
> should do this for this release to avoid any issues with Apache.
>
> Alan.
>
> On Oct 22, 2012, at 1:14 PM, Olga Natkovich wrote:
>
> > There are still 76 unresolved JIRAs more than half unassigned. Lets
> clean this up by theend of this week. I propose we do the following:
> >
> > (1) Unlink all JIRAs for new features since we already branched so we
> should not be taken on new work. If people feel strongly that some new
> features still need to go in please bring it up.
> > (2) For bug fixes, if people fill strongly that some of the unassigned
> issues need to be addressed please take ownership. If you are unable to
> solve them but still feel they are important, please, bring them up.
> > (3) Owners of unresolved issues, please, take a look if you will have
> time to solve them in the next 2 weeks. If not, lets move them to 12. If
> you can't address them but feel they are important, please, bring it up.
> >
> > Lets make sure that all JIRAs that require changes to the documentation
> have appropriate information in the release notes section so that we can
> quickly compile release documentation.
> >
> > Thanks for you help!
> >
> > Olga
> >
> >
> >
> >
> > ________________________________
> > From: Alan Gates <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Sent: Monday, October 15, 2012 11:55 AM
> > Subject: Re: Pig 0.11
> >
> > At this point no one has taken on release documentation for 0.11.
> >
> > Alan.
> >
> > On Oct 15, 2012, at 11:49 AM, Olga Natkovich wrote:
> >
> >> Thanks!
> >>
> >> Are you talking about items 15 and 16 on the How To Release.Publish
>  page?
> >>
> >> Also, who is doing release documentation these days? I can help with
> that as well. I would also be happy to roll the release if you guys need
> help with that.
> >>
> >> Olga
> >>
> >>
> >> ________________________________
> >> From: Dmitriy Ryaboy <[EMAIL PROTECTED]>
> >> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> >> Cc: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> >> Sent: Friday, October 12, 2012 5:59 PM
> >> Subject: Re: Pig 0.11
> >>
> >> Thanks Olga and welcome back!
> >> I know there's some process for linking jiras to releases, but I'm not
> sure what that is. If you could explain and maybe cover a portion of that
> work, that'd be super helpful. And reviews, of course.
> >>
> >> On Oct 12, 2012, at 2:06 PM, Olga Natkovich <[EMAIL PROTECTED]>
> wrote:
> >>
> >>> Dmitry, I would be happy to help with the release process. Want to get
> back into this now that I am back at work. Let me know what you would like
> me to do.
> >>>
> >>> Olga
> >>>
> >>>
> >>>
> >>> ________________________________
> >>> From: Dmitriy Ryaboy <[EMAIL PROTECTED]>
> >>> To: [EMAIL PROTECTED]
> >>> Cc: [EMAIL PROTECTED]