Skip to contentSkip to conversation

More frequent kexec-tools releases

DISCUSSION Vivek Goyal 6 participants 20 messages Jan 28, 2014 – Feb 25, 2014

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi All,

Just now we were discussing that fedora kexec-tools should rebase to upstream kexec-tools every release so that we can test the latest code sooner.

Then Dave Young pulled in some data about the kexec-tools release duration.

Date: Tue Mar 19 10:46:46 2013 +0900

    kexec-tools 2.0.4 ~100 commits

Date: Mon Jan 16 09:15:25 2012 +1100

    kexec-tools 2.0.3 ~100 commits

Date: Thu Jul 29 13:40:00 2010 +0900

    kexec-tools 2.0.2 ~80 commits

Date: Thu Aug 13 09:28:08 2009 +1000

    kexec-tools 2.0.1 ~60 commits

Date: Sat Jul 19 10:31:30 2008 +1000

    kexec-tools 2.0.0

So that is 5 release in 5.5 years. It is roughly 1 release per year.

I am wondering if there is any interest in more frequent releases of kexec-tools. Say every 3 months or every 6 months.

IMHO, it might be better if there are more frequent release of kexec-tools (say a release every 6 months) and then every 6 months distributions should be able to rebase to that new release.

Thoughts?

Thanks
Vivek

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#1 lore raw

Hello

Quoted 26 lines · Vivek Goyal

Hi All,

Just now we were discussing that fedora kexec-tools should rebase to upstream kexec-tools every release so that we can test the latest code sooner.

Then Dave Young pulled in some data about the kexec-tools release duration.

Date: Tue Mar 19 10:46:46 2013 +0900

    kexec-tools 2.0.4 ~100 commits

Date: Mon Jan 16 09:15:25 2012 +1100

    kexec-tools 2.0.3 ~100 commits

Date: Thu Jul 29 13:40:00 2010 +0900

    kexec-tools 2.0.2 ~80 commits

Date: Thu Aug 13 09:28:08 2009 +1000

    kexec-tools 2.0.1 ~60 commits

Date: Sat Jul 19 10:31:30 2008 +1000

    kexec-tools 2.0.0

So that is 5 release in 5.5 years. It is roughly 1 release per year.

Quoted 8 lines

I am wondering if there is any interest in more frequent releases of kexec-tools. Say every 3 months or every 6 months.

IMHO, it might be better if there are more frequent release of kexec-tools (say a release every 6 months) and then every 6 months distributions should be able to rebase to that new release.

Thoughts?

Agreed. Sometimes, important changes in the kernel side will lead to the change in the kexec-tools, so especially in this case, I think it might be better to release a new version asap.

Quoted 9 lines

Thanks
Vivek

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

Signature · 7 lines
Thanks.
Zhang Yanfei

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
#2 lore raw
Quoted 36 lines · Zhang Yanfei

Hello

Quoted 33 lines · Vivek Goyal

Hi All,

Just now we were discussing that fedora kexec-tools should rebase to upstream kexec-tools every release so that we can test the latest code sooner.

Then Dave Young pulled in some data about the kexec-tools release duration.

Date: Tue Mar 19 10:46:46 2013 +0900

    kexec-tools 2.0.4 ~100 commits

Date: Mon Jan 16 09:15:25 2012 +1100

    kexec-tools 2.0.3 ~100 commits

Date: Thu Jul 29 13:40:00 2010 +0900

    kexec-tools 2.0.2 ~80 commits

Date: Thu Aug 13 09:28:08 2009 +1000

    kexec-tools 2.0.1 ~60 commits

Date: Sat Jul 19 10:31:30 2008 +1000

    kexec-tools 2.0.0

So that is 5 release in 5.5 years. It is roughly 1 release per year.

I am wondering if there is any interest in more frequent releases of kexec-tools. Say every 3 months or every 6 months.

IMHO, it might be better if there are more frequent release of kexec-tools (say a release every 6 months) and then every 6 months distributions should be able to rebase to that new release.

Quoted 5 lines
Quoted 1 line

Thoughts?

Agreed. Sometimes, important changes in the kernel side will lead to the change in the kexec-tools, so especially in this case, I think it might be better to release a new version asap.

One example is recent support of kexec on EFI systems. These changes went into 3.13 kernel as well as kexec-tools.

Simon what do you think? A kexec-tools release every 4 months or every 6 months. Does it make sense to you?

Thanks
Vivek

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#18 lore raw
In reply to Vivek Goyal
Quoted 2 lines · Vivek Goyal

I am wondering if there is any interest in more frequent releases of kexec-tools. Say every 3 months or every 6 months.

Yes, that will be good. I maintain the kexec-tools package for Debian and I often find myself backporting fixes from git into Debian package as users find bugs that are already fixed in upstream. Being able to update the entire package to new release with all accumulated bugfixes periodically will be helpful.

