@Jord, I'm afraid, you're wrong. Last release was made 5 Jun 2016. Since
that there was many commits.
Also there are many changed which were committed to master but were not
integrated into release branch.

Best regards,
Vitalii Koshura

2017-03-29 17:20 GMT+03:00 Jord van der Elst <els...@gmail.com>:

> I've just run git log on the BOINC repository and see something
> immediately:
>
> * | 967fa51ce3 : Add 7.7.2
> * | d310efc264 : client: parse njobs_error in state file (don't lose info
> on transition)
> * | 2c493f50c1 : Update Installshield files and vboxwrapper version
> * | 7436252a47 : change version to 7.7.2
>
> (You should see those in reverse, but I cannot do a reverse log because of
> my pretty formatting. I use this command: git log --since=06-06-2016
> --pretty=format:"%h : %s" --graph > logN-since0606201.txt)
>
> So I suspect that those are the only updates that made it into 7.7.2
>
>
>
> -- Jord van der Elst.
>
> On Wed, Mar 29, 2017 at 4:11 PM, Vitalii Koshura <
> lestat.de.lion...@gmail.com> wrote:
>
>> OK, in this case I'll just go through the list of commits and find the
>> corresponded issues which were fixed. I do not know what to do with tons
>> of
>> commits that were not included previously into the release branch. Maybe
>> I'll save them as some kind of 'ChangeLog'.
>>
>> Best regards,
>> Vitalii Koshura
>>
>> 2017-03-29 17:00 GMT+03:00 Oliver Bock <oliver.b...@aei.mpg.de>:
>>
>> > On 29/03/2017 13:17 , Vitalii Koshura wrote:
>> > > but currently we have another situation:
>> > > master branch can not be a start point for new release branch.
>> >
>> > It's not a matter of whether it should or even can be. It's a matter of
>> > fact that the latest release (7.7.2) was build from master if I'm not
>> > mistaken. Thus the release branch needs to reflect that, otherwise the
>> > release and its branch would simply be inconsistent.
>> >
>> > Best,
>> > Oliver
>> >
>> _______________________________________________
>> boinc_dev mailing list
>> boinc_dev@ssl.berkeley.edu
>> https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
>> To unsubscribe, visit the above URL and
>> (near bottom of page) enter your email address.
>>
>
>
_______________________________________________
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to