[gentoo-portage-dev] Next meeting

[gentoo-portage-dev] Next meeting

[Brian Dolbec]

I've scheduled a meeting for tomorrow, March 10, 2016 at 20:30 UTC
(8:30PM UTC)

topics:

1) next release
2) repoman stage2 rewrite merge status
3) repoman stage3 rewrite discussion for moving data
   to the tree/api.gentoo.org
4) open discussion

-- 
Brian Dolbec <dolsen>

Re: [gentoo-portage-dev] Next meeting

[Brian Dolbec]

[-- Attachment #1: Type: text/plain, Size: 659 bytes --]

On Wed, 9 Mar 2016 12:07:13 -0800
Brian Dolbec <dolsen@gentoo.org> wrote:

> I've scheduled a meeting for tomorrow, March 10, 2016 at 20:30 UTC
> (8:30PM UTC)
> 
> topics:
> 
> 1) next release
> 2) repoman stage2 rewrite merge status
> 3) repoman stage3 rewrite discussion for moving data
>    to the tree/api.gentoo.org
> 4) open discussion
> 

The meeting log for today's meeting is available for download at [1]
but is also attached to this email.  The Meetings wiki page [2] has also
been updated.

[1] http://dev.gentoo.org/~dolsen/meeting-logs/portage/2016-03-10.log
[2] https://wiki.gentoo.org/wiki/Project:Portage/Meetings

-- 
Brian Dolbec <dolsen>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 2016-03-10.log --]
[-- Type: text/x-log, Size: 8001 bytes --]