--
Khalid

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#19 lore raw
Quoted 9 lines · Khalid Aziz
Quoted 2 lines · Vivek Goyal

I am wondering if there is any interest in more frequent releases of kexec-tools. Say every 3 months or every 6 months.

Yes, that will be good. I maintain the kexec-tools package for Debian and I often find myself backporting fixes from git into Debian package as users find bugs that are already fixed in upstream. Being able to update the entire package to new release with all accumulated bugfixes periodically will be helpful.

Agreed. If we have more frequent releases of kexec-tools, then distributions can easily rebase to newer releases more frequently and that will reduce the overhead of cherry-picking and backporting fixes.

Also it allows distribution users to test new features sooner. For example, kexec support on EFI systems. In worst case, a distribution user will have to wait for an year or more before a release happens and user can test this feature. And this is true for any feature which is introduced in kexec-tools.

Thanks
Vivek

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#3 lore raw
In reply to Vivek Goyal
Quoted 43 lines · Vivek Goyal
Quoted 36 lines · Zhang Yanfei

Hello

Quoted 33 lines · Vivek Goyal

Hi All,

Just now we were discussing that fedora kexec-tools should rebase to upstream kexec-tools every release so that we can test the latest code sooner.

Then Dave Young pulled in some data about the kexec-tools release duration.

Date: Tue Mar 19 10:46:46 2013 +0900

    kexec-tools 2.0.4 ~100 commits

Date: Mon Jan 16 09:15:25 2012 +1100

    kexec-tools 2.0.3 ~100 commits

Date: Thu Jul 29 13:40:00 2010 +0900

    kexec-tools 2.0.2 ~80 commits

Date: Thu Aug 13 09:28:08 2009 +1000

    kexec-tools 2.0.1 ~60 commits

Date: Sat Jul 19 10:31:30 2008 +1000

    kexec-tools 2.0.0

So that is 5 release in 5.5 years. It is roughly 1 release per year.

I am wondering if there is any interest in more frequent releases of kexec-tools. Say every 3 months or every 6 months.

IMHO, it might be better if there are more frequent release of kexec-tools (say a release every 6 months) and then every 6 months distributions should be able to rebase to that new release.

Quoted 5 lines
Quoted 1 line

Thoughts?

Agreed. Sometimes, important changes in the kernel side will lead to the change in the kexec-tools, so especially in this case, I think it might be better to release a new version asap.

Quoted 5 lines

One example is recent support of kexec on EFI systems. These changes went into 3.13 kernel as well as kexec-tools.

Simon what do you think? A kexec-tools release every 4 months or every 6 months. Does it make sense to you?

Perhaps we could aim for every second kernel release and see how that goes?

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#4 lore raw

On Fri, Jan 31, 2014 at 02:23:04PM +0900, Simon Horman wrote:

[..]

Quoted 4 lines
Quoted 2 lines

Simon what do you think? A kexec-tools release every 4 months or every 6 months. Does it make sense to you?

Perhaps we could aim for every second kernel release and see how that goes?

Sounds Good. Kernel releases are roughly 3 months apart. So that would mean a kexec-tools release roughly around 6 months. This sounds like a good start.

So 3.13 was release recently. And last kexec-tools release was in march 2013. May be it is a good idea to do one release now and then next one can be after release of kernel 3.15, 3.17 and so on.

Thanks
Vivek

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#5 lore raw
Quoted 8 lines · Vivek Goyal

On Fri, Jan 31, 2014 at 02:23:04PM +0900, Simon Horman wrote:

[..]

Quoted 4 lines
Quoted 2 lines

Simon what do you think? A kexec-tools release every 4 months or every 6 months. Does it make sense to you?

Perhaps we could aim for every second kernel release and see how that goes?

Quoted 7 lines

Sounds Good. Kernel releases are roughly 3 months apart. So that would mean a kexec-tools release roughly around 6 months. This sounds like a good start.

So 3.13 was release recently. And last kexec-tools release was in march 2013. May be it is a good idea to do one release now and then next one can be after release of kernel 3.15, 3.17 and so on.

Yes, I think so too.

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#6 lore raw
Quoted 13 lines · Simon Horman
Quoted 12 lines · Vivek Goyal

On Fri, Jan 31, 2014 at 02:23:04PM +0900, Simon Horman wrote:

[..]

Quoted 4 lines
Quoted 2 lines

Simon what do you think? A kexec-tools release every 4 months or every 6 months. Does it make sense to you?

Perhaps we could aim for every second kernel release and see how that goes?

Sounds Good. Kernel releases are roughly 3 months apart. So that would mean a kexec-tools release roughly around 6 months. This sounds like a good start.

Quoted 5 lines
Quoted 3 lines

So 3.13 was release recently. And last kexec-tools release was in march 2013. May be it is a good idea to do one release now and then next one can be after release of kernel 3.15, 3.17 and so on.

