Front page | perl.perl5.porters |
Postings from March 2014
From: Nicholas Clark
March 25, 2014 09:44
Message ID: 20140325094439.GH22619@plum.flirble.org
On Sun, Mar 23, 2014 at 09:31:27PM -0400, Ricardo Signes wrote:
> I'd hoped to send this email much earlier, along with a new review of blockers,
> but my weekend has been sort of unrelenting.
> As foretold by Porting/release_schedule.pod, blead is now frozen for 5.20.0,
> expected in about two months. The freeze means that the only things getting
> committed should be:
> * fixes for blockers
> * fixes for problems that would become blockers if not immediately fixed
> * uncontroversial documentation improvements
Do you consider changing comments in the C code as documentation?
(Note, comments. Not strings. Not things change the compiled binary, let
alone strings that the user sees)
On Mon, Mar 24, 2014 at 10:17:47AM -0400, Ricardo Signes wrote:
> * "H.Merijn Brand" <firstname.lastname@example.org> [2014-03-24T02:50:19]
> > Will two OK's on IRC from other committers be enough, or will every
> > patch to the main branch need a ML post?
> Sure, as long as everyone is keeping in mind that the goal right now is only to
> fix blockers, not to change any other behavior. "Hey, I can save some memory
> by doing X" can go into a branch for 5.21.1.
> > I just read Nicholas' quest for the use of ccflags in Configure when
> > checking for libraries. Does that qualify for fast(er) action?
> No, better the problems we know than the ones we don't. Fix in 5.21.
Yes, agree. This one is old, not urgent, and likely to be tricky to get
right first time. (ie I forsee that we're going to end up iterating the
fix to get the bugs out. We're not going to get it totally right first