[12:19] <dol-sen> Portage team meeting starts in 10 minutes
[12:20] <dol-sen> provided bernalex gets home in time ;)
[12:22] <bernalex> dol-sen: zmedico: here.
[12:22] <zmedico> hi
[12:22] <dol-sen> :)
[12:23] <dol-sen> you want to start now? or wait another 6 min.
[12:24] <bernalex> dol-sen: get going already! ;)
[12:24] <zmedico> I'm ready
[12:24] <dol-sen> ok, first thing...
[12:24] <dol-sen> next release
[12:24] <dol-sen> I think we need to get a release out that we can make stable, 2.2.27 has too many bugs for that I think
[12:25] <bernalex> hmm ok
[12:25] <zmedico> yeah, it's buggy
[12:25] <bernalex> we can make a conservative release, and move most of the things in the tracker to a .28.
[12:26] <dol-sen> current git has some portageq fixes, plus a bunch of other bugfixes, but not really anything else
[12:26] <dol-sen> portageq fixes are needed for the herds to project changes
[12:27] <maffblaster> dol-sen: Thanks for the help.
[12:27] <maffblaster> I found the answer.
[12:27] <dol-sen> so if we make a release of the current, (adding my repoman commit from this morning) that one should be able to be stabilized
[12:27] <maffblaster> dol-sen: It was a permissions issue. /etc/portage/repos.conf/newoverlay.conf was not readable by others.
[12:28] <dol-sen> ok
[12:28] <zmedico> yeah, changes look pretty conservative
[12:28] <bernalex> there's no repoman commit from this morning
[12:28] <bernalex> oh the patch
[12:28] <bernalex> I thought you meant in git
[12:28] <dol-sen> posted, not pushed
[12:28] <bernalex> you have a spelling error in the msg :p
[12:29] <bernalex> at a glance it looks OK (& conservative)
[12:29] <dol-sen> as much as I'd like to merge the repoman rewrite for the next release, I think it has potential to mess up stabilization
[12:29] <dol-sen> it's been tested fairly well by myself and floppym, with no issues now
[12:29] <bernalex> yes -- repoman rewrite obviously can't go into a conservative stable release.
[12:30] <dol-sen> but I have not tested out the other vcs types to any real extent
[12:30] <bernalex> maybe we should put out .27 as a stable release, and then shoot for repoman (and bugfixes) for .28, and then basically move everything else for a .29?
[12:30] <dol-sen> bernalex, your behind the times
[12:31] <dol-sen> .27 is already released
[12:31] <bernalex> +1 on all
[12:31] <dol-sen> next up is .28
[12:31] <bernalex> yeah 27 was the Januray one, sorry
[12:31] <bernalex> January
[12:31] <zmedico> sounds good
[12:31] <dol-sen> so we could push out .28 now, .29 soon with .28 targeted as stable
[12:32] * sungami has quit (Ping timeout: 250 seconds)
[12:32] <bernalex> yes
[12:32] <dol-sen> .29 if all is well, then stabilize
[12:32] <dol-sen> but rely on .28 as the stable one
[12:32] <dol-sen> ok, sounds good
[12:32] <bernalex> yes, I think we should aim at .29 only being the repoman merge and important bugfixes
[12:33] <bernalex> to make sure it's not too crazy
[12:33] <dol-sen> any last items to merge before .28?
[12:33] * sungami (~sungami@unaffiliated/sungami) has joined
[12:33] <bernalex> not unless zmedico has anything. I have a few things going on, but they're super old bugs so they're not important.
[12:33] <zmedico> no, nothing
[12:34] <dol-sen> ok, I'll work on it this afternoon
[12:34] <bernalex> let me know if you need anything from me -- I'll be available your nighttime at least.
[12:34] <dol-sen> repoman, after zac finishes a last check, I think it's ready to merge
[12:35] <bernalex> w00t!
[12:35] <zmedico> nice
[12:35] <dol-sen> I'll send an email to -dev to test it more, especially for vcs type other than git
[12:35] <dol-sen> once it is in master
[12:36] <bernalex> yeah that's useful
[12:36] <dol-sen> without creating a CVS server, I don't know if cvs code will get any testing
[12:37] <dol-sen> I still have an old cvs checkout, but without a server we can't test commit
[12:37] <dol-sen> and should we even include cvs in a release?
[12:37] <zmedico> probably not
[12:37] <bernalex> maybe just ask the users
[12:38] * zmedico thinks everyone but gentoo moved on from cvs long ago
[12:38] <dol-sen> we can leave it in master for now, if it doesn't get testing, leave it out of the release
[12:38] <dol-sen> eventually nuke it
[12:38] <bernalex> ok
[12:39] <dol-sen> it'll be in the history if it's needed again
[12:39] <dol-sen> ok, stage3...
[12:39] <dol-sen> there is a lot of the repoman data that is currently embedded in the code and needs a release for any changes
[12:40] <dol-sen> I want to gather all that editable data and move it out of the code
[12:40] <dol-sen> like deprecated eclasses to check for,...
[12:41] <dol-sen> stuff that could be placed in the tree or made downloadable from api.g.o
[12:41] <zmedico> nice
[12:41] * javaJake (~javaJake@unaffiliated/javajake) has joined
[12:41] <bernalex> sounds sensible.
[12:41] <dol-sen> so, what should we do, put it in the tree so it's always current?
[12:41] <dol-sen> or make it a download fetch
[12:42] <dol-sen> I think as a file or files in /profiles or /metadata
[12:42] <dol-sen> in the tree
[12:43] <bernalex> I'm not sure I see the dis/advantages of putting it in the tree or making it a fetch.
[12:43] <dol-sen> then any dev can keep it up to date and all other devs immediately get that data for their repoman scans
[12:43] <zmedico> yeah
[12:44] <dol-sen> doing a fetch type means adding in code like ssl-fetch which I would use to do it
[12:44] <dol-sen> in the tree, it's just always there
[12:44] <dol-sen> to put it in the tree do we need a council vote? or some such?
[12:45] <dol-sen> or a -dev bikeshed?
[12:45] <bernalex> ugh. probably. but tree sounds better.
[12:45] <zmedico> yeah, better bikeshed it on -dev
[12:46] <dol-sen> I'm thinking it might be a directory of files
[12:47] <dol-sen> that way it breaks up things a bit so hopefully end up with less breakage from a careless dev
[12:47] <dol-sen> ok...
[12:48] <dol-sen> zmedico, you want to work on the paralleling for it for stage3?
[12:48] <dol-sen> I'll work on the data extraction
[12:48] <zmedico> dol-sen: sure
[12:49] <dol-sen> after the stage2 merge we just keep adding to the repoman branch
[12:49] <dol-sen> ok
[12:49] <zmedico> ok
[12:50] <dol-sen> next :)
[12:50] <dol-sen> I'm done
[12:50] <dol-sen> anything else?
[12:50] <bernalex> not really
[12:50] <dol-sen> oh, I forgot about that sync patch
[12:50] <bernalex> oh :)
[12:51] <dol-sen> bernalex, you commented on the lack of reasoning for it
[12:51] <dol-sen> if I clear that up in the commit message, merge it for .28?
[12:52] <dol-sen> [gentoo-portage-dev] [PATCH] Add sync-git-clone-extra-opts and sync-git-pull-extra-opts
[12:52] <bernalex> yes
[12:53] <dol-sen> zmedico, you see any potential issues in the patch code?
[12:54] <zmedico> dol-sen: lgtm
[12:54] <dol-sen> thanks
[12:55] <dol-sen> qiuet  <= typo #1
[12:55] <dol-sen> bernalex, any more?
[12:56] <bernalex> can't think of anything in particular. I'll try to fix up the trackers tomorrow morning.
[12:56] <dol-sen> any more typos?
[12:57] <bernalex> didn't see nay
[12:57] <dol-sen> ok
[12:58] <dol-sen> alright then
[12:59] <dol-sen> I suppose only thing left is to decide when we should do this again
[13:00] <dol-sen> we should be havng meetings more often
[13:00] <bernalex> hm. I suppose.
[13:01] <bernalex> any preferences?
[13:01] <dol-sen> I'm open
[13:01] <dol-sen> 2nd week in April?
[13:01] <bernalex> sure
[13:01] <dol-sen> 10-16
[13:02] <dol-sen> want to make the whenisgood for that week?
[13:02] <bernalex> I prefer not Tue/Thu. but I can make those work too.
[13:02] <bernalex> yes, sure.
[13:02] <dol-sen> ok, /me adjourns this meeting :)
[13:04] <bernalex> I'll fix the tracker + whenisgood tomorrow & email updates in that regard
[13:04] <bernalex> maybe you want to post a quick email summarising the meeting? I could do that too, but it won't be until tomorrow