Yes, I think so too.

Would any of you object to me doing this with the current state of the tree as of fe2c38cc0fc32573 ("Avoid buffer overflow on strncat usage").

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#7 lore raw

On Tue, Feb 04, 2014 at 09:41:48PM +0900, Simon Horman wrote:

[..]

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 1 line

Perhaps we could aim for every second kernel release and see how that goes?

Sounds Good. Kernel releases are roughly 3 months apart. So that would mean a kexec-tools release roughly around 6 months. This sounds like a good start.

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines

So 3.13 was release recently. And last kexec-tools release was in march 2013. May be it is a good idea to do one release now and then next one can be after release of kernel 3.15, 3.17 and so on.

Yes, I think so too.

Would any of you object to me doing this with the current state of the tree as of fe2c38cc0fc32573 ("Avoid buffer overflow on strncat usage").

I have no objection.

Thanks
Vivek

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#8 lore raw
In reply to Simon Horman
Quoted 14 lines · Simon Horman
Quoted 13 lines · Simon Horman
Quoted 12 lines · Vivek Goyal

On Fri, Jan 31, 2014 at 02:23:04PM +0900, Simon Horman wrote:

[..]

Quoted 4 lines
Quoted 2 lines

Simon what do you think? A kexec-tools release every 4 months or every 6 months. Does it make sense to you?

Perhaps we could aim for every second kernel release and see how that goes?

Sounds Good. Kernel releases are roughly 3 months apart. So that would mean a kexec-tools release roughly around 6 months. This sounds like a good start.

Quoted 9 lines
Quoted 5 lines
Quoted 3 lines

So 3.13 was release recently. And last kexec-tools release was in march 2013. May be it is a good idea to do one release now and then next one can be after release of kernel 3.15, 3.17 and so on.

Yes, I think so too.

Would any of you object to me doing this with the current state of the tree as of fe2c38cc0fc32573 ("Avoid buffer overflow on strncat usage").

NO objection.

Thanks

Quoted 6 lines

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

Signature · 7 lines
Thanks.
Zhang Yanfei

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec
#9 lore raw
Quoted 19 lines · Zhang Yanfei
Quoted 18 lines · Simon Horman
Quoted 17 lines · Simon Horman
Quoted 15 lines · Vivek Goyal

On Fri, Jan 31, 2014 at 02:23:04PM +0900, Simon Horman wrote:

[..]

Quoted 4 lines
Quoted 2 lines

Simon what do you think? A kexec-tools release every 4 months or every 6 months. Does it make sense to you?

Perhaps we could aim for every second kernel release and see how that goes?

Sounds Good. Kernel releases are roughly 3 months apart. So that would mean a kexec-tools release roughly around 6 months. This sounds like a good start.

So 3.13 was release recently. And last kexec-tools release was in march 2013. May be it is a good idea to do one release now and then next one can be after release of kernel 3.15, 3.17 and so on.

Quoted 7 lines
Quoted 5 lines
Quoted 1 line

Yes, I think so too.

Would any of you object to me doing this with the current state of the tree as of fe2c38cc0fc32573 ("Avoid buffer overflow on strncat usage").

NO objection.

Done :)

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#10 lore raw
Quoted 22 lines · Simon Horman
Quoted 21 lines · Zhang Yanfei
Quoted 20 lines · Simon Horman
Quoted 18 lines · Simon Horman
Quoted 8 lines · Vivek Goyal

On Fri, Jan 31, 2014 at 02:23:04PM +0900, Simon Horman wrote:

[..]

Quoted 4 lines
Quoted 2 lines

Simon what do you think? A kexec-tools release every 4 months or every 6 months. Does it make sense to you?

Perhaps we could aim for every second kernel release and see how that goes?

Quoted 7 lines

Sounds Good. Kernel releases are roughly 3 months apart. So that would mean a kexec-tools release roughly around 6 months. This sounds like a good start.

So 3.13 was release recently. And last kexec-tools release was in march 2013. May be it is a good idea to do one release now and then next one can be after release of kernel 3.15, 3.17 and so on.

Yes, I think so too.

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

Would any of you object to me doing this with the current state of the tree as of fe2c38cc0fc32573 ("Avoid buffer overflow on strncat usage").

NO objection.

Done :)

Thanks Simon. I did git pull but I don't see new tag in my tree. Not sure why.

Thanks
Vivek

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#11 lore raw
Quoted 27 lines · Vivek Goyal
Quoted 26 lines · Simon Horman
Quoted 25 lines · Zhang Yanfei
Quoted 23 lines · Simon Horman
Quoted 13 lines · Simon Horman
Quoted 12 lines · Vivek Goyal

On Fri, Jan 31, 2014 at 02:23:04PM +0900, Simon Horman wrote:

