bodhi2 plans

[Vít Ondruch]

Just a few remarks:

* I hoped that it will be possible to combine "type" of upgrade such as
"enhancement + security", but this is not possible it seem :/
* It would be nice if I can select which bug will be closed by this
update and which stays untouched. It happens that update fixes several
bugs, but one bug should be fixed in multiple branches, so I probably
don't want to close it unless I fix the other branch. Also, it would be
nice if Bodhi can identify bugs, which are included in several updates
and the last update pushed stable would close the associated issue.
* I really don't know what is the severity good for. There are probably
people, who always know precisely, but I find this useless.

 Anyway, the "null" updates looks strange to me ...


Vít



Dne 3.8.2015 v 19:03 Kevin Fenzi napsal(a):
> Greetings. 
>
> So, in the releng meeting last week we discussed about landing bodhi2
> before the alpha freeze started, however there were just too many
> things still up in the air to do that, so we held off. 
>
> However, I'd like to propose a concrete date to enable it and try and
> make sure we have everything we need lined up for making that work. :) 
>
> My understanding of the current status: 
> (Luke: please correct me if anything is wrong or unclear here)
>
> * We have bodhi2 web frontend up and running fine in staging: 
> https://admin.stg.fedoraproject.org/updates/
> (well, right now it's down as Luke is working on a update id bug there
> and is repopulating the db, but it was and will be up again soon). 
>
> * We have a bodhi2 backend up in staging and it's successfully mashed
>   updates pushes. 
>
> * bodhi2 isn't yet packaged in Fedora (it and it's deps are in a copr): 
> http://copr.fedoraproject.org/coprs/lmacken/bodhi2/
>
> So, to get that last bit we need: 
>
> * API users. I thought we had a list somewhere, but I cannot seem to
>   find it. At least fedora-easy-karma and fedora-gooey-karma use it.
>   Are all of these using python-fedora for the api? Do we need to
>   update that and bodhi-client? 
>
> * We need bodhi2 in fedora/epel. Were we going to do it as a seperate
>   package, or just an update to the existing 'bodhi' package. I assume
>   maintainers would need the new client to do 'fedpkg update' ?
>
> * Do we need any fedpkg changes? Or anything else? How do we want to
>   handle the switchover?
>
> * Is taskotron all ready to go with bodhi2? or more changes there?
>
> * We will need an outage to switch over. I assume the bodhi1->bodhi2 db
>   conversion shouldn't take too long? But once we convert and make live
>   we are commmited. 
>
> * Anything else I missed?
>
> I'd like to propose we schedule the switchover/outage for 2015-08-19. 
> (Provided alpha doesn't slip). This will allow us a few days to recover
> from flock and get anything lined up we need to. 
>
> Thoughts? additions? 
>
> kevin
>
>
> _______________________________________________
> infrastructure mailing list
> infrastructure at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/infrastructure

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/infrastructure/attachments/20150804/2ec94ba2/attachment-0001.html>