On Wed, Mar 18, 2015 at 09:44:56AM -0600, Kevin Fenzi wrote:
On Wed, 18 Mar 2015 15:25:48 +0100
Pierre-Yves Chibon <pingou(a)pingoured.fr> wrote:
> Hi everyone,
> The next pkgdb2 release (1.24) will be a pretty big releases, to give
> you an idea this is its current changelog:
...snip good stuff...
> Since these changes might be pretty big and impact multiple person, I
> would like to hear when people think it would be best to make the
> Note: I will not do it today, but basically I could from tomorrow :)
I'd say do it tomorrow. ;)
Well, is it already in stg and working there?
The main changes are running in stg yes (the new package/branch requests), the
other changes are either running already in prod (backported to 1.23) or are
small enough that I do not expect any problem.
I'd say push to staging and make sure there's nothing
broken, then go to prod.
Sure, I can cut a 1.24 tomorrow and push it to prod.
> Note2: As it will likely take a little time for people to get
> adjusted to the new workflow (that needs to be documented & so on),
> there will likely be a time for pkgdb admins and releng when they
> will have to check both bugzilla and pkgdb.
Right. However, we should be able to roll this out and keep using the
old process for new packages and branches right? ie, maintainers don't
even need to know this is there unless we ask them to try it?
Yes, since we do not touch bugzilla nor the way packages are created in pkgdb,
the old process will work just fine.
So, we should be able to put it in place and have a small group of
folks test things and fix issues, and only then announce to maintainers
to switch to the new process.
Sounds good :)
Only people might notice the big blue button on the front page:
That's one way to make them aware I guess ;-)