DNF as default package manager

[Jan Zeleny]

Dne Čt 22. ledna 2015 14:54:47, Adam Williamson napsal(a):
> On Wed, 2015-01-21 at 13:40 +0100, Jan Zelený wrote:
> > On 21. 1. 2015 at 11:07:31, Peter Robinson wrote:
> > > > > > 1) DNF will be the default package manager for F22 [2], so
> > > > > > everything is
> > > > > > ok here.
> > > > > 
> > > > > I really wonder what is the state here. This is on my rawhide:
> > > > We strongly believe all the major problems will be resolved in
> > > > time. Also,
> > > > as of last week we have one person dedicated to helping people
> > > > with porting their application and the rest of the developers
> > > > focus mainly on major usability issues.
> > > > 
> > > > But still, I would appreciate more cooperation from the Fedora
> > > > community.
> > > > Most of the package maintainers don't seem to care about this
> > > > transition.
> > > > They didn't respond to the bugs that are filed against their
> > > > components, not even to direct emails we sent them offering help
> > > > with the transition.
> > > 
> > > All features are due to be complete in a month [1] but earlier in
> > > the thread it was said that some of the functionality isn't even
> > > written yet.....
> > > 
> > > [1] https://fedoraproject.org/wiki/Releases/22/Schedule
> > 
> > What date are you referring to? Is it "Change Checkpoint: Completion
> > deadline
> > (testable)"? If yes then I don't see any problems. DNF has been
> > testable for
> > quite some time and I invite people to test it.
> 
> The checkpoints have precise definitions, the links are just
> summaries. From https://fedoraproject.org/wiki/Changes/Policy , "What
> are the change process deadline dates (Checkpoints)?":
> 
> Change Checkpoint: Completion deadline
> 
> This deadline falls on the same day as the Alpha milestone freeze (see
> Schedule).
> 
>    * New changes must be feature complete or close enough to
> completion by the Change Checkpoint: Completion deadline date that a
> majority of its functionality can be tested during the Alpha and Beta
> releases.
>    * If a change proposal page specifies a change will be enabled by
> default, it must be so by this date.
>    * Changes meeting the preceding bullets are considered testable.
>    * Use the MODIFIED status in the tracker bug to show the change
> made the change deadline and is testable.
> 
> "Testable"
> 
> This means the change is substantially complete and can be tested when
> the change is not 100% completely implemented. This is an attempt to
> provide some flexibility without completely losing the understood
> meaning of a change being feature complete. All new changes are tested
> during the Alpha and Beta releases.


Thank you for the link Adam,
in that case we will focus all our effort into implementing whatever remains to 
be implemented by that date.

Jan