[Bf-committers] BLENDER_VERSION_CHAR

[Sergey Sharybin]

They are specified properly in an appropriate branch/tag.

If we do 'a' release it totally happens in the tag now and we only backport
there crucial fixes.

It's arguable, but don't really think doing 'a' release in a tag would make
master branch having 'a' character as well. It's just two different
projects. Master is more like a RR.


On Thu, Jun 5, 2014 at 4:27 AM, IRIE Shinsuke <irieshinsuke at yahoo.co.jp>
wrote:

> > Because we started 2.71 release cycles in master when we've released
> 2.70a.
>
> That's curious. The 2.71 release cycle has already started when v2.70-rc
> tag was created:
>
> https://developer.blender.org/rBe097c987a8a55f2eb09c19ceac923e7c32e19d89
>
> As far as I remember, BLENDER_VERSION and BLENDER_VERSION_CHAR have been
> used for indicating latest release version. When 2.68a was released, the
> version char was indeed bumped to "a", and changed again to "" for 2.69
> release:
>
> https://developer.blender.org/rBd9b0f660c9e49b13abc212270c0e8a366a2a096f
> https://developer.blender.org/rBdfe16105041292a1fc7ee29d825c25135a4f6a3c
>
> We have another macro BLENDER_VERSION_CYCLE to indicate the release cycle.
>
> > What's the issue anyway?
>
> If BLENDER_VERSION or BLENDER_VERSION_CHAR is not update properly,
> I have to specify package version of my own deb packages manually...
>
> IRIE Shinsuke
>
> 2014/06/05, Sergey Sharybin wrote:
> > Because we started 2.71 release cycles in master when we've released
> 2.70a.
> >
> > What's the issue anyway?
> >
> >
> > On Wed, Jun 4, 2014 at 10:49 PM, IRIE Shinsuke <irieshinsuke at yahoo.co.jp
> >
> > wrote:
> >
> >> Why was the version char changed only in the tag?
> >> I think the same change should have happened in git master as well.
> >>
> >> IRIE Shinsuke
> >>
> >> 2014/06/05, Sergey Sharybin wrote:
> >>> Not sure why cambo showed that commit as an example. Actual change
> >> happened
> >>> when we've been doing 2.70a release. The char was changed in the tag,
> >>> see f93bc7693a530632455d3ec7acc4bce54a1f85bc.
> >>>
> >>>
> >>> On Wed, Jun 4, 2014 at 10:04 PM, IRIE Shinsuke <
> irieshinsuke at yahoo.co.jp
> >>>
> >>> wrote:
> >>>
> >>>> rBdfe161050412 was a version bump for 2.69 release.
> >>>> BLENDER_VERSION was indeed changed from 268 to 269 in this commit.
> >>>>
> >>>> BLENDER_VERSION_CHAR should've been changed when 2.70a was released
> >>>> but it remains blank since 2.69 release.
> >>>>
> >>>> IRIE Shinsuke
> >>>>
> >>>> 2014/06/05, Campbell Barton wrote:
> >>>>> Its still in use, it was changed after 2.70a
> >>>>>
> >>
> https://developer.blender.org/rBdfe16105041292a1fc7ee29d825c25135a4f6a3c
> >>>>>
> >>>>> On Thu, Jun 5, 2014 at 12:57 AM, IRIE Shinsuke <
> >> irieshinsuke at yahoo.co.jp>
> >>>> wrote:
> >>>>>> Hi devs,
> >>>>>>
> >>>>>> Recently I noticed BLENDER_VERSION_CHAR in BKE_blender.h has not
> been
> >>>>>> changed since Oct. 8 2013 though 2.69, 2.70, and 2.70a were released
> >>>>>> after that.
> >>>>>>
> >>>>>> Is this macro obsoleted?  If so, I have to stop using it to build
> own
> >>>>>> .deb packages. If not, please don't forget to update it...
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> --
> >>>>>> IRIE Shinsuke
> >>>>>> _______________________________________________
> >>>>>> Bf-committers mailing list
> >>>>>> Bf-committers at blender.org
> >>>>>> http://lists.blender.org/mailman/listinfo/bf-committers
> >>>>>
> >>>>>
> >>>>>
> >>>> _______________________________________________
> >>>> Bf-committers mailing list
> >>>> Bf-committers at blender.org
> >>>> http://lists.blender.org/mailman/listinfo/bf-committers
> >>>>
> >>>
> >>>
> >>>
> >> _______________________________________________
> >> Bf-committers mailing list
> >> Bf-committers at blender.org
> >> http://lists.blender.org/mailman/listinfo/bf-committers
> >>
> >
> >
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
With best regards, Sergey Sharybin