Repository release about catalogue-development HOT 4 CLOSED

Ok well it's not obvious.

Release mechanism is in fact important part of the development.

But let's start at the more basic question: who can do what?
Because we (organisation/admins) have the ability to decide which user has access to which repositories and which level of access he has, the answer in general is simple:
If the site allows you to do something, you can do it. Of course there is a level of trust we give you, so that some people can delete whole repositories or even organisation, but we expect them not to.

So returning to the release mechanism. As a result of how we assigned organisation teams, currently everyone who is a member of BSData has push access to at least all catalogue repositories (but not the bsdata repo). And that push access gives you the ability to use the release mechanism.

So to sum up: everyone can do releases.

Now onto the second part: when to release?
Of course, it depends :D

In general, if some problem or enhancement is solved/done, release it. However because of the way appspot app works, each release uses part of a limit equal to the weight of repo.

So to not use up much of that limit (it's day-based, 24h limit), we recommend no more than one release a day.

More often releases are better. There is no point in holding out bugfixes etc. Just try not to do more than 1 per 24hrs. That means if you know someone is working, wait for him to finish and combine the release. If not, do it on yourself.

from catalogue-development.

How does one go about doing a release properly?

from catalogue-development.

I was wondering this yesterday... have you seen this? https://github.com/BSData/bsdata/wiki/Developer-Guide#releasing

from catalogue-development.

Closed because of age

from catalogue-development.