Loomio

Adopt a versioning scheme and release cycle.

ST Sean Tilley Public Seen by 41
ST

Poll Created Thu 30 Aug 2012 4:54PM

Adopt a versioning scheme and release cycle. Closed Sat 1 Sep 2012 11:57PM

One thing that would immensely help developers and podmins alike would to be adopt a time-based release cycle. Ubuntu, for example, does a release every six months, and while they have some larger overreaching goals, they only really have to worry about the immediate six-month roadmap for improving the platform.

Similarly, moving to a versioning scheme beyond calling it "Alpha" or "Beta" might be a better indicator of progress on what's getting done. It would encourage podmins to pull from stable releases rather than just GitHub upstream,

Results

Results Option % of points Voters
Agree 100.0% 2 JR F
Abstain 0.0% 0  
Disagree 0.0% 0  
Block 0.0% 0  
Undecided 0% 50 ST FS MS TS AA S CB HF BO JH DM GC JH M EG G AX PP BB T

2 of 52 people have participated (3%)

JR

Jason Robinson
Agree
Sat 1 Sep 2012 8:35PM

Partly relating to this I created a proposal for a branching model which currently is missing. Definitely a release and versioning scheme is needed, although this proposal doesn't define what exactly it should be ;)

F

Flaburgan
Agree
Sat 1 Sep 2012 9:31PM

For the moment, I think we just need to branches, "unstable", and "stable", which would be make with the unstable branch once a month (for example). This is linked to ¨Define a clear git branching model¨

JH

Poll Created Thu 13 Sep 2012 10:14PM

Adopt semantic versioning with no time constraints Closed Sat 22 Sep 2012 11:54AM

See http://semver.org/.

With the following changes:

In our case API is defined as:
- Our frontend (major changes -> major version, minor changes -> minor version, you'll get the idea).
- The federation protocol.
- The client API (not existent yet)

Big internal and structural changes that do not influence the users of all sort (users, client developers, pods), except perhaps for performance, still only justify a minor version.

The version is prefixed with another number which will be increased at community decision instead of a major release. This is to avoid a false sense of rapid development and increasing stability while still maintaining a meaning in the version number changes from the start.

The first version to release will be 0.0.1

Results

Results Option % of points Voters
Agree 100.0% 10 ST FS TS BO JH JR M G DY SH
Abstain 0.0% 0  
Disagree 0.0% 0  
Block 0.0% 0  
Undecided 0% 42 MS AA S CB HF DM GC JH F EG AX PP BB T RF DM DS EP S PP

10 of 52 people have participated (19%)

FS

Florian Staudacher
Agree
Thu 13 Sep 2012 11:54PM

ok, so that would be MAYOR.MINOR.PATCH

ST

Sean Tilley
Agree
Fri 14 Sep 2012 12:39AM

I like it. Will we adopt a roadmap for milestones to hit for stable release? (in terms of platform and feature development?)

JR

Jason Robinson
Agree
Fri 14 Sep 2012 8:42AM

I totally agree and this would be nice to be implemented at the same time as we improve the branching model

SH

Steven Hancock
Agree
Sat 15 Sep 2012 5:51AM

I agree with semantic versioning. People should have a way, before they upgrade the software, to know if there are any breaking changes.

TS

Tom Scott
Agree
Mon 17 Sep 2012 8:39PM

I use SemVer for every one of my projects. It's also how I built the tagger, so I assumed we'd be using it.. :)

M

movilla
Agree
Tue 18 Sep 2012 11:44AM

It's a great idea that will help developers, users, and even podmins bloggers who publish news about new versions.

Load More