[..]

Quoted 4 lines
Quoted 2 lines

Simon what do you think? A kexec-tools release every 4 months or every 6 months. Does it make sense to you?

Perhaps we could aim for every second kernel release and see how that goes?

Sounds Good. Kernel releases are roughly 3 months apart. So that would mean a kexec-tools release roughly around 6 months. This sounds like a good start.

Quoted 5 lines
Quoted 3 lines

So 3.13 was release recently. And last kexec-tools release was in march 2013. May be it is a good idea to do one release now and then next one can be after release of kernel 3.15, 3.17 and so on.

Yes, I think so too.

Would any of you object to me doing this with the current state of the tree as of fe2c38cc0fc32573 ("Avoid buffer overflow on strncat usage").

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

NO objection.

Done :)

Thanks Simon. I did git pull but I don't see new tag in my tree. Not sure why.

Could you try again? I messed up the push.

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#13 lore raw
Quoted 9 lines · Vivek Goyal

On Thu, Feb 06, 2014 at 10:55:13AM +0900, Simon Horman wrote:

[..]

Quoted 4 lines
Quoted 2 lines

Thanks Simon. I did git pull but I don't see new tag in my tree. Not sure why.

Could you try again? I messed up the push.

It works now. Thanks.

It seems that a few bugs showed up in 2.0.5, fixes for which are now in the git repository. I am thinking it would be a good idea to release these as 2.0.6 unless people would rather that I held off.

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#14 lore raw
Quoted 7 lines · Simon Horman
Quoted 6 lines · Vivek Goyal

On Thu, Feb 06, 2014 at 10:55:13AM +0900, Simon Horman wrote:

[..]

Quoted 3 lines
Quoted 2 lines

Thanks Simon. I did git pull but I don't see new tag in my tree. Not sure why.

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

Could you try again? I messed up the push.

It works now. Thanks.

It seems that a few bugs showed up in 2.0.5, fixes for which are now in the git repository. I am thinking it would be a good idea to release these as 2.0.6 unless people would rather that I held off.

I'm fine with a new release, thanks a lot.

Dave

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#15 lore raw
In reply to Simon Horman
Quoted 7 lines · Simon Horman
Quoted 6 lines · Vivek Goyal

On Thu, Feb 06, 2014 at 10:55:13AM +0900, Simon Horman wrote:

[..]

Quoted 3 lines
Quoted 2 lines

Thanks Simon. I did git pull but I don't see new tag in my tree. Not sure why.

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

Could you try again? I messed up the push.

It works now. Thanks.

It seems that a few bugs showed up in 2.0.5, fixes for which are now in the git repository. I am thinking it would be a good idea to release these as 2.0.6 unless people would rather that I held off.

I am fine with new release.

In future you might have to come up with a process where you merge only important fixes so that you can do a stable release.

May be create a development branch 2-3 weeks before final release. Master branch slowly will get ready for release and will get only important fixes committed. Devel branch will have everything. And after release, devel will be rebased on top of master and merged or some other better process.

Thanks
Vivek

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#16 lore raw
Quoted 18 lines · Vivek Goyal
Quoted 7 lines · Simon Horman
Quoted 6 lines · Vivek Goyal

On Thu, Feb 06, 2014 at 10:55:13AM +0900, Simon Horman wrote:

[..]

Quoted 3 lines
Quoted 2 lines

Thanks Simon. I did git pull but I don't see new tag in my tree. Not sure why.

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

Could you try again? I messed up the push.

It works now. Thanks.

It seems that a few bugs showed up in 2.0.5, fixes for which are now in the git repository. I am thinking it would be a good idea to release these as 2.0.6 unless people would rather that I held off.

I am fine with new release.

Quoted 8 lines

In future you might have to come up with a process where you merge only important fixes so that you can do a stable release.

May be create a development branch 2-3 weeks before final release. Master branch slowly will get ready for release and will get only important fixes committed. Devel branch will have everything. And after release, devel will be rebased on top of master and merged or some other better process.

I think something like that should work quite well.

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#17 lore raw
In reply to Simon Horman
Quoted 7 lines · Simon Horman
Quoted 6 lines · Vivek Goyal

On Thu, Feb 06, 2014 at 10:55:13AM +0900, Simon Horman wrote:

[..]

Quoted 3 lines
Quoted 2 lines

Thanks Simon. I did git pull but I don't see new tag in my tree. Not sure why.

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

Could you try again? I messed up the push.

It works now. Thanks.

It seems that a few bugs showed up in 2.0.5, fixes for which are now in the git repository. I am thinking it would be a good idea to release these as 2.0.6 unless people would rather that I held off.

As you mentioned, I found 2.0.5 doesn't build on i386. I consider these are major bugs, which deserves a hot fix release as 2.0.6. What do you think?

Thanks
WANG Chao

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec