Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Enter Payment to Vendor
01-09-2018, 01:25 AM,
#7
RE: Enter Payment to Vendor
(01-08-2018, 08:10 AM)falkoner Wrote: What we should really do is return to the days when we kept a stable branch. That is a branch whose root is the last release, but only has bug fixes applied to it and none of the new features. Then people can download scripts with bug fixes without worrying that they corrupt their current code base with new features which could block other areas. Perhaps something you could consider running Paul (Thursby)?

Tim

I agree that fixes should be separate from new and/or extended features. This would prevent confusion, which we often see with respect to DB schema for example.

It appears we don't really use the typical SVN Tag/Branch/Trunk schema so perhaps we should include fixes in the trunk and new/extended features only in a coming-release branch.

While this is more work I think it would benefit all involved.
https://www.linkedin.com/in/eclipsepaulbecker
Reply


Messages In This Thread
Enter Payment to Vendor - by briantmg - 01-06-2018, 10:15 AM
RE: Enter Payment to Vendor - by briantmg - 01-07-2018, 02:06 AM
RE: Enter Payment to Vendor - by TurboPT - 01-07-2018, 02:55 AM
RE: Enter Payment to Vendor - by briantmg - 01-07-2018, 03:55 AM
RE: Enter Payment to Vendor - by TurboPT - 01-07-2018, 05:26 AM
RE: Enter Payment to Vendor - by TimSchofield - 01-08-2018, 08:10 AM
RE: Enter Payment to Vendor - by VortecCPI - 01-09-2018, 01:25 AM
RE: Enter Payment to Vendor - by TimSchofield - 01-09-2018, 02:10 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)