Is Fedora 27 EOL?

[Florian Weimer]

There has been no EOL announcement, my guess for the EOL data
(2018-11-30) has not passed yet, but I get this when pushing to
src.fedoraproject.org:

remote: Running hooks for rpms/glibc
remote: Branch refs/heads/f27 is unsupported
remote: Denied push for ref 'refs/heads/f27' for user 'fweimer'
remote: All changes have been rejected

Is Fedora 27 EOL or not?

Thanks,
Florian
_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.o

[John Florian]

Post by Florian Weimer
There has been no EOL announcement, my guess for the EOL data
(2018-11-30) has not passed yet

At the very least, I don't recall seeing the announcement that it will
be EOL in ~30 days.
_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@lists.fedorap

[Ben Cotton]

Post by John Florian
At the very least, I don't recall seeing the announcement that it will
be EOL in ~30 days.

That's my fault. I missed my reminder to send it. I apologize for the
short notice.

--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorap

[Mohan Boddu]

The 27 EOL should be tomorrow.

The n release gets EOL'ed 4 weeks after n+2 release.

But I am not sure why fedpkg is rejecting the push.

Post by Ben Cotton

Post by John Florian
At the very least, I don't recall seeing the announcement that it will
be EOL in ~30 days.

That's my fault. I missed my reminder to send it. I apologize for the
short notice.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

[Ben Cotton]

Post by Mohan Boddu
The 27 EOL should be tomorrow.
The n release gets EOL'ed 4 weeks after n+2 release.

The policy on the wiki[1] says "one month", which is fairly ambiguous.
I'll update that to say "four weeks", which is what we mean, but is
not the practical interpretation of what we say. Since I dropped the
ball on this, let's do the F27 EOL on Friday and I'll fix both the
text of the policy and my own workflow to prevent this issue in the
future.


--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/

[Florian Weimer]

Post by Ben Cotton

Post by Mohan Boddu
The 27 EOL should be tomorrow.
The n release gets EOL'ed 4 weeks after n+2 release.

The policy on the wiki[1] says "one month", which is fairly ambiguous.
I'll update that to say "four weeks", which is what we mean, but is
not the practical interpretation of what we say. Since I dropped the
ball on this, let's do the F27 EOL on Friday and I'll fix both the
text of the policy and my own workflow to prevent this issue in the
future.

I don't understand.

Fedora 27 is already EOL *today* because it is impossible to push
updates:

$ git push
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 531 bytes | 531.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Running hooks for rpms/glibc
remote: Branch refs/heads/f27 is unsupported
remote: Denied push for ref 'refs/heads/f27' for user 'fweimer'
remote: All changes have been rejected
To ssh://pkgs.fedoraproject.org/rpms/glibc
! [remote rejected] HEAD -> f27 (pre-receive hook declined)
error: failed to push some refs to 'ssh://***@pkgs.fedoraproject.org/rpms/glibc'

Thanks,
Florian
_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archive

[Mohan Boddu]

I am working on fixing it.

It should be fixed soon, I will send an update once its fixed.

Post by Florian Weimer

Post by Ben Cotton

Post by Mohan Boddu
The 27 EOL should be tomorrow.
The n release gets EOL'ed 4 weeks after n+2 release.

The policy on the wiki[1] says "one month", which is fairly ambiguous.
I'll update that to say "four weeks", which is what we mean, but is
not the practical interpretation of what we say. Since I dropped the
ball on this, let's do the F27 EOL on Friday and I'll fix both the
text of the policy and my own workflow to prevent this issue in the
future.

I don't understand.
Fedora 27 is already EOL *today* because it is impossible to push
$ git push
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 531 bytes | 531.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Running hooks for rpms/glibc
remote: Branch refs/heads/f27 is unsupported
remote: Denied push for ref 'refs/heads/f27' for user 'fweimer'
remote: All changes have been rejected
To ssh://pkgs.fedoraproject.org/rpms/glibc
! [remote rejected] HEAD -> f27 (pre-receive hook declined)
error: failed to push some refs to 'ssh://
Thanks,
Florian
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

[Matthew Miller]

Post by Ben Cotton
The policy on the wiki[1] says "one month", which is fairly ambiguous.
I'll update that to say "four weeks", which is what we mean, but is
not the practical interpretation of what we say. Since I dropped the
ball on this, let's do the F27 EOL on Friday and I'll fix both the
text of the policy and my own workflow to prevent this issue in the
future.

For the record, FESCo ticket where 4 weeks / 28 days was made official:
https://pagure.io/fesco/issue/1750



--
Matthew Miller
<***@fedoraproject.org>
Fedora Project Leader
_______________________________________________
devel mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to devel-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.o

[Mohan Boddu]

I am still updating the EOL's in pdc, but some of them should be updated.

I will send another email once all of them are updated.

Post by Matthew Miller

Post by Ben Cotton
The policy on the wiki[1] says "one month", which is fairly ambiguous.
I'll update that to say "four weeks", which is what we mean, but is
not the practical interpretation of what we say. Since I dropped the
ball on this, let's do the F27 EOL on Friday and I'll fix both the
text of the policy and my own workflow to prevent this issue in the
future.

https://pagure.io/fesco/issue/1750
--
Matthew Miller
Fedora Project Leader
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

[Mohan Boddu]

Okay, all of the eol entries for f27 in pdc should be updated now.

Please create a ticket at https://pagure.io/releng if you find any issues.

Thanks.

Post by Mohan Boddu
I am still updating the EOL's in pdc, but some of them should be updated.
I will send another email once all of them are updated.

Post by Matthew Miller

Post by Ben Cotton
The policy on the wiki[1] says "one month", which is fairly ambiguous.
I'll update that to say "four weeks", which is what we mean, but is
not the practical interpretation of what we say. Since I dropped the
ball on this, let's do the F27 EOL on Friday and I'll fix both the
text of the policy and my own workflow to prevent this issue in the
future.

https://pagure.io/fesco/issue/1750
--
Matthew Miller
Fedora Project Leader
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines