From: "V.Krishn" <vkrishn4@gmail.com>
Reply-To: vkrishn4@gmail.com
To: Leonardo Arena <rnalrd@gmail.com>
Subject: Re: [alpine-devel] v3.3 feature freeze
Date: Thu, 29 Oct 2015 13:11:01 +0530
User-Agent: KMail/1.13.7 (Linux/3.9.6-64; KDE/4.8.4; x86_64; ; )
References: <20151022180104.1feeb73a@ncopa-laptop> <20151026101227.2e9e3058@ncopa-desktop.alpinelinux.org> <1445872834.3455.43.camel@df1844j>
In-Reply-To: <1445872834.3455.43.camel@df1844j>
Cc: alpine-devel@lists.alpinelinux.org
Precedence: list
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-Id: <201510291311.01965.vkrishn4@gmail.com>

> On lun, 2015-10-26 at 10:12 +0100, Natanael Copa wrote:
> > On Fri, 23 Oct 2015 03:04:36 +0530
> > 
> > "V.Krishn" <vkrishn4@gmail.com> wrote:
> > > > Hi,
> > > > 
> > > > We now need to stop working on new features for the v3.3 release and
> > > > concentrate on wrapping things up for v3.3 release. Testing and
> > > > fixing bugs.
> > > > 
> > > > A few questions:
> > > > 
> > > > Can we make the 'lua' package be lua5.3? I think everything that
> > > > needs 5.1 should have depends on 'lua5.1' instead of 'lua'.
> > > > 
> > > > Can anyone help with upgrading llvm-3.7 and clang?
> > > > 
> > > > Can anyone help with upgrade xen to 4.6?
> > > > 
> > > > I'd like to move as much ruby stuff as possible to community, can
> > > > someone help with that?
> > > > 
> > > > Are there anything else that needs cleanup for v3.3?
> > > 
> > > Any thoughts on:
> > > 1. All desktops except one that we want to keep as default and ready to
> > > jump on it to fix when update available or broken.
> > 
> > You mean move to community?
> > 
> > I'm all for moving as much as possible to community.
> > 
> > The question was more general, what more cleanup, more than just move
> > stuff to community, are *needed* before v3.3. Eg the critical stuff,
> > the things we can not forget.
> > 
> > > 2. Web application like drupal, phpmyadmin, owncloud i.e pkgs that does
> > > not require compiling and are sometimes more easier to install by
> > > downloading the orig tar and just uncompressing in web-folders.
> > 
> > What about those packages?
> 
> I think we should move to community the packages which don't have stable
> and maintained releases. This is not the case of ownCloud since is
> maintained for 1,5 years after release. For example v6.0.0 was released
> in Dec. 2013 and last update was 6.0.9 on July 2016. v7.0.0 was released
> July 2014 it's still actively maintained.
> 
> I think it's handy to have web applications packages for run-from-RAM
> installations. Also upgrade of packaged web application is faster then
> tar-based installations.
> 
> Not sure about drupal maintenance policy, and may be phpmyadmin can be
> likely moved.

Criteria is not upstream stability release but,
1. Does these pkgs' normal updates get backported ?
2. If we decide fitting main is one CD or two do we want them in main then ?
3. Pkgs like these are easy to maintain and maybe tagged/delegated to new or 
less experienced maintainers.
4. Note, there is no stopping for main devs in maintaining community pkgs.

> 
> > > More pkgs can be picked based on definition and difference
> > > 
> > >  in community and main (please expand)
> > > 
> > > 1. main requires 2yrs maintenance skill commitment.
> > > 2. main has higher priority when comes to pushing update/broken pkgs in
> > > next releases , right ?
> > 
> > Something like that yes.
> > 
> > > Based on 2 above, I can spot (debatable though),
> > > 
> > >  zabbix, nagios, wayland
> > 
> > I think we want atleast zabbix and nagios to stay in main.
> 
> +1
> 
> > Wayland can probably move to community, unless there is something that
> > depends on it that we want/need keep in main.
> > 
> > Would be great if the feedback would not include any kind of research
> > from my part (eg wayland is in the dependency chain of what packages?)
> > 
> > > This can also help in creating various isos, like
> > > 1. alpine-boot (bootable+live+AL preferred net tools/utils)
> > > 
> > >     media that gets you started with bare alpine install
> > >     (quite same as current alpine-mini)
> > > 
> > > 2. alpine-cd (same above + main) - non-desktop
> > > 2a. alpine-cd2 (anything in main if above 700mb)
> > > ...
> > > 3. alpine-dvd (1+2+2a+community)
> > 
> > Lets take that discussion after v3.3. We are unfortunally running out
> > of time for v3.3 release.
> > 
> > > What if 2+3 had boot options - grsec vanilla ?
> > > Will this help in not creating the smaller sized vanilla and xen isos ?
> > 
> > to late for this kind of changes now.
> > 
> > > Comments welcome.
> > 
> > -nc
> 
> I'll try to come up with list of packages that we could consider moving
> to community.
> 
> Thanks!
> 
> - leo


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---