[CFT] Call for testing pkg 1.5.0

[Baptiste Daroussin]

On Mon, Apr 13, 2015 at 04:05:09PM -0400, Adam McDougall wrote:
> On 04/03/2015 11:13, Baptiste Daroussin wrote:
> > On Fri, Apr 03, 2015 at 11:07:19AM -0400, Adam McDougall wrote:
> >> On 03/31/2015 15:03, Baptiste Daroussin wrote:
> >>> Hi all,
> >>>
> >>> We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel),
> >>>
> >>> Please test and report as much bugs as you can!
> >>> We could be very grateful if regressions tests could be provided along with the
> >>> bug reports :)
> >>>
> >>> Plan is to release 1.5.0 as soon as possible
> >>>
> >>> Best regards,
> >>> Bapt
> >>>
> >>
> >> When the rapid cycle of bugreport-> fix slows down in the RC stage,
> >> could you give a heads up and ETA before final release (2-3 weeks?)
> >> I will probably be out of town for this release but my inclinations to
> >> test are rising.  In the past, the final release came very quickly after
> >> a number of reported bugs were fixed.  Fortunately 1.4.0 was good.  I
> >> feel the late RC stage needs a short announced period of a week or more
> >> to let risk-averse testers know that it is worthwhile to start testing
> >> without concern of almost daily fixes.  Thanks.
> >>
> > 
> > My hope is 2 weeks we have added lots of regressions tests (which is still not
> > enough) so I'm a little bit more confident than I use to be.
> > 
> > Of course I will delay the release if the amount of bugs reported is too
> > important.
> > 
> > I suspect more people will test during the Week End to depending on the feedback
> > of this week end I may release the RC1 on monday/tuesday and then depending on
> > the feedback of the next week a final release could happen on next wednesday
> > (14th.).
> > 
> > Best regards,
> > Bapt
> > 
> 
> I have been testing 1.4.99.19 and 1.4.99.20 over the weekend on a couple
> desktop installs and so far it works fine.  I think I noticed a new
> behavior, it seems to print multiple warnings when a dependency library
> is locked (for testing).  I think pkg 1.4.12 only prints it once.  If
> multiple are intentional, could it print the name of the package causing
> it?  It does not seem to prevent upgrade of any leaf packages which
> seems improper.  I went ahead with the upgrade, verified 'pkg upgrade'
> reports nothing, unlocked gtk3, then it offered to upgrade just gtk3.  I
> don't know if it would be different if a shlib version changed.  I can
> redo this test and/or provide more data but I only have today and
> tomorrow.  Thanks.
> 
Yes it is planned to bring more informations to users, but that would be too
intrusive changes internally to get added to pkg 1.5 at this time before the
release.

I hope to bring that for 1.6

Best regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-pkg/attachments/20150414/d1078ec7/attachment.sig>